From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 05:07:39 2011 Return-Path: Delivered-To: mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CF5B106564A for ; Fri, 28 Oct 2011 05:07:39 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3EFD58FC13 for ; Fri, 28 Oct 2011 05:07:39 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p9S52jRp028890 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Thu, 27 Oct 2011 23:02:45 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20111028151655.E71254@sola.nimnet.asn.au> Date: Thu, 27 Oct 2011 23:02:41 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <708A7A3F-4F03-43B6-B630-5B4128309B0C@bsdimp.com> References: <20111028005925.A98377@sola.nimnet.asn.au> <20111028151655.E71254@sola.nimnet.asn.au> To: Ian Smith X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Thu, 27 Oct 2011 23:02:45 -0600 (MDT) Cc: mobile@freebsd.org Subject: Re: Billionton Cardbus to USB 2.0 PC Card adapter X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 05:07:39 -0000 On Oct 27, 2011, at 10:22 PM, Ian Smith wrote: > On Thu, 27 Oct 2011, Warner Losh wrote: >> Power to the USB device? CardBus cards don't get much power from the=20= >> system, and often are underprovisioned to give power to the devices. =20= >> Many of the require additional external adapters to power just about=20= >> anything. Try a self-powered device instead. I've had several=20 >> experiences where I had non-working devices that worked when I=20 >> plugged in an external adapter. >>=20 >> Warner >=20 > Thanks Warner. I'm off for a couple of days but will try it through a=20= > powered hub when I get back. Funny, it has a small socket between the=20= > ports on the card for a 2.5mm? plug saying 5V (with usual polarity) = and=20 > I assumed that was a 5V power output - but maybe it's asking for 5V=20 > input? No plug or cord with it, so I'll hunt one up and test it. That's exactly what that's for. To provide power to external devices. > Getting hard to find good Cardbus gear these days .. Yea.. Ebay is even drying up. Warner > cheers, Ian >=20 >> On Oct 27, 2011, at 9:17 PM, Ian Smith wrote: >>=20 >>> Finding no clues to something known to work on FreeBSD, I'm trying=20= >>> $subject card, wanting to add 2 x USB 2.0 ports to my Thinkpad T23=20= >>> running 8.2-RELEASE, and soon 9.0-RC1 >>>=20 >>> The T23 has 2 x USB 1.0 UHCI ports. They work fine but 12 minutes = to=20 >>> write an 9.0-RC1 image is not much fun, forget external USB HDs etc. >>>=20 >>> Plugging in the card looks promising enough: >>>=20 >>> Oct 27 18:28:54 t23 kernel: ohci0: mem = 0x88000000-0x88000fff irq 11 at device 0.0 on cardbus0 >>> Oct 27 18:28:54 t23 kernel: ohci0: [ITHREAD] >>> Oct 27 18:28:54 t23 kernel: usbus3: on = ohci0 >>> Oct 27 18:28:54 t23 kernel: usbus3: 12Mbps Full Speed USB v1.0 >>> Oct 27 18:28:54 t23 kernel: ohci1: mem = 0x88001000-0x88001fff irq 11 at device 0.1 on cardbus0 >>> Oct 27 18:28:54 t23 kernel: ohci1: [ITHREAD] >>> Oct 27 18:28:54 t23 kernel: ugen3.1: at usbus3 >>> Oct 27 18:28:54 t23 kernel: uhub3: on usbus3 >>> Oct 27 18:28:54 t23 kernel: usbus4: on = ohci1 >>> Oct 27 18:28:54 t23 kernel: usbus4: 12Mbps Full Speed USB v1.0 >>> Oct 27 18:28:54 t23 kernel: ehci0: mem 0x88002000-0x880020ff irq 11 at device 0.2 on cardbus0 >>> Oct 27 18:28:54 t23 kernel: ehci0: [ITHREAD] >>> Oct 27 18:28:54 t23 kernel: usbus5: EHCI version 0.95 >>> Oct 27 18:28:54 t23 kernel: ugen4.1: at usbus4 >>> Oct 27 18:28:54 t23 kernel: uhub4: on usbus4 >>> Oct 27 18:28:54 t23 kernel: usbus5: on ehci0 >>> Oct 27 18:28:54 t23 kernel: usbus5: 480Mbps High Speed USB v2.0 >>> Oct 27 18:28:54 t23 kernel: ugen5.1: at usbus5 >>> Oct 27 18:28:54 t23 kernel: uhub5: on usbus5 >>> Oct 27 18:28:56 t23 kernel: uhub4: 2 ports with 2 removable, self = powered >>> Oct 27 18:28:56 t23 kernel: uhub3: 3 ports with 3 removable, self = powered >>> Oct 27 18:28:57 t23 kernel: uhub5: 5 ports with 5 removable, self = powered >>>=20 >>> But plugging in either of my (working on the UHCI USB1 ports) USB = memory=20 >>> sticks fails, and in quite inconsistent ways on subsequent insertion = and=20 >>> removal. More successful, in that /dev/da0 appears but is = inaccessible: >>>=20 >>> Oct 28 01:26:52 t23 root: Unknown USB device: vendor 0x0951 product = 0x1624 bus uhub5 >>> Oct 28 01:26:52 t23 kernel: ugen5.2: at usbus5 >>> Oct 28 01:26:52 t23 kernel: umass0: on usbus5 >>> Oct 28 01:26:52 t23 kernel: umass0: SCSI over Bulk-Only; quirks =3D = 0x0000 >>> Oct 28 01:26:53 t23 kernel: umass0:2:0:-1: Attached to scbus2 >>> Oct 28 01:26:55 t23 kernel: (probe0:umass-sim0:0:0:0): AutoSense = failed >>> Oct 28 01:26:55 t23 kernel: da0 at umass-sim0 bus 0 scbus2 target 0 = lun 0 >>> Oct 28 01:26:55 t23 kernel: da0: = Removable Direct Access SCSI-0 device >>> Oct 28 01:26:55 t23 kernel: da0: 40.000MB/s transfers >>> Oct 28 01:26:55 t23 kernel: da0: 7640MB (15646720 512 byte sectors: = 255H 63S/T 973C) >>> Oct 28 01:27:00 t23 kernel: (da0:umass-sim0:0:0:0): AutoSense failed >>> Oct 28 01:27:32 t23 last message repeated 3 times >>> Oct 28 01:29:36 t23 last message repeated 12 times >>> Oct 28 01:33:12 t23 last message repeated 4 times >>>=20 >>> .. during which time I was trying things like below, before even = trying=20 >>> to mount it. Throughout that time the LED on the stick flashes = about 4=20 >>> times per second, steady, like it's repeatedly trying to connect. >>>=20 >>> smithi on t23% ll /dev/da* >>> crw-r----- 1 root operator 0, 157 Oct 28 01:26 /dev/da0 >>> smithi on t23% id -p >>> uid smithi >>> groups smithi wheel operator staff dialer network vboxusers >>> smithi on t23% dd if=3D/dev/da0 count=3D1 | hd >>> dd: /dev/da0: Input/output error >>> 0+0 records in >>> 0+0 records out >>> 0 bytes transferred in 0.193469 secs (0 bytes/sec) >>> smithi on t23% ll /dev/da* >>> crw-r----- 1 root operator 0, 157 Oct 28 01:26 /dev/da0 >>> smithi on t23% fdisk /dev/da0 >>> fdisk: unable to get correct path for /dev/da0: Input/output error >>> smithi on t23% date >>> Fri Oct 28 01:37:21 EST 2011 >>> smithi on t23% ll /dev/da* >>> crw-r----- 1 root operator 0, 157 Oct 28 01:26 /dev/da0 >>>=20 >>> I've done all that as root other times, it's not a permissions = thing. =20 >>> Here it seems to disconnect cleanly on removal, not so at other = times: >>>=20 >>> Oct 28 01:40:36 t23 kernel: ugen5.2: at usbus5 = (disconnected) >>> Oct 28 01:40:36 t23 kernel: umass0: at uhub5, port 2, addr 2 = (disconnected) >>> Oct 28 01:40:36 t23 kernel: (da0:umass-sim0:0:0:0): lost device >>> Oct 28 01:40:36 t23 kernel: (da0:umass-sim0:0:0:0): removing device = entry >>>=20 >>> Another less successful attempt, with juicy error messages. To an = old=20 >>> systems hacker such inconsistency smells of timing issues, but my = sense=20 >>> of smell isn't what it used to be :) >>>=20 >>> Oct 27 18:32:57 t23 root: Unknown USB device: vendor 0x090c product = 0x1000 bus uhub5 >>> Oct 27 18:32:57 t23 kernel: ugen5.2: at usbus5 >>> Oct 27 18:32:57 t23 kernel: umass0: on usbus5 >>> Oct 27 18:32:57 t23 kernel: umass0: SCSI over Bulk-Only; quirks =3D = 0x0000 >>> Oct 27 18:32:58 t23 kernel: umass0:2:0:-1: Attached to scbus2 >>> Oct 27 18:32:58 t23 kernel: (probe0:umass-sim0:0:0:0): TEST UNIT = READY. CDB: 0 0 0 0 0 0 >>> Oct 27 18:32:58 t23 kernel: (probe0:umass-sim0:0:0:0): CAM status: = SCSI Status Error >>> Oct 27 18:32:58 t23 kernel: (probe0:umass-sim0:0:0:0): SCSI status: = Check Condition >>> Oct 27 18:32:58 t23 kernel: (probe0:umass-sim0:0:0:0): SCSI sense: = UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have = changed) >>> Oct 27 18:32:58 t23 kernel: da0 at umass-sim0 bus 0 scbus2 target 0 = lun 0 >>> Oct 27 18:32:58 t23 kernel: da0: Removable = Direct Access SCSI-0 device >>> Oct 27 18:32:58 t23 kernel: da0: 40.000MB/s transfers >>> Oct 27 18:32:58 t23 kernel: da0: 967MB (1981440 512 byte sectors: = 64H 32S/T 967C) >>> Oct 27 18:33:07 t23 kernel: ugen5.2: at usbus5 = (disconnected) >>> Oct 27 18:33:07 t23 kernel: umass0: at uhub5, port 1, addr 2 = (disconnected) >>> Oct 27 18:33:07 t23 kernel: (da0:umass-sim0:0:0:0): AutoSense failed >>> Oct 27 18:33:07 t23 kernel: (da0:umass-sim0:0:0:0): lost device >>> Oct 27 18:33:07 t23 kernel: (da0:umass-sim0:0:0:0): Invalidating = pack >>> Oct 27 18:33:07 t23 kernel: (da0:umass-sim0:0:0:0): removing device = entry >>>=20 >>> The apparent connection and then soon disconnection occurs without = any=20 >>> attempts at access by me. This 1GB Shintaro stick also works on the=20= >>> UHCI ports, and I'd expect the Kingston stick to be reasonable = quality. >>>=20 >>> Inserting the card with a USB stick already in place fared no = better. >>>=20 >>> Any advice on things to try welcome. >>>=20 >>> cheers, Ian >=20 >=20