Re: ranscend JetFlash V85

2010-08-24 Thread Volodymyr Kostyrko

23.08.2010 22:39, Mykola Dzham wrote:

This is bcdDevice range. So, change first 0x0142 to 0x100 for your
flash drive or add another quirk (before quirk for all TRANSCEND's)
with 3-4 places set to 0x100.


Yes, that was the key. I'll file a pr for that.

--
Sphinx of black quartz judge my vow.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: ranscend JetFlash V85

2010-08-23 Thread Mykola Dzham
 Volodymyr Kostyrko wrote:
 21.08.2010 21:29, Hans Petter Selasky wrote:
  You can use usbconfig to add quirks on the fly. See:
 
  usbconfig -h
 
  And:
 
  man usbconfig
 
  Tried that, but it doesn't work for me or I'm messing things up...
 
  usbconfig -d 3.3 add_quirk UQ_MSC_NO_SYNC_CACHE
 
  And errors continue to show up. The man page also is kinda short on data.
 
  After setting the quirk, you need to reset or re-attach the USB device.
 
 Not a good behavior for me. What if I need to boot from one? Most FS 
 don't like been pushed off device.
 
 But this doesn't work too.
 
 usbconfig -d 3.3 add_quirk UQ_MSC_NO_TEST_UNIT_READY
 usbconfig -d 3.3 reset
 
 Gives me:
 
 Aug 21 22:46:14 limbo kernel: umass1: at uhub3, port 5, addr 3 
 (disconnected)
 Aug 21 22:46:14 limbo kernel: (da4:umass-sim1:1:0:0): lost device
 Aug 21 22:46:14 limbo kernel: (da4:umass-sim1:1:0:0): removing device entry
 Aug 21 22:46:15 limbo root: Unknown USB device: vendor 0x058f product 
 0x6387 bus uhub3
 Aug 21 22:46:15 limbo kernel: umass1: JetFlash Mass Storage Device, 
 class 0/0, rev 2.00/1.00, addr 3 on usbus3
 Aug 21 22:46:15 limbo kernel: umass1:  SCSI over Bulk-Only; quirks = 0x0100
 
 Here, quirks field doesn't change when I add more quirks.
 
 Aug 21 22:46:16 limbo kernel: umass1:2:1:-1: Attached to scbus2
 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT 
 READY. CDB: 0 0 0 0 0 0
 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: 
 SCSI Status Error
 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: 
 Check Condition
 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: 
 UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed)
 Aug 21 22:46:16 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0
 Aug 21 22:46:16 limbo kernel: da4: JetFlash TS4GJFV85 8.07 Removable 
 Direct Access SCSI-2 device
 Aug 21 22:46:16 limbo kernel: da4: 40.000MB/s transfers
 Aug 21 22:46:16 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 
 255H 63S/T 497C)
 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SYNCHRONIZE 
 CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI 
 Status Error
 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check 
 Condition
 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI sense: 
 ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list)
 
 Mentioned patch was looking like:
 
 USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, 
 UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE),
 
 But I don't understand what should be set for my flash at 3-4 places... 
 They are covering some range but inspecting my flash I don't see 
 something close to the 0x142.

This is bcdDevice range. So, change first 0x0142 to 0x100 for your
flash drive or add another quirk (before quirk for all TRANSCEND's)
with 3-4 places set to 0x100.

-- 
LEFT-(UANIC|RIPE)
JID: lev...@jabber.net.ua
PGP fingerprint: 1BCD 7C80 2E04 7282 C944  B0E0 7E67 619E 4E72 9280


pgpZ2sMmCp0yv.pgp
Description: PGP signature