Aquileo | Recent changes to feature-requestshttps://sourceforge.net/p/linux-hotplug/feature-requests/Recent changes to feature-requestsenSat, 29 Apr 2006 18:49:24 -0000Aquileo | Device description for Canon Piwershot A410https://sourceforge.net/p/linux-hotplug/feature-requests/13/<div class="markdown_content"><p>I have the above camera and it was not allowing me to<br />
use it in digikam. I found that I could use it as root,<br />
but wanted to use it as a standard user. I tried adding<br />
the user to the camera group, but to no avail. Finally<br />
I found that the device was not described in the<br />
libgphoto2.rules file. I have added it and the camera<br />
works correctly in digikam now. I got the device<br />
information from:<br />
<a href="http://www.teaser.fr/~hfiguiere/linux/digicam.html" rel="nofollow">http://www.teaser.fr/~hfiguiere/linux/digicam.html</a></p>
<p>I added the following to my libgphoto2.rules</p>
<p># Canon PowerShot A410 (PTP mode)<br />
SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="30f9",<br />
MODE="0660", GROUP="camera"</p>
<p>If this is not the correct place for me to submit this,<br />
then my apologies, but please could you pass it on to<br />
the right place.</p>
<p>I am using Debian with a kernel I rolled from the<br />
2.6.16 Debian kernel source. The camera worked fine<br />
with Mepis, so maybe they are using different files.</p>
<p>Apart from that, many thanks for an excellent system.<br />
When it works it works mighty fine!</p></div>Matthew PearsonSat, 29 Apr 2006 18:49:24 -0000https://sourceforge.net9c4329664acf0ad8dc68dcd803599c2c50ccf0d0Aquileo | Better user actionshttps://sourceforge.net/p/linux-hotplug/feature-requests/12/<div class="markdown_content"><p>Today, I tried to write a small script. It should copy all <br />
of the images to the harddrive and delete them from the <br />
camera after copying as soon I plug the usbcam in. </p>
<p>Everything went fine while using shell programs like <br />
gphoto2 and so on. </p>
<p>As the last action in the script, I tried to open the <br />
newly created dir in konqueror. UNfortunately, I'm not <br />
that familiar with shell scripting, and got a lot of <br />
problems. Seems not to be that easy to start GUI <br />
programs using the hotplug mechanism. It's a pity, <br />
because /etc/hotplug/usb/usbcam already knew the <br />
correct user. </p>
<p>So, wouldn't it be great if hotplug also would look into <br />
the homedirectory of $CONSOLEOWNER and execute the <br />
scripts which are put there in - let's say - a <br />
subdirectory maybe called ~/.hotplug/usb/ ? </p>
<p>As one can read here: </p>
<p><a href="http://bugs.kde.org/show_bug.cgi?id=59833" rel="nofollow">http://bugs.kde.org/show_bug.cgi?id=59833</a> <br />
</p>
<p>the KDE people also plan to better integrate hotplug <br />
into the desktop. It would be great to have a easy to <br />
use GUI where a user can put/choose the ID of a device <br />
and select an action to be executed (shell scripts, or <br />
starting digikam or camera:/ as soon as his or her <br />
camera gets detected). </p>
<p>Any collaboration here would really make a lot of things <br />
easier, especially cameras which can be accessed via <br />
PTP instead of mounting it as a mass storage device. <br />
But also pen drives, scanners and similar could be <br />
possible candidates. </p></div>Christoph EckertSun, 31 Oct 2004 23:43:27 -0000https://sourceforge.netfb06ea04df49483918f67720ff804ce2d6204a91Aquileo | Please add a -v version switchhttps://sourceforge.net/p/linux-hotplug/feature-requests/11/<div class="markdown_content"><p>Hi,</p>
<p>It would be helpful if you add a -v switch. I would like <br />
it to print out something like "hotplug version 0.85 build <br />
#43 for debian 686 on March 3, 2004"</p>
<p>Truly,</p>
<p>Robert Searle</p></div>Robert SearleSun, 29 Aug 2004 19:10:32 -0000https://sourceforge.net3f0386c720f63ae7c27aae78fe6e97f5c7abb2e2Aquileo | remove bashismshttps://sourceforge.net/p/linux-hotplug/feature-requests/10/<div class="markdown_content"><p>hi,</p>
<p>i'm working in an embedded environment. it would be<br />
nice to be able to not have to use bash, and use ash<br />
provided by busybox (since bash eats about 1 Mb of my<br />
16 Mb flash).</p>
<p>i think the only thing that's needed to be removed is<br />
the arithmetic expansions, ie:</p>
<p>PCI_ANY=$((0xffffffffff))</p>
<p>causes problems with ash/busybox.</p></div>rob0214Thu, 01 Jul 2004 06:23:47 -0000https://sourceforge.neta35f5e657d2d8af5fb1e3d2e6348e50fabc4fd36Aquileo | Device ID submission: CH Products HFX Joystickhttps://sourceforge.net/p/linux-hotplug/feature-requests/9/<div class="markdown_content"><p>This USB joystick reports as:</p>
<p>cat /proc/bus/usb/devices</p>
<p>S: Manufacturer=CH PRODUCTS<br />
S: Product=CH HFX 2 AXIS 1 BUTTON JOYSTICK</p>
<p>Dec 20 00:47:39 er2 /etc/hotplug/usb.agent: Setup hid<br />
for USB product 68e/e2/0</p>
<p>I add these lines to /etc/hotplug/usb.handmap:</p>
<p># CH Products HFX OEM Joystick<br />
joydev 0x0003 0x068e 0x00e2 0x0000 <br />
0x0000 0x00 0x00 0x00 <br />
0x00 0x00 0x00 <br />
0x00000000 <br />
</p>
<p>and it all works!</p></div>Glenn BurkhardtSat, 31 Jan 2004 20:43:06 -0000https://sourceforge.net60d432a99edd0f8fadd188f53b4501f7ad9b576cAquileo | Submitting device ID data : Olympus C-750UZhttps://sourceforge.net/p/linux-hotplug/feature-requests/8/<div class="markdown_content"><p>When attempting to plug in an Olympus C-750UZ digital<br />
camera to a USB port, I was getting this error message:</p>
<p>Dec 22 01:05:40 devastator kernel: hub.c: new USB<br />
device 02:06.0-1, assigned address 6<br />
Dec 22 01:05:40 devastator kernel: WARNING: USB Mass<br />
Storage data integrity not assured<br />
Dec 22 01:05:40 devastator kernel: USB Mass Storage<br />
device found at 6<br />
Dec 22 01:05:43 devastator usb.agent[13805]: ... no<br />
modules for USB product 7b4/105/1</p>
<p>I added the following line to /etc/hotplug/usb.handmap:</p>
<p>usb-storage 0x000f 0x07b4 0x0105 0x0000 <br />
0x0000 0x00<br />
0x00 0x00 0x00 <br />
0x00 0x00<br />
0x00000000</p>
<p>The camera now appears as a new scsi disk upon hot-plug<br />
in, and I can access its flash card properly.</p>
<p>Submitter: Carl Miller (chaz *AT* energoncube *DOT* net)</p></div>AnonymousMon, 22 Dec 2003 09:45:08 -0000https://sourceforge.net7b6715b27104eca3b9bff90402df57f4b57631e3Aquileo | fxload Hexfile from stdinhttps://sourceforge.net/p/linux-hotplug/feature-requests/7/<div class="markdown_content"><p>I made a little script to put on hotplug directory for a <br />
simpler linux embedded use (for my own devices), <br />
works fine but need to write the code to the disk before <br />
load it, just wonder if its possible to load the data for <br />
fxload from stdin .</p></div>AnonymousTue, 22 Apr 2003 10:20:13 -0000https://sourceforge.net6b64c1dcbda41fb4b9a3ef2af0471ab8e5d87382Aquileo | cardbus modem troublehttps://sourceforge.net/p/linux-hotplug/feature-requests/6/<div class="markdown_content"><p>Hi there,</p>
<p>I'm having trouble with a cardbus PCMCIA modem. The<br />
modem is a Xircom RBM56g and used to work fine with<br />
with 2.2 series kernels (when it was handled by the<br />
serial_cb driver of the PCMCIA subsystem). I<br />
understand that in the 2.4 kernels, the hotplug<br />
subsystem is supposed to take care of the modem, and to<br />
use the serial driver. However, the hotplug system<br />
doesn't seem to know what to do with the modem and<br />
passes responsibility back to the PCMCIA system (that<br />
attempts to use a wrong driver; serial_cb is not part<br />
of the kernel, and attempting to use serial_cs fails).<br />
Here's what my system log says what happens upon<br />
insertion of the modem:</p>
<p>kernel: cs: cb_alloc(bus 2): vendor 0x115d, device 0x0101<br />
kernel: PCI: Enabling device 02:00.0 (0000 -&gt; 0003)<br />
cardmgr[973]: initializing socket 0<br />
cardmgr[973]: socket 0: Serial or Modem<br />
cardmgr[973]: executing: 'modprobe serial_cs' </p>
<p>Is there a way to tell the system to use the regular<br />
serial driver? And if so, does it work even if that<br />
driver is compiled into the kernel rather than loaded<br />
as a module? I'd very much appreciate any help you can<br />
give me.</p>
<p>Dirk</p>
<p>Dirk.Arnold@uDu.edu</p></div>AnonymousTue, 07 Jan 2003 10:25:48 -0000https://sourceforge.net2b4b8527258e1e9700814efade6a0fd1911c9556Aquileo | Dynamic SCSI bus rescanhttps://sourceforge.net/p/linux-hotplug/feature-requests/5/<div class="markdown_content"><p>For Linux to be more acceptable as an enterprise level<br />
OS, it needs to provide features at par with other<br />
UNIX-flavored OSes out there.</p>
<p>I would really like to see a command that would cause a<br />
dynamic scasi bus rescan to get new devices or get rid<br />
of old (removed) ones in it's device tree. eg. Solaris<br />
had drvconfig, Irix has scsiha -p, etc etc.</p>
<p>I think this is one feature most people out there need<br />
in the Linux sub-system.</p>
<p>Thanks,<br />
Rajat Gupta</p></div>AnonymousMon, 14 Jan 2002 18:25:15 -0000https://sourceforge.net331ff9478b2833d5cb3a6e39a8a0582f77c6f532Aquileo | Automatic downloading of drivers.https://sourceforge.net/p/linux-hotplug/feature-requests/4/<div class="markdown_content"><p>It's quite easy to use wget to do a query to some <br />
central HTTP server which will return all necessary <br />
info about how to get a driver for a specific <br />
(USB|PCI|*) device (especially from a shell script), <br />
so why isn't this feature supported (yet)?</p></div>stamitFri, 21 Dec 2001 10:46:37 -0000https://sourceforge.netcbc1028dabb8281fe0ee34e2f37a48913eec738b