Prev: Incoming FAX call discrimination
Next: Handling multicore CPUs; what the competition is thinking
From: Frank Pittel on 21 Mar 2010 15:36
have an internal card reader that connect via usb. I'm finding that when I
plug in a memory card a umount of the card "unmounts" the card reader. From
that point forward I can't use the device without rebooting the machine!!
I've tried unloading the usb-storage module and reloading it but that
doesn't help. I see the following entries in the messages file when I do
that.

Mar 20 22:12:15 localhost kernel: usbcore: deregistering interface driver
usb-storage
Mar 20 22:12:23 localhost kernel: Initializing USB Mass Storage driver...
Mar 20 22:12:23 localhost kernel: usb-storage: probe of 2-3:1.0 failed with
error -1
Mar 20 22:12:23 localhost kernel: usbcore: registered new interface driver
usb-storage
Mar 20 22:12:23 localhost kernel: USB Mass Storage support registered.
Mar 20 22:17:32 localhost kernel: usbcore: deregistering interface driver
usb-storage
Mar 20 22:18:52 localhost kernel: Initializing USB Mass Storage driver...
Mar 20 22:18:52 localhost kernel: usb-storage: probe of 2-3:1.0 failed with
error -1
Mar 20 22:18:52 localhost kernel: usbcore: registered new interface driver
usb-storage
Mar 20 22:18:52 localhost kernel: USB Mass Storage support registered.

I'm hoping that there's a solution because I like the idea of having an
internal card reader. As it stands it's only slightly better then useless.

--




-------------------
Keep working dumbo needs the money
From: Lusotec on 21 Mar 2010 16:32
Frank Pittel wrote:
> have an internal card reader that connect via usb. I'm finding that when
> I plug in a memory card a umount of the card "unmounts" the card reader.
> From that point forward I can't use the device without rebooting the
> machine!! I've tried unloading the usb-storage module and reloading it but
> that doesn't help. I see the following entries in the messages file when I
> do that.
>
> Mar 20 22:12:15 localhost kernel: usbcore: deregistering interface driver
> usb-storage
> Mar 20 22:12:23 localhost kernel: Initializing USB Mass Storage driver...
> Mar 20 22:12:23 localhost kernel: usb-storage: probe of 2-3:1.0 failed
> with error -1
> Mar 20 22:12:23 localhost kernel: usbcore: registered new interface driver
> usb-storage
> Mar 20 22:12:23 localhost kernel: USB Mass Storage support registered.
> (...)
> I'm hoping that there's a solution because I like the idea of having an
> internal card reader. As it stands it's only slightly better then useless.

Sorry, with only that information I can't help you.

Use the command "lsusb -v" to check the state of the USB subsystem. Use a
diff command to expose the differences in the various relevant moments
(before inserting card, after inserting card, after mount, after unmount,
after removing modules, after reloading modules) and post diff's output.

Run udevd in debug mode, "udevd --debug --debug-trace", and post the output.

Also, the command "lshal -m" will show what HAL thinks is happening to the
system. Post that too.

With (some of) that information, it should be possible (for you or someone
else) to diagnose the problem.

Regards.

From: Wolfgang Draxinger on 28 Mar 2010 10:59
Frank Pittel wrote:

> have an internal card reader that connect via usb. I'm finding that when
> I
> plug in a memory card a umount of the card "unmounts" the card reader.
> From that point forward I can't use the device without rebooting the
> machine!! I've tried unloading the usb-storage module and reloading it but
> that doesn't help. I see the following entries in the messages file when I
> do that.

That happens if the unmounting programm issues an eject on the device. By
some people it's considered the correct behaviour for e.g. USB thumb drives.
It's the wrong thing for a storage card terminal.

Depening on which method is used (HAL, or pmount) this behaviour can be
configured.

However a ordinary umount, performed on the command line, will not eject the
device.

Wolfgang

 | 
Pages: 1
Prev: Incoming FAX call discrimination
Next: Handling multicore CPUs; what the competition is thinking