On 04/01/15 16:27, Damian Weber wrote: > >> Try adding some quirks: >> >> usbconfig dump_quirk_names | grep MSC >> >> --HPS > > Dear Hans Petter and Kurt, thank you for your great advice, > I successfully attached my Verbatim USB drive > > the magic lines are > > in ./dev/usb/usbdevs : > > +vendor VERBATIM 0x18a5 Verbatim > +product VERBATIM STORENGO 0x0243 Verbatim Store N Go > > in ./dev/usb/quirk/usb_quirk.c > > /* copied from SANDISK, SDCZ2_128 */ > > + USB_QUIRK(VERBATIM, STORENGO, 0x0000, 0xffff, UQ_MSC_FORCE_WIRE_BBB, > + UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_IGNORE_RESIDUE, > + UQ_MSC_NO_SYNC_CACHE), > > > result: > a) can mount it (mount_msdosfs) > b) can read/write files (sha1-checksums verified) > > two questions remain > > 1) can the dmesg error messages be dealt with? ILLEGAL REQUEST asc:20,0 > > ugen2.2: <Verbatim> at usbus2 > umass0: <Verbatim STORE N GO, class 0/0, rev 2.10/1.00, addr 2> on usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x4080 > umass0:4:0: Attached to scbus4 > (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 > (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): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) > (probe0:umass-sim0:0:0:0): Error 22, Unretryable error > da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 > da0: <Verbatim STORE N GO > Removable Direct Access SPC-4 SCSI device > da0: 40.000MB/s transfers > da0: 14909MB (30535401 512 byte sectors: 255H 63S/T 1900C) > da0: quirks=0x2<NO_6_BYTE> > > 2) is it possible to modify usb_quirk.c without > going through the whole make-kernel dance? > Hi, If usb_quirk is built like a module you only rebuild that and load. Can you put this quirk and patch in a PR and assign to me and I'll get it in! --HPSReceived on Wed Apr 01 2015 - 12:37:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:56 UTC