umass, Verbatim STORE N GO drive, CAM status 0x50

[Damian Weber]

> Date: Sat, 28 Mar 2015 15:36:01
> From: Hans Petter Selasky <hps at selasky.org>
> To: Damian Weber <dweber at htwsaar.de>, freebsd-current at freebsd.org
> Subject: Re: umass, Verbatim STORE N GO drive, CAM status 0x50
> 
> On 03/28/15 15:06, Damian Weber wrote:
> > what do you recommend?
> 
> Try adding some quirks:
> 
> usbconfig dump_quirk_names | grep MSC
> 
> --HPS
> 
> 


thanks for the hint, dumping device description gives

 # usbconfig -u 2 -a 2 dump_device_desc
ugen2.2: <STORE N GO Verbatim> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0210 
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000   
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x18a5 
  idProduct = 0x0243  
  bcdDevice = 0x0100 
  iManufacturer = 0x0001  <Verbatim>
  iProduct = 0x0002  <STORE N GO>
  iSerialNumber = 0x0003  <125800000000013C>
  bNumConfigurations = 0x0001 


in order to ensure I understood it correctly 

[ 0) no umass kernel module here  ]

1) new entry for Vendor VERBATIM in
sys/dev/usb/usbdevs
with vendor id 0x18a5

2) new entry in the sys/dev/usb/quirk/usb_quirk.c below 

/* Quirks for manufacturers which USB devices does not respond */

  USB_QUIRK(VERBATIM, DUMMY, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE, UQ_MATC
H_VENDOR_ONLY),

(the "," after the last entry is a bit irritating)

most of these entries have UQ_MSC_NO_SYNC_CACHE - if that
doesn't work, I'll try UQ_MSC_NO_TEST_UNIT_READY which is
the only other option within that "does not respond"-section

3) make kernel

4) reboot

I did not find where the product ID goes ...
is that everything I have to consider?

Thanks a lot

   Damian