On Mon, 18 Oct 2004, Mike Yates wrote: > Today I booted SuSE with no USB devices, then plugged in the 250Gb drive:- > > > Bus 005 Device 002: ID 07ab:fccd Freecom Technologies > > Bus 005 Device 001: ID 0000:0000 > > 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 > > So, I'm sorry, my CD-RW is "fc01" and my client's 250Gb id "fccd", just > like Eero's 160Gb.
Okay, that clears up one mystery. > The "IDE bridge" is not only confusing to me, it seems to trigger > usb-storage unnecessarily for the CD-RW:- > > > usb 1-1: new full speed USB device using address 2 > > Initializing USB Mass Storage driver... > > scsi0 : SCSI emulation for USB Mass Storage devices > > Vendor: TEAC Model: CD-W54E Rev: 1.1B > > Type: CD-ROM ANSI SCSI revision: 02 > > sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray > > Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 > > Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 5 > > USB Mass Storage device found at 2 > > usbcore: registered new driver usb-storage > > USB Mass Storage support registered. It's not unnecessary. usb-storage is the driver for _all_ USB mass storage devices, including CDs. > While the 250Gb in SuSE9 consistantly fails at scsi level, locking any > attempt to "cat /proc/bus/usb/devices" (odd number of sectors):- > > > usb 5-1: new high speed USB device using address 2 > > usb 5-1: Product: FHD-Classic > > usb 5-1: Manufacturer: Freecom Technologies > > usb 5-1: SerialNumber: 10000000000000000CA89 > > Initializing USB Mass Storage driver... > > usb 5-1: control timeout on ep0in > > scsi0 : SCSI emulation for USB Mass Storage devices > > Vendor: HDS72252 Model: 5VLAT80 Rev: V36O > > Type: Direct-Access ANSI SCSI revision: 02 > > SCSI device sda: 488397169 512-byte hdwr sectors (250059 MB) > > sda: assuming drive cache: write through > > sda:SCSI error : <0 0 0 0> return code = 0x70000 > > end_request: I/O error, dev sda, sector 488397168 > > Buffer I/O error on device sda, logical block 488397168 Which version of the kernel is that? I vaguely recall seeing 2.6.5 in an earlier email. The FIX_CAPACITY patch I sent to Eero ought to work just as well even with 2.6.5. Maybe it will get you up and running. > Back in Fedora2 with verbose, Alan Stern patched kernel, the GetMaxLUN > fails -71 and it gives up quickly:- > > > ehci_hcd 0000:00:0d.2: GetStatus port 1 status 001803 POWER sig=j CSC CONNECT > > hub 1-0:1.0: port 1, status 0501, change 0001, 480 Mb/s > > hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x501 > > hub 1-0:1.0: port 1 not reset yet, waiting 50ms > > ehci_hcd 0000:00:0d.2: port 1 high speed > > ehci_hcd 0000:00:0d.2: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT > > usb 1-1: new high speed USB device using address 2 > > usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=3 > > usb 1-1: default language 0x0409 > > usb 1-1: Product: FHD-Classic > > usb 1-1: Manufacturer: Freecom Technologies > > usb 1-1: SerialNumber: 10000000000000000CA89 > > usb 1-1: hotplug > > usb 1-1: adding 1-1:1.0 (config #1, interface 0) > > usb 1-1:1.0: hotplug > > usb-storage 1-1:1.0: usb_probe_interface > > usb-storage 1-1:1.0: usb_probe_interface - got id > > usb-storage: USB Mass Storage device detected > > usb-storage: altsetting is 0, id_index is 72 > > usb-storage: -- associate_dev > > usb-storage: Vendor: Freecom Technologies > > usb-storage: Product: FHD-Classic > > usb 1-1: control timeout on ep0in > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > usb-storage: Transport: Bulk > > usb-storage: Protocol: Transparent SCSI > > usb-storage: Endpoints: In: 0xcc6d6474 Out: 0xcc6d6460 Int: 0x00000000 (Period 0) > > usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1 > > ehci_hcd 0000:00:0d.2: devpath 1 ep0in 3strikes > > usb-storage: GetMaxLUN command result is -71, data is 0 > > usb-storage: storage_probe() failed > > usb-storage: -- usb_stor_release_resources > > usb-storage: -- dissociate_dev > > usb-storage: probe of 1-1:1.0 failed with error -1 And which kernel version was that? I suspect the problem here lies with the EHCI driver or the string descriptor routines. > However, when the Maxtor HDD is connected, it goes back to probing the > Freecom 250Gb:- Why do you say that? The log messages I omitted show the system probing the Maxtor drive, not the HDS drive. > Likewise at any other USB connection or disconnection, while without the > 250Gb connected, the dmesg output is much shorter. There shouldn't be any difference. Can you post some examples, comparing what happens when you attach the TEAC CD drive with the 250 GB disk plugged in and without it? > Is the GetMaxLUN (or whatever) fixable? The problem starts earlier than the GetMaxLUN; it appears during some string descriptor fetches. And the odd thing is that those very same fetches worked correctly just moments earlier, during initial device detection. The fact that it works for Eero in 2.6.9-rc4-mm1 indicates that the problem already has been fixed, but the fix isn't in the kernel version you're using. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
