Known issue, and being worked on. There is a patch floating around to fix
this, but I don't have it right now. Search mailing list archives for "not
ready to ready transition" and you should find it.
Matt
On Sat, Jun 09, 2001 at 05:43:01PM +0200, Johannes Zellner wrote:
> Hi,
>
> I tried to get a sony cd writer working but w/o success.
> I compiled scsi and usb support into the kernel (2.4.5).
> If I try to mount scd0 I get the following message:
>
> mount: /dev/scd0: unknown device
>
> below is the relevant output of 'lsusb', 'dmesg' and
> 'cat /proc/scsi/usb-storage-0/0': The cd writer is
> apparently recognized.
>
> how do I find out on which scsi device the usb-storage
> is attached ?
>
> any help much appreciated.
>
> --
> Johannes
>
> # cat /proc/scsi/usb-storage-0/0
> cat /proc/scsi/usb-storage-0/0
> Host scsi0: usb-storage
> Vendor: SONY
> Product: USB Mass STORAGE
> Serial Number: None
> Protocol: 8020i
> Transport: Control/Bulk
> GUID: 054c00230000000000000000
>
> # lsusb
> [...]
> Bus 001 Device 002: ID 054c:0023 Sony Corporation
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.00
> bDeviceClass 0 Interface
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x054c Sony Corporation
> idProduct 0x0023
> bcdDevice 2.00
> iManufacturer 1 SONY
> iProduct 2 USB Mass STORAGE
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 39
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x40
> Self Powered
> MaxPower 0mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 8 Mass Storage
> bInterfaceSubClass 2
> bInterfaceProtocol 1
> iInterface 4
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type none
> wMaxPacketSize 64
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01 EP 1 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type none
> wMaxPacketSize 64
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type none
> wMaxPacketSize 2
> bInterval 100
> Language IDs: 0409
>
> # dmesg
> [...]
> hub.c: USB new device connect on bus1/1, assigned device number 2
> usb-storage: act_altsettting is 0
> usb-storage: id_index calculated to be: 26
> usb-storage: Array length appears to be: 44
> usb-storage: USB Mass Storage device detected
> usb-storage: Endpoints: In: 0xc7f5d160 Out: 0xc7f5d174 Int: 0xc7f5d188 (Period 100)
> usb-storage: New GUID 054c00230000000000000000
> usb-storage: Transport: Control/Bulk
> usb-storage: Protocol: 8020i
> usb-storage: *** thread sleeping.
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Command INQUIRY (6 bytes)
> usb-storage: 12 00 00 00 ff 00 23 c1 07 00 00 00
> usb-storage: Call to usb_stor_control_msg() returned 12
> usb-storage: usb_stor_transfer_partial(): xfer 255 bytes
> usb-storage: usb_stor_bulk_msg() returned 0 xferred 96/255
> usb-storage: CB data stage result is 0x1
> usb-storage: -- CB transport device requiring auto-sense
> usb-storage: Issuing auto-REQUEST_SENSE
> usb-storage: Call to usb_stor_control_msg() returned 12
> usb-storage: usb_stor_transfer_partial(): xfer 18 bytes
> usb-storage: usb_stor_bulk_msg() returned 0 xferred 18/18
> usb-storage: usb_stor_transfer_partial(): transfer complete
> usb-storage: CB data stage result is 0x0
> usb-storage: -- Result from auto-sense is 0
> usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
> usb-storage: Unit Attention: (unknown ASC/ASCQ)
> usb-storage: Fixing INQUIRY data to show SCSI rev 2
> usb-storage: scsi cmd done, result=0x2
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (1/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (2/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (3/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (4/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (5/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (6/0)
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand() called
> usb-storage: *** thread awakened.
> usb-storage: Bad target number (7/0)
> usb-storage: *** thread sleeping.
> WARNING: USB Mass Storage data integrity not assured
> USB Mass Storage device found at 2
> [...]
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> http://lists.sourceforge.net/lists/listinfo/linux-usb-users
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
It's not that hard. No matter what the problem is, tell the customer
to reinstall Windows.
-- Nurse
User Friendly, 3/22/1998
PGP signature
