Re: Problem with ebook reader on usb

On Sun, 8 Dec 2013 22:44:33 +0100
Marc "UBM" Bocklet <ubm.freebsd_at_gmail.com> wrote:

> 
> Hiho! :-)
> 
> I got myself a new ebook reader (Onyx M92), but encountered a strange
> problem when connecting it to my freebsd machine. Shortly after
> mounting it, the device gets disconnected (causing the mounted storage
> to disappear). There is no such behavior with Windows 7.
> 
> uname -a:
> FreeBSD xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #11
> r258254M: Sun Nov 17 13:38:01 CET 2013
> xxx:/usr/obj/usr/src/sys/SUBMARINE_SMP  amd64
> 
> 
> The device identifies as follows:
> 
> Dec  2 17:45:51 ubm kernel: ugen4.2: <Linux 2.6.35.3-gd7932e6-dirty
> with fsl-usb2-udc> at usbus4 
> 
> Dec  2 17:45:51 ubm kernel: umass0: <Mass Storage> on usbus4 
> 
> Dec  2 17:45:51 ubm kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun
> 0 
> 
> Dec  2 17:45:51 ubm kernel: da0: <Linux File-Stor Gadget 0326>
> Removable Direct Access SCSI-2 device 
> 
> Dec  2 17:45:51 ubm kernel: da0:40.000MB/s transfers 
> 
> Dec  2 17:45:51 ubm kernel: da0: 3156MB (6463552 512 byte sectors: 255H
> 63S/T 402C) 
> 
> Dec  2 17:45:51 ubm kernel: da0: quirks=0x2<NO_6_BYTE>
> 
> I tried setting (widly guessing):
> hw.usb.power_timeout: 30 -> 0
> hw.usb.no_cs_fail: 0 -> 1
> 
> but to no avail.
> 
> Setting "hw.usb.debug: 1" yields no additional output.
> 
> usbconfig dump_device_desc yields:
> ugen4.2: <File-backed Storage Gadget Linux 2.6.35.3-gd7932e6-dirty with
> fsl-usb2-udc> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> 
>   bLength = 0x0012 
>   bDescriptorType = 0x0001 
>   bcdUSB = 0x0200 
>   bDeviceClass = 0x0000 
>   bDeviceSubClass = 0x0000 
>   bDeviceProtocol = 0x0000 
>   bMaxPacketSize0 = 0x0040 
>   idVendor = 0x0525 
>   idProduct = 0xa4a5 
>   bcdDevice = 0x0326 
>   iManufacturer = 0x0001  <Linux 2.6.35.3-gd7932e6-dirty with
>   fsl-usb2-udc> iProduct = 0x0002  <File-backed Storage Gadget>
>   iSerialNumber = 0x0003  <3230204E6F76>
>   bNumConfigurations = 0x0001 
> 
> Anybody got any ideas? :-)

Some further data: the mass storage usually remains mounted if there
is NO read/write activity. Read activity seems to immediately cause a
disconnect. Writing behaves differently, I just managed to copy a 1.4M
file onto it, it disconnected seconds after finishing. The copied file
is not corrupted.

Bye
Marc