-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
HI everybody, I am not a subscriber - please CC me on any replies. Thanks! My iAudio G3 (1GB version) works fine on my Vaio laptop with kernel 2.6.8.1, but on my other computer (dual opteron server) with kernel 2.6.12.3 (SMP), it does not work at all. My USB printer and scanner work fine on 2.6.12.3. Both are stock kernels. Note that my laptop has no SCSI devices, but my server does have SCSI disks and a SCSI DVD reader. Here is the device info from from the 2.6.8.1 kernel (/proc/bus/usb/devices). I never see this with the 2.6.12.3 kernel. ======= /proc/bus/usb/devices from 2.6.8.1 ======= T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0e21 ProdID=0601 Rev= 1.10 S: Manufacturer=COWON S: Product=iAUDIO G3 S: SerialNumber=0002F5DB02688405 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= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms =================================================== Here is a printout from /var/log/messages which occurs on 2.6.8.1 when I first plug the device into the USB hub: ======= /var/log/messages 2.6.8.1 ======= Aug 22 21:21:09 tuxtop kernel: usb 1-2: new full speed USB device using address 2 Aug 22 21:21:11 tuxtop /etc/hotplug/usb.agent[14548]: need a device for this command Aug 22 21:21:17 tuxtop kernel: Initializing USB Mass Storage driver... Aug 22 21:21:17 tuxtop kernel: usb-storage: USB Mass Storage device detected Aug 22 21:21:17 tuxtop kernel: usb-storage: altsetting is 0, id_index is 122 Aug 22 21:21:17 tuxtop kernel: usb-storage: -- associate_dev Aug 22 21:21:17 tuxtop kernel: usb-storage: Transport: Bulk Aug 22 21:21:17 tuxtop kernel: usb-storage: Protocol: Transparent SCSI Aug 22 21:21:17 tuxtop kernel: usb-storage: Endpoints: In: 0xc8d5a2a0 Out: 0xc8d5a2b4 Int: 0x00000000 (Period 0) Aug 22 21:21:17 tuxtop kernel: usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1 Aug 22 21:21:17 tuxtop kernel: usb-storage: GetMaxLUN command result is 1, data is 0 Aug 22 21:21:17 tuxtop kernel: usb-storage: *** thread sleeping. Aug 22 21:21:17 tuxtop kernel: scsi1 : SCSI emulation for USB Mass Storage devices Aug 22 21:21:17 tuxtop kernel: usb-storage: queuecommand called Aug 22 21:21:17 tuxtop kernel: usb-storage: *** thread awakened. Aug 22 21:21:17 tuxtop kernel: usb-storage: Command INQUIRY (6 bytes) Aug 22 21:21:17 tuxtop kernel: usb-storage: 12 00 00 00 24 00 Aug 22 21:21:17 tuxtop kernel: usb-storage: Bulk Command S 0x43425355 T 0x89 L 36 F 128 Trg 0 LUN 0 CL 6 Aug 22 21:21:17 tuxtop kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Aug 22 21:21:17 tuxtop kernel: usb-storage: Status code 0; transferred 31/31 Aug 22 21:21:17 tuxtop kernel: usb-storage: -- transfer complete ...lots more...you get the idea, it worked. ========================================= Now, here is the output from /var/log/messages in the 2.6.12.3 kernel, when the device didn't work. ======= /var/log/messages 2.6.12.3 ======= Aug 22 21:09:24 amdtux kernel: usb 1-1.3: new full speed USB device using uhci_hcd and address 5 Aug 22 21:09:32 amdtux kernel: Initializing USB Mass Storage driver... Aug 22 21:09:32 amdtux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Aug 22 21:09:32 amdtux kernel: usb-storage: device found at 5 Aug 22 21:09:32 amdtux kernel: usb-storage: waiting for device to settle before scanning Aug 22 21:09:32 amdtux kernel: usbcore: registered new driver usb-storage Aug 22 21:09:32 amdtux kernel: USB Mass Storage support registered. Aug 22 21:10:52 amdtux kernel: usb 1-1.3: reset full speed USB device using uhci_hcd and address 5 Aug 22 21:10:53 amdtux kernel: usb 1-1.3: device descriptor read/64, error -71 Aug 22 21:10:53 amdtux su: (to root) andy on /dev/pts/5 Aug 22 21:10:53 amdtux su: pam_unix2: session started for user root, service su Aug 22 21:10:58 amdtux kernel: usb 1-1.3: device descriptor read/64, error -71 Aug 22 21:10:58 amdtux kernel: usb 1-1.3: reset full speed USB device using uhci_hcd and address 5 Aug 22 21:11:00 amdtux kernel: usb 1-1.3: device descriptor read/64, error -71 Aug 22 21:11:05 amdtux kernel: usb 1-1.3: device descriptor read/64, error -71 Aug 22 21:11:05 amdtux kernel: usb 1-1.3: reset full speed USB device using uhci_hcd and address 5 Aug 22 21:11:10 amdtux kernel: usb 1-1.3: device not accepting address 5, error -71 Aug 22 21:11:10 amdtux kernel: usb 1-1.3: reset full speed USB device using uhci_hcd and address 5 Aug 22 21:11:16 amdtux kernel: usb 1-1.3: device not accepting address 5, error -71 Aug 22 21:11:16 amdtux kernel: scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0 Aug 22 21:11:16 amdtux kernel: usb-storage: device scan complete Aug 22 21:11:16 amdtux kernel: usb 1-1.3: USB disconnect, address 5 ========================================== I do not know if this is a kernel problem or something else. I am open to experimenting to try to find the cause. Can anybody suggest a course of action to help solve this problem? Thanks! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDCocWHl0iXDssISsRAvkwAJ4gASnVy4MhfTx0sTVJOhfVUlRp/wCfeB/D +HeVhR/rpaujiRdKNptMKFs= =GJPK -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
