On Sun, 6 Jun 2004, James Buchanan wrote:

> Hi,
> 
> Sorry for the delay, thanks for answering my post.
> 
> Here's a snippet from /var/log/messages when I put in my flash disk,
> then took it out, then plugged in the Netgear DM602:
> 
> Jun  6 08:36:41 darkstar kernel: Initializing USB Mass Storage driver...
> Jun  6 08:36:41 darkstar kernel: usb.c: registered new driver
> usb-storage
> Jun  6 08:36:41 darkstar kernel: scsi1 : SCSI emulation for USB Mass
> Storage devices
> Jun  6 08:36:42 darkstar kernel:  sda: sda1
> Jun  6 08:36:42 darkstar kernel: USB Mass Storage support registered.
> Jun  6 08:40:30 darkstar kernel: usb.c: USB disconnect on device
> 00:07.2-2 address 2
> Jun  6 08:41:18 darkstar kernel: hub.c: new USB device 00:07.2-2,
> assigned address 3
> Jun  6 08:41:21 darkstar kernel: usb.c: registered new driver acm
> Jun  6 08:41:21 darkstar kernel: acm.c: v0.21:USB Abstract Control Model
> driver for USB modems and ISDN adapters
> 
> 
> Relevant lines are last two lines.  Seems the ACM driver thinks the
> device is OK.

You can't tell that from the log above.  All it indicates is that the ACM 
driver was loaded.  It doesn't say anything about what the driver thinks 
of the device.

>  Here is a copy of /proc/usb/devices:
> 
> T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
> B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
> D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0000 ProdID=0000 Rev= 0.00
> S:  Product=USB UHCI-alt Root Hub
> S:  SerialNumber=8000
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
> I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
> E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
> T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=0846 ProdID=3501 Rev= 0.14
> S:  Manufacturer=54697461
> S:  Product=45746830
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=200mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
> E:  Ad=81(I) Atr=03(Int.) MxPS=  32 Ivl=100ms
> E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=05(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> 
> Starting from the 11th line seems to be the comm. device, then line 16
> is the data device.  See how the hub device driver is registered for the
> comm. device?  (Or is that a line that belongs to the hub only?  I'll
> have to read up on the /proc/usb/devices file and how I should interpret
> its contents.)

No, the root hub is lines 1-9 and the comm. device is 10-19.  New devices 
occur at lines starting with 'T'.  The hub driver is bound to the hub 
device, and nothing is bound to the comm. device.

If you turn on USB debugging in your kernel's configuration, you might see 
some more informative information in the system log.

Alan Stern



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to