Martin DiViaio on 18 Jan 2004 20:25:03 -0000 |
> USB 2.0 output of /proc/bus/usb/devices: > Bus=04 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=0781 ProdID=7101 Rev= 1.02 > S: Manufacturer=SanDisk Corporation > S: Product=Cruzer Mini > S: SerialNumber=000132114 > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 > Driver=usb-storage > E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms > > DMESG: > > hub.c: new USB device 00:1d.7-3, assigned address 2 > usb.c: USB device 2 (vend/prod 0x781/0x7101) is not claimed by any > active driver. The USB module doesn't have a clue about what the device is so it's going to take a guess. > Initializing USB Mass Storage driver... > usb.c: registered new driver usb-storage > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Generic Model: STORAGE DEVICE Rev: 1.02 > Type: Direct-Access ANSI SCSI revision: 02 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > USB Mass Storage support registered. > Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 > SCSI device sda: 512000 512-byte hdwr sectors (262 MB) > sda: Write Protect is off > sda: sda1 > inserting floppy driver for 2.4.22-1.2140.nptl ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The USB module is guessing (incorrectly) that the device is a floppy drive. > floppy0: no floppy controllers found Expected. > hub.c: USB device not accepting new address (error=-71) > scsi: device set offline - not ready or command retry failed after bus > reset: host 1 channel 0 id 0 lun 0 > sda: I/O error: dev 08:00, sector 0 > I/O error: dev 08:00, sector 0 > unable to read partition table > usb.c: USB disconnect on device 00:1d.7-3 address 2 > inserting floppy driver for 2.4.22-1.2140.nptl > floppy0: no floppy controllers found Since the floppy module load failed, the USB module backs out of what it started. Someone has already said to check to make sure that the hotplug packages are installed. You will also want to check the usb.* files in /etc/hotplug to see if the card is identified. If not, you will have to add it and restart the hotplug daemon. Adding it is a little bit of an artform as there is little documentation on the process (at least I couldn't find any when I had to do it.) Running hotplugd in debug mode will provide some really important clues on what goes where. ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|