Bug 190464 - lsusb fails to list device
Summary: lsusb fails to list device
Alias: None
Product: Fedora
Classification: Fedora
Component: hwdata
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-02 17:03 UTC by Bob Arendt
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-07-24 08:42:48 UTC

Attachments (Terms of Use)
lsusb and /proc/bus/usb/devices output (30.95 KB, text/plain)
2006-05-02 17:03 UTC, Bob Arendt
no flags Details
Adds iriver T10 signature to usb.ids. (403 bytes, patch)
2006-05-09 10:34 UTC, Jindrich Novy
no flags Details | Diff
applied diff (570 bytes, text/plain)
2006-05-10 14:06 UTC, Bob Arendt
no flags Details

Description Bob Arendt 2006-05-02 17:03:04 UTC
Description of problem:
An iRiver T10 usb device is no longer listed by lsusb, or recognized
by gphoto2 (did work with FC4, until upgrading to FC5).  Booting to
a Knoppix CD, lsusb works - indicating that the device and computer
hardware still function.

The device *does* show up in /proc/bus/usb/devices, but shown by lsusb.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Plug in, turn on iRiver T10 device
2.  lsusb
    It lists other devices, but not the iRiver
3.  Before conversion to UMS firmware, the T10 was not recognized by
    gphoto2 (used for PTP2 xfer capability).  D
Actual results:
    No corresponding device entry in lsusb
    gphoto2 returns "device not found"

Expected results:
    lsusb entry
    gphoto2 finds device, and (when MTP) would list contents and
    upload files.

Additional info:
    attached output of lsusb -v with USB_DEBUG=255 asserted, and
    contents of /proc/bus/usb/devices for FC5 (failure) and Knoppix (OK).

    It looks like the principle difference is that the device is now
    handled by the ehci_hcd driver in FC5, while it looks like it
    was handled by the uhci_hcd in earlier kernels (Knoppix / FC4).

    After switching the device to UMS, it's functional using the
    usb-storage driver (gphoto2 no longer required), but it still
    doesn't show in the lsusb output.

    Note that the USB mouse shows up in all output.

    The motherboard is an ASUS P4P800

Comment 1 Bob Arendt 2006-05-02 17:03:04 UTC
Created attachment 128500 [details]
lsusb and /proc/bus/usb/devices output

Comment 2 Jindrich Novy 2006-05-09 10:34:28 UTC
Created attachment 128774 [details]
Adds iriver T10 signature to usb.ids.

Your mp3 player is not detected by lsusb because there's no corresponding entry
for the VendorID/ProductID in usb.ids in usbutils. This patch adds it there.

Comment 3 Bob Arendt 2006-05-10 14:06:14 UTC
Created attachment 128851 [details]
applied diff

I applied these changes to /usr/share/hwdata/usb.ids
The device still doesn't show up via lsusb, though the kernel-side
activities (mounting UMS device, posting to /proc/bus/usb/devices)
work fine.  Now using kernel 2.6.16-1.2111_FC5smp.

Comment 4 Bob Arendt 2007-01-25 04:48:41 UTC
Same behaviour with FC6 + latest updates as of today
Linux host 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686 i686 i386

Comment 5 Thomas Woerner 2007-05-31 12:14:32 UTC
Assigning to hwdata. usbutils only contains the lsusb utility, which uses the
usb.ids database from hwdata.

Assigning to hwdata.

Comment 6 Bob Arendt 2007-07-24 01:28:04 UTC
lsusb now works for this device with the latest kernel update:


Even though this device is NOT listed in /usr/share/hwdata/usb.ids,
it still (properly) shows up:

Bus 002 Device 005: ID 4102:1013 iRiver, Ltd. 

Please feel free to close this Bug.  Though it would be interesting to get a
postmortem as to what was really broken.  I suspect it had something to with
high-speed USB devices not getting reported in in /proc properly?  This broke
the same time the xfer rate suddenly jumped up.  Perhaps the new kernel fixed it?

Comment 7 Karsten Hopp 2007-07-24 08:42:48 UTC
most probably the kernel, but I'm wondering why noone else reported this   
problem. Maybe a case where your bios settings and the kernel didn't work
together as expected.

Note You need to log in before you can comment on or make changes to this bug.