Re: MITSUMI USB FDD with USB4BSD does not work, neither

From: Michael Butler <imb_at_protected-networks.net>
Date: Sat, 28 Feb 2009 20:47:23 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Petter Selasky wrote:
> On Saturday 28 February 2009, Yoshihiro Ota wrote:
>> I have a MITSUMI USB fdd and pluged in to 8-CURRENT.
>> FreeBSD 8.0-CURRENT #5 r189058M: Thu Feb 26 11:29:13 EST 2009
>>
>> It printed as following but nothing happened there after.
>>
>> ugen0.3: <MITSUMI> at usbus0
>> umass0: <MITSUMI MITSUMI USB FDD, class 0/0, rev 1.10/1.00, addr 3> on
>> usbus0 umass0:  SCSI over Bulk-Only; quirks = 0x0100
>                                         ^^^ your device is listed with quirks.
> Maybe the quirks are incorrect. Please check the quirk table in
> /sys/dev/usb/storage/umass.c

This is a similar symptom to that which I observed .. the "standard"
USB2 code and quirks do this with my external USB drive:

ugen4.2: <Sunplus Technology Inc.> at usbus4
umass0: <Bulk Only Interface> on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:3:0:-1: Attached to scbus3
xptioctl: pass driver is not in the kernel
xptioctl: put "device pass" in your kernel config file
umass0: at ushub4, port 3, addr 2 (disconnected)

If I add a quirk entry in umass.c, I get this (once):

ugen4.2: <Sunplus Technology Inc.> at usbus4
umass0: <Bulk Only Interface> on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x0000
umass0:3:0:-1: Attached to scbus3
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <  > Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 95396MB (195371568 512 byte sectors: 255H 63S/T 12161C)

 .. but I am still unable to see da0s1 on the device.

However, if I detach the device and reattach, it fails as in the first
example. This leads me to believe that, while it saw and created "da0",
it got hung up somewhere before being able to present the slice :-(

As another data-point, a Nikon camera attaches and just works, once I
added a quirk to stop the cache-synchronization and test-unit ready
issues in response to:

ugen1.2: <NIKON> at usbus1
umass0: <NIKON NIKON DSC COOLPIX L4, class 0/0, rev 1.10/0.00, addr 2>
	on usbus1
umass0:  8070i (ATAPI) over Bulk-Only; quirks = 0x0000
umass0:3:0:-1: Attached to scbus3
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have
	changed
(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <NIKON DSC COOLPIX L4 > Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 982MB (2012160 512 byte sectors: 64H 32S/T 982C)
GEOM: da0: partition 1 does not start on a track boundary.
GEOM: da0: partition 1 does not end on a track boundary.
(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi
	status == 0x0
last message repeated 2 times
GEOM_LABEL: Label for provider da0s1 is msdosfs/NO_NAME.
(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi
	status == 0x0
toshi last message repeated 3 times
umass0: at ushub1, port 1, addr 2 (disconnected)
(da0:umass-sim0:0:0:0): lost device
(da0:umass-sim0:0:0:0): removing device entry

	Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkmp6SsACgkQQv9rrgRC1JKB4ACgjs4pomPKpjpGHTU1+rh86ZRK
JecAn1eYWMyfR2Z68PN5rEbdXTLdRNDg
=dDbk
-----END PGP SIGNATURE-----
Received on Sun Mar 01 2009 - 00:47:30 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:42 UTC