Excessivly cheap USB device issue

Robert Noland rnoland at FreeBSD.org
Sun Sep 27 14:47:37 UTC 2009


On Mon, 2009-09-28 at 00:09 +0930, Daniel O'Connor wrote:
> I have a very cheap USB CF/SD/SM/MS connected to an 8.0-RC1 system and
>  it is detected, ie..
> Sep 27 14:29:18 midget kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> Sep 27 14:29:18 midget kernel: da0: <Generic USB SD Reader 1.00> Removable Direct Access SCSI-0 device
> Sep 27 14:29:18 midget kernel: da0: 40.000MB/s transfers
> Sep 27 14:29:18 midget kernel: da0: Attempt to query device size failed: NOT READY, Medium not present
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): SCSI Status: Check Condition
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): NOT READY csi:0,aa,55,40 asc:3a,0
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Medium not present
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Unretryable error
> Sep 27 14:29:18 midget kernel: da1 at umass-sim0 bus 0 target 0 lun 1
> Sep 27 14:29:18 midget kernel: da1: <Generic USB CF Reader 1.01> Removable Direct Access SCSI-0 device
> Sep 27 14:29:18 midget kernel: da1: 40.000MB/s transfers
> Sep 27 14:29:18 midget kernel: da1: Attempt to query device size failed: NOT READY, Medium not present
> 
> If I connect a CF card to da1 and run 'fdisk da1' I get..
> [midget 0:06] ~ >fdisk da1
> load: 0.29  cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k
> fdisk: unable to get correct path for da1: Input/output error
> 
> [midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc
> ugen5.2: <Mass Storage Device Generic> at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
> 
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x0000
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x058f
>   idProduct = 0x6362
>   bcdDevice = 0x0129
> load: 0.21  cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k
>   iManufacturer = 0x0001  <retrieving string failed>
> load: 0.19  cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k
>   iProduct = 0x0002  <retrieving string failed>
>   iSerialNumber = 0x0003  <retrieving string failed>
>   bNumConfigurations = 0x0001
> 
> Perhaps some quirk would help but I'm not sure which one :)

I also have a similar device, which I've been messing with a bit the
last couple of days.  In your case, it isn't seeing the media, just the
"drive".  I've had to try various combinations of unplugging the adapter
from usb, inserting the media then plugging it back in.  It does seem to
work fairly reliably if you boot with the media already inserted, but it
doesn't seem to detect media change at all.

robert.

-- 
Robert Noland <rnoland at FreeBSD.org>
FreeBSD



More information about the freebsd-stable mailing list