From owner-freebsd-mobile@FreeBSD.ORG Mon Oct 24 16:32:44 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EBD71065676 for ; Mon, 24 Oct 2011 16:32:44 +0000 (UTC) (envelope-from jandrese@mitre.org) Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD3B8FC14 for ; Mon, 24 Oct 2011 16:32:43 +0000 (UTC) Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9267D21B106A for ; Mon, 24 Oct 2011 12:17:28 -0400 (EDT) Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 859B521B0436 for ; Mon, 24 Oct 2011 12:17:28 -0400 (EDT) Received: from IMCMBX02.MITRE.ORG ([169.254.2.229]) by IMCCAS02.MITRE.ORG ([129.83.29.79]) with mapi id 14.01.0339.001; Mon, 24 Oct 2011 12:17:28 -0400 From: "Andresen, Jason R." To: "freebsd-mobile@freebsd.org" Thread-Topic: Battery charge limiting Thread-Index: AQHMjc9mWblqZf+yRUymWg6eDJaJmJWDQugAgAAYC4CAABDtAIAAfTgAgAAru4CAAB02AIAHgl9g Date: Mon, 24 Oct 2011 16:17:27 +0000 Message-ID: <027252D1B68F5541829574B3220B4D7801081A@IMCMBX02.MITRE.ORG> References: <201110182335.15862.onyx@z-up.ru> <201110190844.17703.onyx@z-up.ru> <201110191713.02435.onyx@z-up.ru> <4E9F0A0E.10009@paz.bz> In-Reply-To: <4E9F0A0E.10009@paz.bz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.83.31.51] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: Battery charge limiting 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: Mon, 24 Oct 2011 16:32:44 -0000 From: owner-freebsd-mobile@freebsd.org [mailto:owner-freebsd- >mobile@freebsd.org] On Behalf Of Jim Pazarena >Kevin Oberman wrote, On 2011-10-19 8:49 AM: >> On Wed, Oct 19, 2011 at 6:13 AM, Dmitry Kolosov wrote: >>> Now the question is: how to discover EC/battery controller capabilities= of >>> such functions as holding battery about X% of full charge. >> >> Or to find the EC magic to turn off charging and create a daemon that >> monitors charge level nd turns charging off at about 80% and back on >> if it drops below 75%. > >renowned Tech Guy "Leo Laporte" and security expert "Steve Gibson" >had a discussion regarding lithium ion batteries, and Steve's findings >contradict these comments. I think the deal isn't that 100% charge is bad, but overcharging is what kills the battery. The problem is that the battery level is difficult= =20 to measure so most laptops end up overcharging the battery quite badly when trying to bring it up to 100%. If you stop at 80% (which seems overly conservative to me) then you never have to worry=20 about overcharging.=20 From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 03:53:45 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 7D5E1106566B for ; Fri, 28 Oct 2011 03:53:45 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id A512C8FC13 for ; Fri, 28 Oct 2011 03:53:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p9S3HdAD073481 for ; Fri, 28 Oct 2011 14:17:39 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 28 Oct 2011 14:17:38 +1100 (EST) From: Ian Smith To: mobile@freebsd.org Message-ID: <20111028005925.A98377@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: 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 03:53:45 -0000 Finding no clues to something known to work on FreeBSD, I'm trying $subject card, wanting to add 2 x USB 2.0 ports to my Thinkpad T23 running 8.2-RELEASE, and soon 9.0-RC1 The T23 has 2 x USB 1.0 UHCI ports. They work fine but 12 minutes to write an 9.0-RC1 image is not much fun, forget external USB HDs etc. Plugging in the card looks promising enough: 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 But plugging in either of my (working on the UHCI USB1 ports) USB memory sticks fails, and in quite inconsistent ways on subsequent insertion and removal. More successful, in that /dev/da0 appears but is inaccessible: 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 = 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 .. during which time I was trying things like below, before even trying to mount it. Throughout that time the LED on the stick flashes about 4 times per second, steady, like it's repeatedly trying to connect. 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=/dev/da0 count=1 | 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 I've done all that as root other times, it's not a permissions thing. Here it seems to disconnect cleanly on removal, not so at other times: 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 Another less successful attempt, with juicy error messages. To an old systems hacker such inconsistency smells of timing issues, but my sense of smell isn't what it used to be :) 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 = 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 The apparent connection and then soon disconnection occurs without any attempts at access by me. This 1GB Shintaro stick also works on the UHCI ports, and I'd expect the Kingston stick to be reasonable quality. Inserting the card with a USB stick already in place fared no better. Any advice on things to try welcome. cheers, Ian From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 04:10:28 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 E999E1065675 for ; Fri, 28 Oct 2011 04:10:28 +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 9B8E28FC0C for ; Fri, 28 Oct 2011 04:10:28 +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 p9S49MPV028301 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Thu, 27 Oct 2011 22:09:24 -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: <20111028005925.A98377@sola.nimnet.asn.au> Date: Thu, 27 Oct 2011 22:09:18 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20111028005925.A98377@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 22:09:24 -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 04:10:29 -0000 Power to the USB device? CardBus cards don't get much power from the = system, and often are underprovisioned to give power to the devices. = Many of the require additional external adapters to power just about = anything. Try a self-powered device instead. I've had several = experiences where I had non-working devices that worked when I plugged = in an external adapter. Warner On Oct 27, 2011, at 9:17 PM, Ian Smith wrote: > 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 > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to = "freebsd-mobile-unsubscribe@freebsd.org" >=20 >=20 From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 04:22:21 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 C5C68106566B for ; Fri, 28 Oct 2011 04:22:21 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 00FB78FC14 for ; Fri, 28 Oct 2011 04:22:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p9S4MHBb075621; Fri, 28 Oct 2011 15:22:17 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 28 Oct 2011 15:22:17 +1100 (EST) From: Ian Smith To: Warner Losh In-Reply-To: Message-ID: <20111028151655.E71254@sola.nimnet.asn.au> References: <20111028005925.A98377@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 04:22:21 -0000 On Thu, 27 Oct 2011, Warner Losh wrote: > Power to the USB device? CardBus cards don't get much power from the > system, and often are underprovisioned to give power to the devices. > Many of the require additional external adapters to power just about > anything. Try a self-powered device instead. I've had several > experiences where I had non-working devices that worked when I > plugged in an external adapter. > > Warner Thanks Warner. I'm off for a couple of days but will try it through a powered hub when I get back. Funny, it has a small socket between the ports on the card for a 2.5mm? plug saying 5V (with usual polarity) and I assumed that was a 5V power output - but maybe it's asking for 5V input? No plug or cord with it, so I'll hunt one up and test it. Getting hard to find good Cardbus gear these days .. cheers, Ian > On Oct 27, 2011, at 9:17 PM, Ian Smith wrote: > > > Finding no clues to something known to work on FreeBSD, I'm trying > > $subject card, wanting to add 2 x USB 2.0 ports to my Thinkpad T23 > > running 8.2-RELEASE, and soon 9.0-RC1 > > > > The T23 has 2 x USB 1.0 UHCI ports. They work fine but 12 minutes to > > write an 9.0-RC1 image is not much fun, forget external USB HDs etc. > > > > Plugging in the card looks promising enough: > > > > 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 > > > > But plugging in either of my (working on the UHCI USB1 ports) USB memory > > sticks fails, and in quite inconsistent ways on subsequent insertion and > > removal. More successful, in that /dev/da0 appears but is inaccessible: > > > > 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 = 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 > > > > .. during which time I was trying things like below, before even trying > > to mount it. Throughout that time the LED on the stick flashes about 4 > > times per second, steady, like it's repeatedly trying to connect. > > > > 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=/dev/da0 count=1 | 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 > > > > I've done all that as root other times, it's not a permissions thing. > > Here it seems to disconnect cleanly on removal, not so at other times: > > > > 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 > > > > Another less successful attempt, with juicy error messages. To an old > > systems hacker such inconsistency smells of timing issues, but my sense > > of smell isn't what it used to be :) > > > > 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 = 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 > > > > The apparent connection and then soon disconnection occurs without any > > attempts at access by me. This 1GB Shintaro stick also works on the > > UHCI ports, and I'd expect the Kingston stick to be reasonable quality. > > > > Inserting the card with a USB stick already in place fared no better. > > > > Any advice on things to try welcome. > > > > cheers, Ian 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 From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 10:18:36 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 CF97A1065675 for ; Fri, 28 Oct 2011 10:18:36 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id 544D08FC14 for ; Fri, 28 Oct 2011 10:18:35 +0000 (UTC) Received: from [194.32.164.28] (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id p9S9s3GK014232; Fri, 28 Oct 2011 10:54:04 +0100 (BST) (envelope-from rb@gid.co.uk) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Bob Bishop In-Reply-To: <20111028151655.E71254@sola.nimnet.asn.au> Date: Fri, 28 Oct 2011 10:53:58 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7FC7ED10-2F23-41AE-9C50-5426A9FB481E@gid.co.uk> References: <20111028005925.A98377@sola.nimnet.asn.au> <20111028151655.E71254@sola.nimnet.asn.au> To: Ian Smith X-Mailer: Apple Mail (2.1084) 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 10:18:36 -0000 Hi, On 28 Oct 2011, at 05:22, Ian Smith wrote: > ...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? [etc] It's asking for 5V in, those cards can barely provide the minimum power = on the USB side without it. -- Bob Bishop rb@gid.co.uk From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 15:05:33 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83AD9106566C for ; Fri, 28 Oct 2011 15:05:33 +0000 (UTC) (envelope-from irek-kaenly@yandex.ru) Received: from forward7.mail.yandex.net (forward7.mail.yandex.net [IPv6:2a02:6b8:0:202::2]) by mx1.freebsd.org (Postfix) with ESMTP id 004AC8FC17 for ; Fri, 28 Oct 2011 15:05:32 +0000 (UTC) Received: from smtp7.mail.yandex.net (smtp7.mail.yandex.net [77.88.61.55]) by forward7.mail.yandex.net (Yandex) with ESMTP id 3AC341C35E3 for ; Fri, 28 Oct 2011 19:05:31 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1319814331; bh=mAB+xSl9Dsz64kuM1G1/QZCXQuTizo41bEkDyN4MEbE=; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; b=S5+lzMq7CHMn59xJNnSmNAlIr59B/6tdGCutrBDLS0BgoVolMxFINRPI069bvEEB6 MAMO7HX5fLYnHtrAUMnWAKBaMbEU0m5wmsqfulj1og8ruPlX8uZehtgNA2N8gzqdtO lJCsTe1qC4KZgoUXLqgvBSqdX1A05at+Jo/YKQy0= Received: from smtp7.mail.yandex.net (localhost [127.0.0.1]) by smtp7.mail.yandex.net (Yandex) with ESMTP id 1B438158054B for ; Fri, 28 Oct 2011 19:05:31 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1319814331; bh=mAB+xSl9Dsz64kuM1G1/QZCXQuTizo41bEkDyN4MEbE=; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; b=S5+lzMq7CHMn59xJNnSmNAlIr59B/6tdGCutrBDLS0BgoVolMxFINRPI069bvEEB6 MAMO7HX5fLYnHtrAUMnWAKBaMbEU0m5wmsqfulj1og8ruPlX8uZehtgNA2N8gzqdtO lJCsTe1qC4KZgoUXLqgvBSqdX1A05at+Jo/YKQy0= Received: from unknown (unknown [178.206.73.250]) by smtp7.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 5UguY0Y4-5Ug8NQIS; Fri, 28 Oct 2011 19:05:30 +0400 X-Yandex-Spam: 1 Message-ID: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> From: =?koi8-r?B?6dLFyyDzwcTZy8/X?= To: Date: Fri, 28 Oct 2011 19:05:33 +0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Mailman-Approved-At: Fri, 28 Oct 2011 15:22:28 +0000 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD release Acer Aspire 5735Z 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 15:05:33 -0000 Hello! I Irek Sadykov, I write to You from Russia.=20 I'm the owner of a laptop, which has these characteristics: Acer ASPIRE 5735Z-322G25Mn (Pentium Dual-Core T3200 2000 = Mhz/15.6"/1366x768/2048Mb/250.0Gb/DVD-RW/Wi-Fi/Win Vista HP). I wonder what kind of a FreeBSD release will be stable work in this = laptop? From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 16:02:12 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79EF81065675 for ; Fri, 28 Oct 2011 16:02:12 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0E4BB8FC12 for ; Fri, 28 Oct 2011 16:02:11 +0000 (UTC) Received: by faar19 with SMTP id r19so5356573faa.13 for ; Fri, 28 Oct 2011 09:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=x5ooG+m/ORdmOhNGNlDIOu9CQgXyxpGy/u4ISPEQjTk=; b=AJQND5N2mO8TgirRa6UYo8uCOpppV8gqxCGwjP5vy5QzWWlHYBRdgWhdRUBW29e7qw OwFqg/BWY+PefVOygwd0WLoGnB+lUK2du4NvLEkAPam2otjrDnLYVA/eRXX1I/qBVcFa 5xwR33banChuvZT3cZESvVMqyTCyn4JEbaS1w= Received: by 10.223.75.15 with SMTP id w15mr6903914faj.9.1319815856163; Fri, 28 Oct 2011 08:30:56 -0700 (PDT) Received: from [192.168.0.150] (athedsl-4364788.home.otenet.gr. [79.130.9.228]) by mx.google.com with ESMTPS id x19sm10287596fag.5.2011.10.28.08.30.53 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Oct 2011 08:30:54 -0700 (PDT) Message-ID: <4EAACAAF.7020107@gmail.com> Date: Fri, 28 Oct 2011 18:30:55 +0300 From: Manolis Kiagias User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: =?UTF-8?B?0JjRgNC10Log0KHQsNC00YvQutC+0LI=?= References: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> In-Reply-To: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-mobile@freebsd.org Subject: Re: FreeBSD release Acer Aspire 5735Z 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 16:02:12 -0000 On 28/10/2011 6:05 μμ, Ирек Садыков wrote: > Hello! > I Irek Sadykov, I write to You from Russia. > > I'm the owner of a laptop, which has these characteristics: > Acer ASPIRE 5735Z-322G25Mn (Pentium Dual-Core T3200 2000 Mhz/15.6"/1366x768/2048Mb/250.0Gb/DVD-RW/Wi-Fi/Win Vista HP). > > I wonder what kind of a FreeBSD release will be stable work in this laptop? I suggest you try the latest 9.0-RC1. Acer is notorious for FreeBSD-unfriendly BIOSes, my 5739G has several problems with every 7.X to 8.X release including panics and failing to attach to devices such as network cards and wireless. 9.0-RC1 seems to work ok though. From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 28 18:24:36 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FF04106564A for ; Fri, 28 Oct 2011 18:24:36 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 4E1C28FC13 for ; Fri, 28 Oct 2011 18:24:35 +0000 (UTC) Received: from [89.204.154.182] (helo=tiny.Sisis.de.) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1RJqQ2-0000sq-RD; Fri, 28 Oct 2011 19:40:40 +0200 Received: from tiny.Sisis.de. (localhost [127.0.0.1]) by tiny.Sisis.de. (8.14.3/8.14.3) with ESMTP id p9SHetlu001047; Fri, 28 Oct 2011 19:40:55 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de. (8.14.3/8.14.3/Submit) id p9SHerLp001046; Fri, 28 Oct 2011 19:40:53 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de.: guru set sender to guru@unixarea.de using -f Date: Fri, 28 Oct 2011 19:40:53 +0200 From: Matthias Apitz To: =?utf-8?B?0JjRgNC10Log0KHQsNC00YvQutC+0LI=?= Message-ID: <20111028174052.GA1034@tiny> References: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 89.204.154.182 Cc: freebsd-mobile@freebsd.org Subject: Re: FreeBSD release Acer Aspire 5735Z X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 18:24:36 -0000 El día Friday, October 28, 2011 a las 07:05:33PM +0400, Ирек Садыков escribió: > Hello! > I Irek Sadykov, I write to You from Russia. > > I'm the owner of a laptop, which has these characteristics: > Acer ASPIRE 5735Z-322G25Mn (Pentium Dual-Core T3200 2000 Mhz/15.6"/1366x768/2048Mb/250.0Gb/DVD-RW/Wi-Fi/Win Vista HP). > > I wonder what kind of a FreeBSD release will be stable work in this laptop? Hello, As you own the laptop already, try to boot a recent Knoppix live DVD to see what chips are in the box exactly; than check if drivers are available, esp. for graphic and Wifi; HIH matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 29 10:08:06 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63236106566C for ; Sat, 29 Oct 2011 10:08:06 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id E7FB18FC17 for ; Sat, 29 Oct 2011 10:08:05 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mail.0x20.net (Postfix) with ESMTP id 8C6EF6A6619; Sat, 29 Oct 2011 12:08:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.0x20.net Received: from mail.0x20.net ([217.69.76.211]) by mail.0x20.net (mail.0x20.net [217.69.76.211]) (amavisd-new, port 10024) with ESMTP id ggTkiuHIyC5p; Sat, 29 Oct 2011 12:08:04 +0200 (CEST) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 413566A6016; Sat, 29 Oct 2011 12:08:04 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.4/8.14.4) with ESMTP id p9TA84a1067588; Sat, 29 Oct 2011 12:08:04 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.4/8.14.4/Submit) id p9TA83oO066645; Sat, 29 Oct 2011 12:08:03 +0200 (CEST) (envelope-from lars) Date: Sat, 29 Oct 2011 12:08:03 +0200 From: Lars Engels To: Matthias Apitz Message-ID: <20111029100803.GA96706@e-new.0x20.net> References: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> <20111028174052.GA1034@tiny> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" Content-Disposition: inline In-Reply-To: <20111028174052.GA1034@tiny> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.2-RELEASE-p3 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ???????? ?????????????? , freebsd-mobile@freebsd.org Subject: Re: FreeBSD release Acer Aspire 5735Z 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: Sat, 29 Oct 2011 10:08:06 -0000 --liOOAslEiF7prFVr Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 28, 2011 at 07:40:53PM +0200, Matthias Apitz wrote: > El d=C3=ADa Friday, October 28, 2011 a las 07:05:33PM +0400, ???????? ???= ??????????? escribi=C3=B3: >=20 > > Hello! > > I Irek Sadykov, I write to You from Russia.=20 > >=20 > > I'm the owner of a laptop, which has these characteristics: > > Acer ASPIRE 5735Z-322G25Mn (Pentium Dual-Core T3200 2000 Mhz/15.6"/1366= x768/2048Mb/250.0Gb/DVD-RW/Wi-Fi/Win Vista HP). > >=20 > > I wonder what kind of a FreeBSD release will be stable work in this lap= top? >=20 > Hello, >=20 > As you own the laptop already, try to boot a recent Knoppix live DVD to > see what chips are in the box exactly; than check if drivers are > available, esp. for graphic and Wifi; And cross your fingers that the button to enable / disable wireless works out of the box. Unfortunately there's no port of Linux' acer_acpi [1] to FreeBSD.=20 [1] http://code.google.com/p/aceracpi/ --liOOAslEiF7prFVr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk6r0IMACgkQKc512sD3afiNNQCeKWk/c44IzamI95Y39taqqxQr D4wAoLDOSQum4b03xZ4wEHo9WIeDPLDC =aWsH -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 29 13:38:30 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7F7E106566C for ; Sat, 29 Oct 2011 13:38:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9E32C8FC0A for ; Sat, 29 Oct 2011 13:38:30 +0000 (UTC) Received: by vws5 with SMTP id 5so5962226vws.17 for ; Sat, 29 Oct 2011 06:38:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ubV7gI3nQahTt5s6b56e/MQGtrnlVxFbsrtYDIQ06QQ=; b=r9fbXVLtbGVQ699hyQcDsewPkUbQDnyM73UVhUP6MqkCKU30AYq8zWoOB0cRKpU0a9 QRo3mJ6xegIhd1YN6klzTWEd0SqNq4MwFImwArsMNrv1FQE5Ho7oOSEnHzmG3n/kEoce IXqJWmwDihX6KPPtJajH1PBWIyDl0G4Kvv0gY= MIME-Version: 1.0 Received: by 10.52.34.100 with SMTP id y4mr1605435vdi.66.1319895509459; Sat, 29 Oct 2011 06:38:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.164.101 with HTTP; Sat, 29 Oct 2011 06:38:29 -0700 (PDT) In-Reply-To: <20111029100803.GA96706@e-new.0x20.net> References: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> <20111028174052.GA1034@tiny> <20111029100803.GA96706@e-new.0x20.net> Date: Sun, 30 Oct 2011 00:38:29 +1100 X-Google-Sender-Auth: br5QXF6NXhlSe4EhOd4hIEwMs8U Message-ID: From: Adrian Chadd To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 Cc: irek-kaenly@yandex.ru, Matthias Apitz , freebsd-mobile@freebsd.org Subject: Re: FreeBSD release Acer Aspire 5735Z 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: Sat, 29 Oct 2011 13:38:31 -0000 On 29 October 2011 21:08, Lars Engels wrote: > And cross your fingers that the button to enable / disable wireless > works out of the box. Unfortunately there's no port of Linux' acer_acpi > [1] to FreeBSD. > > [1] http://code.google.com/p/aceracpi/ Please please please, can someone port this? Adrian From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 29 18:42:09 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 372C8106566C for ; Sat, 29 Oct 2011 18:42:09 +0000 (UTC) (envelope-from mubeeshalivm@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id C3AEE8FC08 for ; Sat, 29 Oct 2011 18:42:08 +0000 (UTC) Received: by wwi18 with SMTP id 18so6928842wwi.31 for ; Sat, 29 Oct 2011 11:42:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Qi2AvMLzWKeZDrC780fxEkCXE880giYrTnCn4phk3y4=; b=KJsclrFlz2CMHhaF02MrF1Z480nqmdg/Py6u4TlpX3uyZO4bsTL7k85p7/44zofKRc Z409WxOnMtofmB6/twxpY8gEkf6DxWw32Q1GgzbCtFq/bgwL5gBfX+UAaah/pQ7HrqKm 912AQurWd7Ci0aTydAxPukvTCj0Bz4QXN1lrg= MIME-Version: 1.0 Received: by 10.227.205.2 with SMTP id fo2mr9900456wbb.21.1319912213801; Sat, 29 Oct 2011 11:16:53 -0700 (PDT) Received: by 10.180.24.201 with HTTP; Sat, 29 Oct 2011 11:16:53 -0700 (PDT) In-Reply-To: References: <7003D4EE027640E6A49BFC84DD733D7F@Laptop> <20111028174052.GA1034@tiny> <20111029100803.GA96706@e-new.0x20.net> Date: Sat, 29 Oct 2011 23:46:53 +0530 Message-ID: From: Mubeesh ali To: irek-kaenly@yandex.ru Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Matthias Apitz , Lars Engels , freebsd-mobile@freebsd.org Subject: Re: FreeBSD release Acer Aspire 5735Z 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: Sat, 29 Oct 2011 18:42:09 -0000 have seen acers get stuck on boot unless you turn off sata emulation from ahci mode . So may be better to turn off ahci in bios, Not sure if that issue is fixed ... On Sat, Oct 29, 2011 at 7:08 PM, Adrian Chadd wrote: > On 29 October 2011 21:08, Lars Engels wrote: > >> And cross your fingers that the button to enable / disable wireless >> works out of the box. Unfortunately there's no port of Linux' acer_acpi >> [1] to FreeBSD. >> >> [1] http://code.google.com/p/aceracpi/ > > Please please please, can someone port this? > > > > Adrian > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > --=20 Best=A0 Regards, Mubeesh Ali.V.M