From owner-freebsd-usb@FreeBSD.ORG Thu Dec 10 16:08:58 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92B3B1065708 for ; Thu, 10 Dec 2009 16:08:58 +0000 (UTC) (envelope-from spil.oss@googlemail.com) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id 5038F8FC26 for ; Thu, 10 Dec 2009 16:08:58 +0000 (UTC) Received: by ywh35 with SMTP id 35so3669351ywh.7 for ; Thu, 10 Dec 2009 08:08:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Evm38Yw2a1djUMo7dXnQ1OxTgRzrPr7hLsUYaZMT6R8=; b=LQ++Yh7hw2DceSX9/fEqYmWbCkXiMtC6U8nk9Exb68V3x4NeSE+4doOnR/aa54RiWR IcUvf+RqFOm7gDrPDhnVbh0hn020gxTlyq9zZsh4j4dRi/FMJglpDKWE0Uw+nV73LGrU u9yNMmWHWxfedN6A08F032gBowMFQw7sMeYXs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=MMWJLyXBFJC2UBpefJCkEjrUsm2MguryAUjt89TIEq2XPjwPiRtcPuuC+a0huBSkhi B1ntVWCNnrvdGA4SRQ/Tx5b4jWooQe32S/2Khiy9xe8khjxQLLKHMTfnESKj5MGOL5T5 K4VAYDq+9b2XLiWrKntn+KQOiIYFhEl99GM5k= MIME-Version: 1.0 Received: by 10.101.183.1 with SMTP id k1mr169437anp.59.1260461333230; Thu, 10 Dec 2009 08:08:53 -0800 (PST) In-Reply-To: <5fbf03c20912100108p72de71a8t95937304510c9a9a@mail.gmail.com> References: <5fbf03c20912100108p72de71a8t95937304510c9a9a@mail.gmail.com> Date: Thu, 10 Dec 2009 17:08:53 +0100 Message-ID: <5fbf03c20912100808w5606ef45i988d20c7171454a5@mail.gmail.com> From: Spil Oss To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Problem with 2.5" USB drive X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: spil.oss@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 16:08:58 -0000 On Thu, Dec 10, 2009 at 10:08 AM, Spil Oss 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 =A08 16:11:20 gw root: Unknown USB device: vendor 0x0402 product > 0x5642 bus uhub3 > Dec =A08 16:11:20 gw kernel: ugen3.2: at usbus3 > Dec =A08 16:11:20 gw kernel: umass0: Device, class 0/0, rev 2.00/1.00, addr 2> on usbus3 > Dec =A08 16:11:20 gw kernel: umass0: =A0SCSI over Bulk-Only; quirks =3D 0= x0000 > Dec =A08 16:11:21 gw kernel: umass0:0:0:-1: Attached to scbus0 > Dec =A08 16:11:21 gw kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Dec =A08 16:11:21 gw kernel: da0: Fixed > Direct Access SCSI-0 device > Dec =A08 16:11:21 gw kernel: da0: 40.000MB/s transfers > Dec =A08 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 =A09 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 =A08 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 =A08 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:2= 8,0 > Dec =A08 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: at usbus0, cfg=3D0 md=3DHOST spd=3DFULL (12M= bps) pwr=3DON bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0100 bDeviceClass =3D 0x0009 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x0000 bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x0000 idProduct =3D 0x0000 bcdDevice =3D 0x0100 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0000 bNumConfigurations =3D 0x0001 ugen1.1: at usbus1, cfg=3D0 md=3DHOST spd=3DFULL (12M= bps) pwr=3DON bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0100 bDeviceClass =3D 0x0009 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x0000 bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x0000 idProduct =3D 0x0000 bcdDevice =3D 0x0100 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0000 bNumConfigurations =3D 0x0001 ugen2.1: at usbus2, cfg=3D0 md=3DHOST spd=3DFULL (12M= bps) pwr=3DON bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0100 bDeviceClass =3D 0x0009 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x0000 bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x0000 idProduct =3D 0x0000 bcdDevice =3D 0x0100 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0000 bNumConfigurations =3D 0x0001 ugen3.1: at usbus3, cfg=3D0 md=3DHOST spd=3DHIGH (480Mbps) pwr=3DON bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0200 bDeviceClass =3D 0x0009 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x0001 bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x0000 idProduct =3D 0x0000 bcdDevice =3D 0x0100 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0000 bNumConfigurations =3D 0x0001 ugen3.2: at usbus3, cfg=3D0 md=3DHOST spd=3DHIGH (480Mbps) pwr=3DON bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0200 bDeviceClass =3D 0x0000 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x0000 bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x0402 idProduct =3D 0x5642 bcdDevice =3D 0x0100 iManufacturer =3D 0x0000 iProduct =3D 0x0001 iSerialNumber =3D 0x0002 <12345678901234567890> bNumConfigurations =3D 0x0001 Thanks! Spil