Aquileo | Recent changes to feature-requests

Aquileo | Device description for Canon Piwershot A410

2006-04-29T18:49:24Z

I have the above camera and it was not allowing me to
use it in digikam. I found that I could use it as root,
but wanted to use it as a standard user. I tried adding
the user to the camera group, but to no avail. Finally
I found that the device was not described in the
libgphoto2.rules file. I have added it and the camera
works correctly in digikam now. I got the device
information from:
http://www.teaser.fr/~hfiguiere/linux/digicam.html

I added the following to my libgphoto2.rules

# Canon PowerShot A410 (PTP mode)
SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="30f9",
MODE="0660", GROUP="camera"

If this is not the correct place for me to submit this,
then my apologies, but please could you pass it on to
the right place.

I am using Debian with a kernel I rolled from the
2.6.16 Debian kernel source. The camera worked fine
with Mepis, so maybe they are using different files.

Apart from that, many thanks for an excellent system.
When it works it works mighty fine!

Aquileo | Better user actions

2004-10-31T23:43:27Z

Today, I tried to write a small script. It should copy all
of the images to the harddrive and delete them from the
camera after copying as soon I plug the usbcam in.

Everything went fine while using shell programs like
gphoto2 and so on.

As the last action in the script, I tried to open the
newly created dir in konqueror. UNfortunately, I'm not
that familiar with shell scripting, and got a lot of
problems. Seems not to be that easy to start GUI
programs using the hotplug mechanism. It's a pity,
because /etc/hotplug/usb/usbcam already knew the
correct user.

So, wouldn't it be great if hotplug also would look into
the homedirectory of $CONSOLEOWNER and execute the
scripts which are put there in - let's say - a
subdirectory maybe called ~/.hotplug/usb/ ?

As one can read here:

http://bugs.kde.org/show_bug.cgi?id=59833

the KDE people also plan to better integrate hotplug
into the desktop. It would be great to have a easy to
use GUI where a user can put/choose the ID of a device
and select an action to be executed (shell scripts, or
starting digikam or camera:/ as soon as his or her
camera gets detected).

Any collaboration here would really make a lot of things
easier, especially cameras which can be accessed via
PTP instead of mounting it as a mass storage device.
But also pen drives, scanners and similar could be
possible candidates.

Aquileo | Please add a -v version switch

2004-08-29T19:10:32Z

Hi,

It would be helpful if you add a -v switch. I would like
it to print out something like "hotplug version 0.85 build
#43 for debian 686 on March 3, 2004"

Truly,

Robert Searle

Aquileo | remove bashisms

2004-07-01T06:23:47Z

hi,

i'm working in an embedded environment. it would be
nice to be able to not have to use bash, and use ash
provided by busybox (since bash eats about 1 Mb of my
16 Mb flash).

i think the only thing that's needed to be removed is
the arithmetic expansions, ie:

PCI_ANY=$((0xffffffffff))

causes problems with ash/busybox.

Aquileo | Device ID submission: CH Products HFX Joystick

2004-01-31T20:43:06Z

This USB joystick reports as:

cat /proc/bus/usb/devices

S: Manufacturer=CH PRODUCTS
S: Product=CH HFX 2 AXIS 1 BUTTON JOYSTICK

Dec 20 00:47:39 er2 /etc/hotplug/usb.agent: Setup hid
for USB product 68e/e2/0

I add these lines to /etc/hotplug/usb.handmap:

# CH Products HFX OEM Joystick
joydev 0x0003 0x068e 0x00e2 0x0000
0x0000 0x00 0x00 0x00
0x00 0x00 0x00
0x00000000

and it all works!

Aquileo | Submitting device ID data : Olympus C-750UZ

2003-12-22T09:45:08Z

When attempting to plug in an Olympus C-750UZ digital
camera to a USB port, I was getting this error message:

Dec 22 01:05:40 devastator kernel: hub.c: new USB
device 02:06.0-1, assigned address 6
Dec 22 01:05:40 devastator kernel: WARNING: USB Mass
Storage data integrity not assured
Dec 22 01:05:40 devastator kernel: USB Mass Storage
device found at 6
Dec 22 01:05:43 devastator usb.agent[13805]: ... no
modules for USB product 7b4/105/1

I added the following line to /etc/hotplug/usb.handmap:

usb-storage 0x000f 0x07b4 0x0105 0x0000
0x0000 0x00
0x00 0x00 0x00
0x00 0x00
0x00000000

The camera now appears as a new scsi disk upon hot-plug
in, and I can access its flash card properly.

Submitter: Carl Miller (chaz *AT* energoncube *DOT* net)

Aquileo | fxload Hexfile from stdin

2003-04-22T10:20:13Z

I made a little script to put on hotplug directory for a
simpler linux embedded use (for my own devices),
works fine but need to write the code to the disk before
load it, just wonder if its possible to load the data for
fxload from stdin .

Aquileo | cardbus modem trouble

2003-01-07T10:25:48Z

Hi there,

I'm having trouble with a cardbus PCMCIA modem. The
modem is a Xircom RBM56g and used to work fine with
with 2.2 series kernels (when it was handled by the
serial_cb driver of the PCMCIA subsystem). I
understand that in the 2.4 kernels, the hotplug
subsystem is supposed to take care of the modem, and to
use the serial driver. However, the hotplug system
doesn't seem to know what to do with the modem and
passes responsibility back to the PCMCIA system (that
attempts to use a wrong driver; serial_cb is not part
of the kernel, and attempting to use serial_cs fails).
Here's what my system log says what happens upon
insertion of the modem:

kernel: cs: cb_alloc(bus 2): vendor 0x115d, device 0x0101
kernel: PCI: Enabling device 02:00.0 (0000 -> 0003)
cardmgr[973]: initializing socket 0
cardmgr[973]: socket 0: Serial or Modem
cardmgr[973]: executing: 'modprobe serial_cs'

Is there a way to tell the system to use the regular
serial driver? And if so, does it work even if that
driver is compiled into the kernel rather than loaded
as a module? I'd very much appreciate any help you can
give me.

Dirk

Dirk.Arnold@uDu.edu

Aquileo | Dynamic SCSI bus rescan

2002-01-14T18:25:15Z

For Linux to be more acceptable as an enterprise level
OS, it needs to provide features at par with other
UNIX-flavored OSes out there.

I would really like to see a command that would cause a
dynamic scasi bus rescan to get new devices or get rid
of old (removed) ones in it's device tree. eg. Solaris
had drvconfig, Irix has scsiha -p, etc etc.

I think this is one feature most people out there need
in the Linux sub-system.

Thanks,
Rajat Gupta

Aquileo | Automatic downloading of drivers.

2001-12-21T10:46:37Z

It's quite easy to use wget to do a query to some
central HTTP server which will return all necessary
info about how to get a driver for a specific
(USB|PCI|*) device (especially from a shell script),
so why isn't this feature supported (yet)?