Certain USB storage devices do not work.

[Alex Jones]

Certain USB storage devices do not work under Ubuntu 9.04. I have all of the latest updates installed as of May 15, 2009 4:11 PM including the proposed updates and unsupported updates. Among these devices are:

Samsung Flipshot when set to "copy to/from card"

The built-in multi-card reader in the Dell XPS 700. (this is an internal card reader but it still uses USB)

Other card readers, mobile phones, and other devices are likely affected as well.

With the Samsung Flipshot, if i go to the terminal and type 'lsusb', lsusb hangs until I unplug the phone. When the phone is unplugged it will display the connected USB devices as normal, minus the phone. This phone works under older versions of Ubuntu, as well as Windows Vista. If the phone is plugged in while the computer is booting, the boot will hang while loading bluetooth until the phone is unplugged. I have no bluetooth adapter connected to the computer (although the phone may be trying to act as one). With the multi-card reader, four devices labeled "USB Drive" show up under Computer in the file manager. The links to the device nodes for the four slots on the reader show up in /dev/disk/by-id, and the corresponding device nodes show up in /dev, but they are not accessible. I get a message like "/dev/something is not a valid block device". Often broken multi-card readers are caused by lack of multiple SCSI LUN support in the kernel (the kernel's USB stack uses SCSI), although I'm not sure if this is the cause here.

My lsusb (without the phone connected of course) is:
Bus 001 Device 006: ID 0644:0200 TEAC Corp.
Bus 001 Device 003: ID 2040:6513 Hauppauge
Bus 001 Device 002: ID 04f9:001d Brother Industries, Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 046d:c216 Logitech, Inc. Dual Action Gamepad
Bus 002 Device 002: ID 0461:4d15 Primax Electronics, Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I think the "Bus 001 Device 006: ID 0644:0200 TEAC Corp." is the multi-card reader.
The names of the device node links in /dev/disk/by-id are:
/dev/disk/by-id/usb-TEAC_USB_HS-CF_Card_00000209B76E-0:0
/dev/disk/by-id/usb-TEAC_USB_HS-MS_Card_00000209B76E-0:2
/dev/disk/by-id/usb-TEAC_USB_HS-SD_Card_00000209B76E-0:3
/dev/disk/by-id/usb-TEAC_USB_HS-xD_SM_00000209B76E-0:1

I have not tested any of these other than the SD card.

[Alex Jones (blenheimears)]

This bug still affects Ubuntu as of August 23, 2009. I no longer have the desktop PC with the card reader, but I still have the phone. I think the two bugs are unrelated.

[Rogério Theodoro de Brito (rbrito)]

Hi, Alex

On 2009-08-23, at 06:29, Alex Jones wrote:

> This bug still affects Ubuntu as of August 23, 2009. I no longer have
> the desktop PC with the card reader, but I still have the phone. I
> think
> the two bugs are unrelated.

Please, do test with the new usbmount in Debian (version 0.0.17.1). I
made a change that (in many cases) changes the behavior of usbmount
and I would appreciate some feedback.

If possible, please give me some response soon, so that the new
version enters karmic before "the gates are closed" (i.e., the freeze).

Thanks, Rogério.

[Alex Jones (blenheimears)]

Apparently I'm not using Usbmount. I think I'm using whatever is included in Gnome. I think this bug might be related to Bluetooth because when I'm booting and the phone is plugged in, it hangs right when it is initializing Bluetooth. When I unplug the phone, it continues booting. I think this bug might even be in the Linux kernel.

[Alex Jones (blenheimears)]

The phone works in the Karmic pre-release. It's still broken in 9.04.

[Rogério Theodoro de Brito (rbrito)]

As the user seems to not be using usbmount, I'm closing this bug.

If necessary, please, reopen it.

Regards.