lsusb required to recognize sandisk media player as usb drive

[Jonathan Amir]

I have a sandisk sansa clip 4gb media player. It is configured to connect to the computer as a flash drive, not using mtp.

When connecting it to latest Hardy, nothing happens. Running lsusb doesn't show anything, but somehow causes some trigger and after a couple of seconds the device shows up again with a disk icon on the desktop.

Here is the output of lsusb, first time, nothing connected:

Bus 005 Device 001: ID 0000:0000
Bus 004 Device 003: ID 0a5c:2110 Broadcom Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Then I connect the device, nothing happens. Running lsusb, second time, yields the same output. However, after a few seconds the device is suddenly recognized. Running lsusb the third time yields this output, confirming the device's presence:

Bus 005 Device 006: ID 0781:7433 SanDisk Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 003: ID 0a5c:2110 Broadcom Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

lshal behaves similarly. The output is identical in the first and second times, before and after connecting the device (expect for minor battery related differences). In the third time, after running lsusb and recognizing the device, 7 more devices are dumped (I am attaching the diff).

[Andreas Moog (ampelbein)]

This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.

[Andreas Moog (ampelbein)]

Narf. Its a bug with the linux-kernel. I forgot to edit the template, sorry for that ;-)

[Sébastien Valette (sebastien-valette)]

I have exactly the same problem on My Desktop computer.

when I plug my usb drive on the box, it is correctly detected.

I also have a usb hub built-in my LCD monitor, and is I plug the drive in this plug, I have to type lsusb to trigger the detection.

output of lsusb when no drive is inserted:

Bus 008 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 003: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000

when plugging the drive to the monitor plug, lsusb outputs the same lines, and the drive appears shortly after.

then lsusb outputs:
Bus 008 Device 005: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB Flash Drive
Bus 008 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 003: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000

as a side note, the first line is wrong since my drive has 4GB capacity.

[kernel-janitor (kernel-janitor)]

Hi jonathan-amir,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 242163

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Samuel Dennis (sjdennis3)]

I can confirm this bug in Linux Mint 8, not sure whether that means it is present in Ubuntu 9.10.

I am running Mint 8 (main edition) on an IBM ThinkCentre 8142. When I plug in the device, it does not appear in Nautilus. When I run lsusb, I get the following output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Which does not include the flash disk.

However after running lsusb, the device suddenly appears in Nautilus - the lsusb command appears to trigger recognition of the device. If I run lsusb a second time now, I get the following output:

Bus 001 Device 005: ID 0ef5:2366 PointChips Flash Disk
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Which has now added the flash disk as Device 005.

This is an extremely frustrating bug, has anyone found a workaround for now?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]