Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Dec 2009 10:37:04 +0100
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        freebsd-usb@freebsd.org, spil.oss@gmail.com
Subject:   Re: Problem with 2.5" USB drive
Message-ID:  <200912111037.05348.hselasky@c2i.net>
In-Reply-To: <5fbf03c20912100808w5606ef45i988d20c7171454a5@mail.gmail.com>
References:  <5fbf03c20912100108p72de71a8t95937304510c9a9a@mail.gmail.com> <5fbf03c20912100808w5606ef45i988d20c7171454a5@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 10 December 2009 17:08:53 Spil Oss wrote:
> On Thu, Dec 10, 2009 at 10:08 AM, Spil Oss <spil.oss@googlemail.com> wrote:
> > Hello all,
> >
> > Can't get my 2.5" USB drive to work reliably. The device has a ALI
> > M5642 Chip and connects 2.5" PATA disks. Vendor 0x0402 is
> > USB_VENDOR_ACERLABS /* Acer Labs */ which ALi is afaik.
> >
> > When I connect it:
> > Dec  8 16:11:20 gw root: Unknown USB device: vendor 0x0402 product
> > 0x5642 bus uhub3
> > Dec  8 16:11:20 gw kernel: ugen3.2: <vendor 0x0402> at usbus3
> > Dec  8 16:11:20 gw kernel: umass0: <vendor 0x0402 USB 2.0 Storage
> > Device, class 0/0, rev 2.00/1.00, addr 2> on usbus3
> > Dec  8 16:11:20 gw kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0000
> > Dec  8 16:11:21 gw kernel: umass0:0:0:-1: Attached to scbus0
> > Dec  8 16:11:21 gw kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> > Dec  8 16:11:21 gw kernel: da0: <USB 2.0 Storage Device 0100> Fixed
> > Direct Access SCSI-0 device
> > Dec  8 16:11:21 gw kernel: da0: 40.000MB/s transfers
> > Dec  8 16:11:21 gw kernel: da0: 38154MB (78140160 512 byte sectors:
> > 255H 63S/T 4864C)
> >
> > When I try to dd/fdisk/bsdlabel the disk I tend to get
> > Dec  9 12:47:49 gw kernel: (da0:umass-sim0:0:0:0): AutoSense Failed
> > Sometimes the LED on the cage stays red until I reconnect it.
> > When I first `usbconfig -u 3 -a 2 reset` and then reconnect the disk
> > it is recognized again. Tried both on an Intel GM855 and a nVidia
> > nForce4 system.
> >
> > Errors that pop up when transferring data:
> > Dec  8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE
> > CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
> > Dec  8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION
> > asc:28,0 Dec  8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): Not ready to
> > ready change, medium may have changed
> >
> > Strangely it seems that this device was recognized on a previous
> > version of FreeBSD see http://takaq1.plala.jp/freebsd/usb/index.html
> > (not that I've tried!) Not quite clear what version of FreeBSD that
> > is.
> >
> > Ultimately FreeBSD crashes when I play around too long..
> >
> > Can anyone assist?
>
> Saw on the list that usbconfig dump_device_desc is helpful,
> problematic device is ugen3.2:
>
> ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0100
>   bDeviceClass = 0x0009
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x0000
>   idProduct = 0x0000
>   bcdDevice = 0x0100
>   iManufacturer = 0x0001  <Intel>
>   iProduct = 0x0002  <UHCI root HUB>
>   iSerialNumber = 0x0000  <no string>
>   bNumConfigurations = 0x0001
>
> ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0100
>   bDeviceClass = 0x0009
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x0000
>   idProduct = 0x0000
>   bcdDevice = 0x0100
>   iManufacturer = 0x0001  <Intel>
>   iProduct = 0x0002  <UHCI root HUB>
>   iSerialNumber = 0x0000  <no string>
>   bNumConfigurations = 0x0001
>
> ugen2.1: <UHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0100
>   bDeviceClass = 0x0009
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x0000
>   idProduct = 0x0000
>   bcdDevice = 0x0100
>   iManufacturer = 0x0001  <Intel>
>   iProduct = 0x0002  <UHCI root HUB>
>   iSerialNumber = 0x0000  <no string>
>   bNumConfigurations = 0x0001
>
> ugen3.1: <EHCI root HUB Intel> at usbus3, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x0009
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0001
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x0000
>   idProduct = 0x0000
>   bcdDevice = 0x0100
>   iManufacturer = 0x0001  <Intel>
>   iProduct = 0x0002  <EHCI root HUB>
>   iSerialNumber = 0x0000  <no string>
>   bNumConfigurations = 0x0001
>
> ugen3.2: <USB 2.0 Storage Device vendor 0x0402> at usbus3, cfg=0
> md=HOST spd=HIGH (480Mbps) pwr=ON
>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x0000
>   bDeviceSubClass = 0x0000
>   bDeviceProtocol = 0x0000
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x0402
>   idProduct = 0x5642
>   bcdDevice = 0x0100
>   iManufacturer = 0x0000  <no string>
>   iProduct = 0x0001  <USB 2.0 Storage Device>
>   iSerialNumber = 0x0002  <12345678901234567890>
>   bNumConfigurations = 0x0001
>
> Thanks!
>

Have you tried a 9-current kernel?

--HPS




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912111037.05348.hselasky>