Well, the pre 3.0 versions have a particular bug which requires that we
treat it as a CB device (instead of CBI). The 3.0 and later versions don't
have this bug.
The log attached looks fine -- I have no idea why you're getting a problem
from the SCSI layer. What does /proc/devices show? And what is the major
number of your sdX nodes?
Nothing has changed in this area that I know of... there have been several
SCSI-layer changes tho.
Matt
On Fri, Jun 16, 2000 at 02:16:28PM -0700, Randy Dunlap wrote:
> Matt,
>
> usb-storage.c lists (in the unusual_dev array) a Y-E Data floppy drive
> rev. 1.14 but it doesn't list rev 3.04 (the newer blue/gray one).
> Should this one be listed also?
>
> The reason that I'm asking is that I'm getting all of the LUN searching
> that doesn't look like it should be happening. (log attached)
>
> Also, after usb-storage recognized the floppy drive, I used to be
> able to enter: mount /dev/sda (no other SCSI in my system),
> where /dev/sda is listed in /etc/fstab .
> I can't do that now. mount replies:
>
> [rdunlap@dragon usb]$ mount /dev/sda
> mount: /dev/sda has wrong major or minor number
> [rdunlap@dragon usb]$
>
> and it does this with /dev/sd[a-g]. Did something change in
> this area? How do I know what to mount?
>
> Thanks,
> Randy
> hub.c: port 2 enable change, status 100
> hub.c: port 1 connection change
> hub.c: portstatus 101, change 1, 12 Mb/s
> hub.c: portstatus 103, change 10, 12 Mb/s
> usb.c: USB new device connect, assigned device number 4
> usb.c: kmalloc IF cb154620, numif 1
> usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
> usb.c: USB device number 4 default language ID 0x409
> Manufacturer: Y-E DATA
> Product: FlashBuster-U
> usb.c: unhandled interfaces on device
> usb.c: This device is not recognized by any installed USB driver.
> Length = 18
> DescriptorType = 01
> USB version = 1.00
> Vendor:Product = 057b:0000
> MaxPacketSize0 = 8
> NumConfigurations = 1
> Device version = 3.04
> Device Class:SubClass:Protocol = 00:00:00
> Per-interface classes
> Configuration:
> bLength = 9
> bDescriptorType = 02
> wTotalLength = 0027
> bNumInterfaces = 01
> bConfigurationValue = 01
> iConfiguration = 00
> bmAttributes = 80
> MaxPower = 500mA
>
> Interface: 0
> Alternate Setting: 0
> bLength = 9
> bDescriptorType = 04
> bInterfaceNumber = 00
> bAlternateSetting = 00
> bNumEndpoints = 03
> bInterface Class:SubClass:Protocol = 08:04:00
> iInterface = 04
> Endpoint:
> bLength = 7
> bDescriptorType = 05
> bEndpointAddress = 81 (in)
> bmAttributes = 02 (Bulk)
> wMaxPacketSize = 0040
> bInterval = 00
> Endpoint:
> bLength = 7
> bDescriptorType = 05
> bEndpointAddress = 02 (out)
> bmAttributes = 02 (Bulk)
> wMaxPacketSize = 0040
> bInterval = 00
> Endpoint:
> bLength = 7
> bDescriptorType = 05
> bEndpointAddress = 83 (in)
> bmAttributes = 03 (Interrupt)
> wMaxPacketSize = 0002
> bInterval = 10
> usb.c: registered new driver usb-storage
> usb-storage.c: Searching unusual device list for (0x57b, 0x0, 0x304)...
> usb-storage.c: -- found matching device: Y-E Data Flashbuster-U
> usb-storage.c: USB Mass Storage device detected
> usb-storage.c: Endpoints: In: 0xce42c8a0 Out: 0xce42c8b1 Int: 0xce42c8c2 (Period 16)
> usb-storage.c: Result from usb_set_interface is 0
> usb-storage.c: New GUID 057b00000000000000000000
> usb-storage.c: Transport: Control/Bulk
> usb-storage.c: Protocol: Uniform Floppy Interface (UFI)
> usb-storage.c: *** thread sleeping.
> scsi1 : SCSI emulation for USB Mass Storage devices
> scsi : 2 hosts.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Command INQUIRY (6 bytes)
> usb-storage.c: 12 00 00 00 ff 00 01 40 77 00
> usb-storage.c: Call to usb_stor_control_msg() returned 12
> usb-storage.c: us_transfer_partial(): xfer 256 bytes
> usb-storage.c: usb_stor_bulk_msg() returned 0 xferred 36/256
> usb-storage.c: CB data stage result is 0x1
> usb-storage.c: -- CB transport device requiring auto-sense
> usb-storage.c: ** no auto-sense for a special command
> usb-storage.c: scsi cmd done, result=0x0
> usb-storage.c: *** thread sleeping.
> Vendor: Y-E DATA Model: USB-FDU Rev: 3.04
> Type: Direct-Access ANSI SCSI revision: 02
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (1/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (2/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (3/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (4/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (5/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (6/0)
> usb-storage.c: *** thread sleeping.
> usb-storage.c: us_queuecommand() called
> usb-storage.c: *** thread awakened.
> usb-storage.c: Bad device number (7/0)
> usb-storage.c: *** thread sleeping.
> WARNING: USB Mass Storage data integrity not assured
> USB Mass Storage device found at 4
> usb.c: usb-storage driver claimed interface cb154620
> usb-storage.c: Searching unusual device list for (0x698, 0x1786, 0x1)...
> usb-storage.c: -- did not find a matching device
> USB Mass Storage support registered.
--
Matthew Dharm Home: [EMAIL PROTECTED]
Senior Engineer, QCP Inc. Work: [EMAIL PROTECTED]
We've made a business out of making money from annoying and stupid people.
I think you fall under that category.
-- Chief
User Friendly, 7/11/1998
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
