From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 01:43:44 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBAC416A4CE for ; Sat, 1 Jan 2005 01:43:43 +0000 (GMT) Received: from silver.teardrop.org (silver.teardrop.org [66.150.202.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C61943D3F for ; Sat, 1 Jan 2005 01:43:43 +0000 (GMT) (envelope-from snow@teardrop.org) Received: by silver.teardrop.org (Postfix, from userid 100) id C86F626C0D; Fri, 31 Dec 2004 20:43:42 -0500 (EST) Date: Fri, 31 Dec 2004 20:43:42 -0500 From: James Snow To: freebsd-mobile@freebsd.org Message-ID: <20050101014342.GA9219@teardrop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Issues with 5.3-p2, Xorg-6.8.1 and ThinkPads? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 01:43:44 -0000 I'm curious to know if anyone has seen abnormally frequent crashes running 5.3-p2 with Xorg-6.8.1 on a ThinkPad. My T22 has begun to be a bit more cantankerous than I'm accustomed to after I portupgraded to Xorg-6.8.1. xli will reliably lock up the X server when scrolling images, for example. Just now it locked up solid in the middle of a portupgrade of Firefox. Unfortunately, my laptop took a small tumble off a sofa shortly after the aforementioned Xorg portupgrade, so it's entirely possible that this is an issue with my hardware. The laptop isn't visibly damaged and doesn't report any obvious errors, so I'm hoping - for my wallet's sake - that it's an issue with the new Xorg. Is anyone with a ThinkPad that hasn't just been dropped seeing any issues? Thanks, -Snow From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 02:12:00 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A2E16A4CE for ; Sat, 1 Jan 2005 02:12:00 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1B643D31 for ; Sat, 1 Jan 2005 02:11:58 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j012Bug06528 for ; Sat, 1 Jan 2005 13:11:56 +1100 (EST) Date: Sat, 1 Jan 2005 13:11:55 +1100 (EST) From: Dave Horsfall To: freebsd-mobile@freebsd.org In-Reply-To: <20050101014342.GA9219@teardrop.org> Message-ID: References: <20050101014342.GA9219@teardrop.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Issues with 5.3-p2, Xorg-6.8.1 and ThinkPads? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 02:12:00 -0000 On Fri, 31 Dec 2004, James Snow wrote: [ ... ] > Is anyone with a ThinkPad that hasn't just been dropped seeing any > issues? There are definitely issues with 6.8.1 and the i810 driver; I could not get X to start on my R31 unless I disabled acceleration. -- Dave From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 02:15:43 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B036B16A4CE for ; Sat, 1 Jan 2005 02:15:43 +0000 (GMT) Received: from sarajevo.pacific.net.sg (sarajevo.pacific.net.sg [203.120.90.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 867E143D2F for ; Sat, 1 Jan 2005 02:15:42 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 23346 invoked from network); 1 Jan 2005 02:15:40 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by sarajevo with SMTP; 1 Jan 2005 02:15:40 -0000 Received: from [192.168.0.109] ([210.24.246.251]) by maxwell2.pacific.net.sg with ESMTP <20050101021540.GLIU1207.maxwell2.pacific.net.sg@[192.168.0.109]>; Sat, 1 Jan 2005 10:15:40 +0800 Message-ID: <41D60825.3000802@pacific.net.sg> Date: Sat, 01 Jan 2005 10:17:09 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Mark A-J. Raught (from the laptop)" References: <41D5911A.6080403@acm.org> In-Reply-To: <41D5911A.6080403@acm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: mobile@freebsd.org Subject: Re: Buying a laptop. (HP, Compaq, or Gateway) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 02:15:43 -0000 Hi, Mark A-J. Raught (from the laptop) wrote: my ideas of a laptop are on the opposite of your scale (small, long battery life ...). All I know is that there is also Acer which offers at least three machines in your class. > > Gateway 7405GX (AMD 64 3200+) > HP zv5320us (AMD XP-M 3000+) > Compaq r3306us (AMD XP-M 3000+) > > On to the big problem; I can't find any info on any of the laptops with > FreeBSD. I checked the usual compatibility web pages, but couldn't find I only have read about the Acer Ferraris. > Extra info: The laptop will be wiped (no windows please) and I will be > running FreeBSD. I have no problem replacing a miniPCI card if need be, FreeBSD is not as good as Windows in a single point: power consumption. Erich From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 05:36:49 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A8EF16A4D0 for ; Sat, 1 Jan 2005 05:36:49 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E088C43D45 for ; Sat, 1 Jan 2005 05:36:48 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Fri, 31 Dec 2004 21:36:48 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3EC1C5D04; Fri, 31 Dec 2004 21:36:48 -0800 (PST) To: James Snow In-reply-to: Your message of "Fri, 31 Dec 2004 20:43:42 EST." <20050101014342.GA9219@teardrop.org> Date: Fri, 31 Dec 2004 21:36:48 -0800 From: "Kevin Oberman" Message-Id: <20050101053648.3EC1C5D04@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Issues with 5.3-p2, Xorg-6.8.1 and ThinkPads? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 05:36:49 -0000 > Date: Fri, 31 Dec 2004 20:43:42 -0500 > From: James Snow > Sender: owner-freebsd-mobile@freebsd.org > > I'm curious to know if anyone has seen abnormally frequent crashes > running 5.3-p2 with Xorg-6.8.1 on a ThinkPad. My T22 has begun to be > a bit more cantankerous than I'm accustomed to after I portupgraded > to Xorg-6.8.1. xli will reliably lock up the X server when scrolling > images, for example. Just now it locked up solid in the middle of a > portupgrade of Firefox. > > Unfortunately, my laptop took a small tumble off a sofa shortly after > the aforementioned Xorg portupgrade, so it's entirely possible that > this is an issue with my hardware. The laptop isn't visibly damaged and > doesn't report any obvious errors, so I'm hoping - for my wallet's sake > - that it's an issue with the new Xorg. > > Is anyone with a ThinkPad that hasn't just been dropped seeing any > issues? My ThinkPad T30 (which has a Radeon M7) has not had any such problems, although it's running 5-Stable, not 5..3. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 10:32:44 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 681D116A4CE for ; Sat, 1 Jan 2005 10:32:44 +0000 (GMT) Received: from over.ru (over.ru [213.247.139.17]) by mx1.FreeBSD.org (Postfix) with SMTP id E90FB43D46 for ; Sat, 1 Jan 2005 10:32:42 +0000 (GMT) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 57419 invoked by uid 65534); 1 Jan 2005 10:31:43 -0000 Received: from over.ru (HELO localhost) (213.247.139.17) by over.ru with SMTP; 1 Jan 2005 10:31:43 -0000 Received: from unknown ([213.247.139.17]) by localhost (over.ru [213.247.139.17]) (amavisd-new, port 10024) with SMTP id 98341-07 for ; Sat, 1 Jan 2005 13:31:35 +0300 (MSK) Received: from unknown (HELO armada) (192.168.1.251) by over.ru with SMTP; 1 Jan 2005 10:31:35 -0000 Received: (qmail 1026 invoked from network); 1 Jan 2005 10:32:29 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by armada with SMTP; 1 Jan 2005 10:32:29 -0000 Date: Sat, 1 Jan 2005 13:32:28 +0300 From: Alex Povolotsky To: freebsd-mobile@freebsd.org Message-ID: <20050101133228.663d0ef9@localhost> In-Reply-To: <200412311138.32041.jhb@FreeBSD.org> References: <20041231100844.6a6e199b@tarkhil.over.ru> <200412311138.32041.jhb@FreeBSD.org> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at over.ru Subject: Re: pccardd in 5.3 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 10:32:44 -0000 On Fri, 31 Dec 2004 11:38:30 -0500 John Baldwin wrote: > Is your network card already working? (That is, does it probe and attach when > you plug it in?) If so, you don't need to use pccardd. FreeBSD 5.x uses a > completely different driver for all of the pccard stuff that supports most > laptops. Only some older non-cardbus laptops need the OLDCARD stuff that > uses pccardd IIRC. Okay, thanks; but how can I automatically run ifconfig when I attach a card? -- Alex Povolotsky SwissCom From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 12:22:33 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10E6A16A4CE for ; Sat, 1 Jan 2005 12:22:33 +0000 (GMT) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 151CE43D2D for ; Sat, 1 Jan 2005 12:22:32 +0000 (GMT) (envelope-from gogo@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.13.2/2004121700) with ESMTP id j01CMU7J007502; Sat, 1 Jan 2005 13:22:30 +0100 (CET) Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by cs.uni-sb.de (8.13.2/2004121700) with ESMTP id j01CMTns016539; Sat, 1 Jan 2005 13:22:29 +0100 (CET) Received: from xantippe (xantippe.cs.uni-sb.de [134.96.240.13]) by mail.cs.uni-sb.de (8.13.2/2004121700) with ESMTP id j01CMSg5019122; Sat, 1 Jan 2005 13:22:28 +0100 (CET) X-Authentication-Warning: mail.cs.uni-sb.de: Host xantippe.cs.uni-sb.de [134.96.240.13] claimed to be xantippe Received: from eugene.cs.uni-sb.de (localhost) [134.96.240.6] (Debian))id 1CkiH5-0005TF-00; Sat, 01 Jan 2005 13:22:27 +0100 From: Robert Gogolok To: freebsd-mobile@freebsd.org Date: Sat, 1 Jan 2005 13:23:12 +0100 User-Agent: KMail/1.7.1 References: <20050101014342.GA9219@teardrop.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5845192.RlNTdyZKRM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501011323.15954.gogo@cs.uni-sb.de> cc: Dave Horsfall Subject: Re: Issues with 5.3-p2, Xorg-6.8.1 and ThinkPads? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 12:22:33 -0000 --nextPart5845192.RlNTdyZKRM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 01 January 2005 03:11, Dave Horsfall wrote: > There are definitely issues with 6.8.1 and the i810 driver; I could not > get X to start on my R31 unless I disabled acceleration. I also use the i810 driver (on sony PCG-R600HMP). Since xorg 6.8.1 I can't = get=20 my X working. Could you send me your xorg.conf? Or what do you mean by disabling=20 acceleration? (See below, it seems it is enabled here too, but I don't know= =20 how to disable it.) I first disabled "glx" and "dri", enabled SWcursor, and the startup attempt= =20 gives the following: http://w5.cs.uni-sb.de/~gogo/screenshots/Xorg.0.log Do you mean by acceleration this line (in the Xorg.0.log file at the end)? <<< II) I810(0): Using XFree86 Acceleration Architecture (XAA) >>> My config is: http://w5.cs.uni-sb.de/~gogo/screenshots/xorg.conf Greetings, Robert! =2D-=20 JID: gogo@jabber.cs.uni-sb.de --nextPart5845192.RlNTdyZKRM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBB1pYzxdrCMIgl4fURAqkCAJ0fGAAI5bu5lXRNUx96dmXmsJKCkwCePlzw W9Rse/7E+t7RkReB/xjCiBE= =7wu4 -----END PGP SIGNATURE----- --nextPart5845192.RlNTdyZKRM-- From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 14:05:59 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A26416A4CE for ; Sat, 1 Jan 2005 14:05:59 +0000 (GMT) Received: from silver.teardrop.org (silver.teardrop.org [66.150.202.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8FB643D2F for ; Sat, 1 Jan 2005 14:05:58 +0000 (GMT) (envelope-from snow@teardrop.org) Received: by silver.teardrop.org (Postfix, from userid 100) id 3773D26C0D; Sat, 1 Jan 2005 09:05:58 -0500 (EST) Date: Sat, 1 Jan 2005 09:05:58 -0500 From: James Snow To: freebsd-mobile@freebsd.org Message-ID: <20050101140557.GA13568@teardrop.org> References: <20050101014342.GA9219@teardrop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050101014342.GA9219@teardrop.org> User-Agent: Mutt/1.4.1i Subject: Re: Issues with 5.3-p2, Xorg-6.8.1 and ThinkPads? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 14:05:59 -0000 On Fri, Dec 31, 2004 at 08:43:42PM -0500, James Snow wrote: > > xli will reliably lock up the X server when scrolling images, for > example. After portupgrading from xorg-libraries-6.8.1 to xorg-libraries-6.8.1_1 I am no longer able to cause this crash in xli. I think that perhaps my laptop is OK and there was something funny going on with xorg. http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/xorg-libraries/Makefile Thanks for the responses. -Snow From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 17:25:45 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A730B16A4CE for ; Sat, 1 Jan 2005 17:25:45 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88EE343D4C for ; Sat, 1 Jan 2005 17:25:45 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Sat, 01 Jan 2005 09:25:44 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9BB655D04; Sat, 1 Jan 2005 09:25:44 -0800 (PST) To: Alex Povolotsky In-reply-to: Your message of "Sat, 01 Jan 2005 13:32:28 +0300." <20050101133228.663d0ef9@localhost> Date: Sat, 01 Jan 2005 09:25:44 -0800 From: "Kevin Oberman" Message-Id: <20050101172544.9BB655D04@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: pccardd in 5.3 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 17:25:45 -0000 > Date: Sat, 1 Jan 2005 13:32:28 +0300 > From: Alex Povolotsky > Sender: owner-freebsd-mobile@freebsd.org > > On Fri, 31 Dec 2004 11:38:30 -0500 > John Baldwin wrote: > > > Is your network card already working? (That is, does it probe and attach when > > you plug it in?) If so, you don't need to use pccardd. FreeBSD 5.x uses a > > completely different driver for all of the pccard stuff that supports most > > laptops. Only some older non-cardbus laptops need the OLDCARD stuff that > > uses pccardd IIRC. > > Okay, thanks; but how can I automatically run ifconfig when I attach a card? This is now handled by devd. See /etc/devd.conf for the attach and detach. Basically, it calls pccard_ether to startx the device and that does most of the work. Added, custom setup comes from start_if.int, just as is done in V4. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 18:18:26 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1337316A4CE for ; Sat, 1 Jan 2005 18:18:26 +0000 (GMT) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C24743D1D for ; Sat, 1 Jan 2005 18:18:25 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 39197 invoked by uid 1005); 1 Jan 2005 18:18:23 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.22 Clear:RC:1(217.235.145.232):. Processed in 0.212099 secs); 01 Jan 2005 18:18:23 -0000 Received: from unknown (HELO ?192.168.1.10?) (rainer@ultra-secure.de@217.235.145.232) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jan 2005 18:18:23 -0000 Message-ID: <41D6F77A.1030905@ultra-secure.de> Date: Sat, 01 Jan 2005 20:18:18 +0100 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mobile@freebsd.org References: <41D5911A.6080403@acm.org> <41D60825.3000802@pacific.net.sg> In-Reply-To: <41D60825.3000802@pacific.net.sg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Buying a laptop. (HP, Compaq, or Gateway) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 18:18:26 -0000 Erich Dollansky wrote: > Hi, > > Mark A-J. Raught (from the laptop) wrote: > > my ideas of a laptop are on the opposite of your scale (small, long > battery life ...). > Indeed. > All I know is that there is also Acer which offers at least three > machines in your class. > >> >> Gateway 7405GX (AMD 64 3200+) >> HP zv5320us (AMD XP-M 3000+) >> Compaq r3306us (AMD XP-M 3000+) >> >> On to the big problem; I can't find any info on any of the laptops >> with FreeBSD. I checked the usual compatibility web pages, but >> couldn't find > > > I only have read about the Acer Ferraris. > I'd also be wary about consumer-grade laptops. The customer-service is often non-existant and the low price comes with (more often than not) ultra-low quality - just search Google for your favourite laptop-brand, together with the word "hinges"...) My advice, if you need the laptop to earn money, is to set for a business-model (like HP NX7010 or so - the FSC E8010 I own will not be so easy to get where you live, I'm afraid). You can buy additional warranty, too. I've only seen Acer PCs, end they seemed less than stellar. >> Extra info: The laptop will be wiped (no windows please) and I will >> be running FreeBSD. I have no problem replacing a miniPCI card if >> need be, > > > FreeBSD is not as good as Windows in a single point: power consumption. It's even worse than Linux (SuSE 9.2). At least on my Fujitsu-Siemens E8010. But SuSE totally drops the ball in the ACPI-departement. I can at least suspend-to-RAM with 5.3 (unfortunately not -to-disk), but SuSE 9.2 doesn't even do that. Well, it can suspend to RAM, but the SuSE doesn't wake-up anymore. Or it wakes up and shows only a black screen. FreeBSD works very good in that specific area. cheers, Rainer -- =================================================== ~ Rainer Duffner - rainer@ultra-secure.de ~ ~ Freising - Munich - Germany ~ ~ Unix - Linux - BSD - OpenSource - Security ~ ~ http://www.ultra-secure.de/~rainer/pubkey.pgp ~ =================================================== From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 1 19:20:01 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B95A316A4CE for ; Sat, 1 Jan 2005 19:20:01 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C47B43D1D for ; Sat, 1 Jan 2005 19:20:01 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Sat, 01 Jan 2005 11:20:00 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 2923F5D04; Sat, 1 Jan 2005 11:20:00 -0800 (PST) X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Rainer Duffner In-reply-to: Your message of "Sat, 01 Jan 2005 20:18:18 +0100." <41D6F77A.1030905@ultra-secure.de> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_20371033920" Date: Sat, 01 Jan 2005 11:20:00 -0800 From: "Kevin Oberman" Message-Id: <20050101192000.2923F5D04@ptavv.es.net> cc: mobile@freebsd.org Subject: Re: Buying a laptop. (HP, Compaq, or Gateway) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 19:20:01 -0000 This is a multipart MIME message. --==_Exmh_20371033920 Content-Type: text/plain; charset=us-ascii > Date: Sat, 01 Jan 2005 20:18:18 +0100 > From: Rainer Duffner > Sender: owner-freebsd-mobile@freebsd.org > > Erich Dollansky wrote: > > > Hi, > > > > Mark A-J. Raught (from the laptop) wrote: > > > > my ideas of a laptop are on the opposite of your scale (small, long > > battery life ...). > > > > > Indeed. > > > > All I know is that there is also Acer which offers at least three > > machines in your class. > > > >> > >> Gateway 7405GX (AMD 64 3200+) > >> HP zv5320us (AMD XP-M 3000+) > >> Compaq r3306us (AMD XP-M 3000+) > >> > >> On to the big problem; I can't find any info on any of the laptops > >> with FreeBSD. I checked the usual compatibility web pages, but > >> couldn't find > > > > > > I only have read about the Acer Ferraris. > > > > > I'd also be wary about consumer-grade laptops. > The customer-service is often non-existant and the low price comes with > (more often than not) ultra-low quality - just search Google for your > favourite laptop-brand, together with the word "hinges"...) > My advice, if you need the laptop to earn money, is to set for a > business-model (like HP NX7010 or so - the FSC E8010 I own will not be > so easy to get where you live, I'm afraid). > You can buy additional warranty, too. > I've only seen Acer PCs, end they seemed less than stellar. > > > >> Extra info: The laptop will be wiped (no windows please) and I will > >> be running FreeBSD. I have no problem replacing a miniPCI card if > >> need be, > > > > > > FreeBSD is not as good as Windows in a single point: power consumption. > > > > It's even worse than Linux (SuSE 9.2). At least on my Fujitsu-Siemens E8010. > But SuSE totally drops the ball in the ACPI-departement. I can at least > suspend-to-RAM with 5.3 (unfortunately not -to-disk), but SuSE 9.2 > doesn't even do that. > Well, it can suspend to RAM, but the SuSE doesn't wake-up anymore. Or it > wakes up and shows only a black screen. > FreeBSD works very good in that specific area. If you are running 5.3, you might try the acpi_pwr5 patch that njl@ posted about a month ago. It will substantially improve power performance in FreeBSD. It may (or may not) help with resume from suspend, I'll attach it an see of it makes it through the mailing list. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 --==_Exmh_20371033920 Content-Type: text/plain ; name="acpi_pwr5.diff"; charset=us-ascii Content-Description: acpi_pwr5.diff Content-Disposition: attachment; filename="acpi_pwr5.diff" Index: sys/dev/acpica/acpi.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v retrieving revision 1.186.2.6 diff -u -r1.186.2.6 acpi.c --- sys/dev/acpica/acpi.c 7 Nov 2004 20:24:05 -0000 1.186.2.6 +++ sys/dev/acpica/acpi.c 30 Nov 2004 20:32:31 -0000 @@ -59,6 +59,10 @@ #include #include +#include "pci_if.h" +#include +#include + MALLOC_DEFINE(M_ACPIDEV, "acpidev", "ACPI devices"); /* Hooks for the ACPI CA debugging infrastructure */ @@ -87,10 +91,14 @@ static void acpi_identify(driver_t *driver, device_t parent); static int acpi_probe(device_t dev); static int acpi_attach(device_t dev); +static int acpi_suspend(device_t dev); +static int acpi_resume(device_t dev); static int acpi_shutdown(device_t dev); static device_t acpi_add_child(device_t bus, int order, const char *name, int unit); static int acpi_print_child(device_t bus, device_t child); +static void acpi_probe_nomatch(device_t bus, device_t child); +static void acpi_driver_added(device_t dev, driver_t *driver); static int acpi_read_ivar(device_t dev, device_t child, int index, uintptr_t *result); static int acpi_write_ivar(device_t dev, device_t child, int index, @@ -110,10 +118,14 @@ static ACPI_STATUS acpi_device_eval_obj(device_t bus, device_t dev, ACPI_STRING pathname, ACPI_OBJECT_LIST *parameters, ACPI_BUFFER *ret); +static int acpi_device_pwr_for_sleep(device_t bus, device_t dev, + int *dstate); static ACPI_STATUS acpi_device_scan_cb(ACPI_HANDLE h, UINT32 level, void *context, void **retval); static ACPI_STATUS acpi_device_scan_children(device_t bus, device_t dev, int max_depth, acpi_scan_cb_t user_fn, void *arg); +static int acpi_set_powerstate_method(device_t bus, device_t child, + int state); static int acpi_isa_pnp_probe(device_t bus, device_t child, struct isa_pnp_id *ids); static void acpi_probe_children(device_t bus); @@ -145,12 +157,14 @@ DEVMETHOD(device_attach, acpi_attach), DEVMETHOD(device_shutdown, acpi_shutdown), DEVMETHOD(device_detach, bus_generic_detach), - DEVMETHOD(device_suspend, bus_generic_suspend), - DEVMETHOD(device_resume, bus_generic_resume), + DEVMETHOD(device_suspend, acpi_suspend), + DEVMETHOD(device_resume, acpi_resume), /* Bus interface */ DEVMETHOD(bus_add_child, acpi_add_child), DEVMETHOD(bus_print_child, acpi_print_child), + DEVMETHOD(bus_probe_nomatch, acpi_probe_nomatch), + DEVMETHOD(bus_driver_added, acpi_driver_added), DEVMETHOD(bus_read_ivar, acpi_read_ivar), DEVMETHOD(bus_write_ivar, acpi_write_ivar), DEVMETHOD(bus_get_resource_list, acpi_get_rlist), @@ -160,7 +174,6 @@ DEVMETHOD(bus_release_resource, acpi_release_resource), DEVMETHOD(bus_child_pnpinfo_str, acpi_child_pnpinfo_str_method), DEVMETHOD(bus_child_location_str, acpi_child_location_str_method), - DEVMETHOD(bus_driver_added, bus_generic_driver_added), DEVMETHOD(bus_activate_resource, bus_generic_activate_resource), DEVMETHOD(bus_deactivate_resource, bus_generic_deactivate_resource), DEVMETHOD(bus_setup_intr, bus_generic_setup_intr), @@ -169,8 +182,12 @@ /* ACPI bus */ DEVMETHOD(acpi_id_probe, acpi_device_id_probe), DEVMETHOD(acpi_evaluate_object, acpi_device_eval_obj), + DEVMETHOD(acpi_pwr_for_sleep, acpi_device_pwr_for_sleep), DEVMETHOD(acpi_scan_children, acpi_device_scan_children), + /* PCI emulation */ + DEVMETHOD(pci_set_powerstate, acpi_set_powerstate_method), + /* ISA emulation */ DEVMETHOD(isa_pnp_probe, acpi_isa_pnp_probe), @@ -212,6 +229,12 @@ static int acpi_serialize_methods; TUNABLE_INT("hw.acpi.serialize_methods", &acpi_serialize_methods); +/* Power devices off and on in suspend and resume. XXX Remove once tested. */ +static int acpi_do_powerstate = 1; +TUNABLE_INT("debug.acpi.do_powerstate", &acpi_do_powerstate); +SYSCTL_INT(_debug_acpi, OID_AUTO, do_powerstate, CTLFLAG_RW, + &acpi_do_powerstate, 1, "Turn off devices when suspending."); + /* * ACPI can only be loaded as a module by the loader; activating it after * system bootstrap time is not useful, and can be fatal to the system. @@ -570,6 +593,72 @@ } static int +acpi_suspend(device_t dev) +{ + struct acpi_softc *sc; + device_t child, *devlist; + int error, i, numdevs, pstate; + + /* First give child devices a chance to suspend. */ + error = bus_generic_suspend(dev); + if (error) + return (error); + + /* + * Now, set them into the appropriate power state, usually D3. If the + * device has an _SxD method for the next sleep state, use that power + * state instead. + */ + sc = device_get_softc(dev); + device_get_children(dev, &devlist, &numdevs); + for (i = 0; i < numdevs; i++) { + /* If the device is not attached, we've powered it down elsewhere. */ + child = devlist[i]; + if (!device_is_attached(child)) + continue; + + /* + * Default to D3 for all sleep states. The _SxD method is optional + * so set the powerstate even if it's absent. + */ + pstate = PCI_POWERSTATE_D3; + error = acpi_device_pwr_for_sleep(device_get_parent(child), + child, &pstate); + if ((error == 0 || error == ESRCH) && acpi_do_powerstate) + pci_set_powerstate(child, pstate); + } + free(devlist, M_TEMP); + error = 0; + + return (error); +} + +static int +acpi_resume(device_t dev) +{ + ACPI_HANDLE handle; + int i, numdevs; + device_t child, *devlist; + + /* + * Put all devices in D0 before resuming them. Call _S0D on each one + * since some systems expect this. + */ + device_get_children(dev, &devlist, &numdevs); + for (i = 0; i < numdevs; i++) { + child = devlist[i]; + handle = acpi_get_handle(child); + if (handle) + AcpiEvaluateObject(handle, "_S0D", NULL, NULL); + if (device_is_attached(child) && acpi_do_powerstate) + pci_set_powerstate(child, PCI_POWERSTATE_D0); + } + free(devlist, M_TEMP); + + return (bus_generic_resume(dev)); +} + +static int acpi_shutdown(device_t dev) { @@ -624,6 +713,45 @@ return (retval); } +/* + * If this device is an ACPI child but no one claimed it, attempt + * to power it off. We'll power it back up when a driver is added. + * + * XXX Disabled for now since many necessary devices (like fdc and + * ATA) don't claim the devices we created for them but still expect + * them to be powered up. + */ +static void +acpi_probe_nomatch(device_t bus, device_t child) +{ + + /* pci_set_powerstate(child, PCI_POWERSTATE_D3); */ +} + +/* + * If a new driver has a chance to probe a child, first power it up. + * + * XXX Disabled for now (see acpi_probe_nomatch for details). + */ +static void +acpi_driver_added(device_t dev, driver_t *driver) +{ + device_t child, *devlist; + int i, numdevs; + + DEVICE_IDENTIFY(driver, dev); + device_get_children(dev, &devlist, &numdevs); + for (i = 0; i < numdevs; i++) { + child = devlist[i]; + if (device_get_state(child) == DS_NOTPRESENT) { + /* pci_set_powerstate(child, PCI_POWERSTATE_D0); */ + if (device_probe_and_attach(child) != 0) + ; /* pci_set_powerstate(child, PCI_POWERSTATE_D3); */ + } + } + free(devlist, M_TEMP); +} + /* Location hint for devctl(8) */ static int acpi_child_location_str_method(device_t cbdev, device_t child, char *buf, @@ -1064,6 +1192,57 @@ return (AcpiEvaluateObject(h, pathname, parameters, ret)); } +static int +acpi_device_pwr_for_sleep(device_t bus, device_t dev, int *dstate) +{ + struct acpi_softc *sc; + ACPI_HANDLE handle; + ACPI_STATUS status; + char sxd[8]; + int error; + + sc = device_get_softc(bus); + handle = acpi_get_handle(dev); + + /* + * XXX If we find these devices, don't try to power them down. + * The serial and IRDA ports on my T23 hang the system when + * set to D3 and it appears that such legacy devices may + * need special handling in their drivers. + */ + if (handle == NULL || + acpi_MatchHid(handle, "PNP0500") || + acpi_MatchHid(handle, "PNP0501") || + acpi_MatchHid(handle, "PNP0502") || + acpi_MatchHid(handle, "PNP0510") || + acpi_MatchHid(handle, "PNP0511")) + return (ENXIO); + + /* + * Override next state with the value from _SxD, if present. If no + * dstate argument was provided, don't fetch the return value. + */ + snprintf(sxd, sizeof(sxd), "_S%dD", sc->acpi_sstate); + if (dstate) + status = acpi_GetInteger(handle, sxd, dstate); + else + status = AcpiEvaluateObject(handle, sxd, NULL, NULL); + + switch (status) { + case AE_OK: + error = 0; + break; + case AE_NOT_FOUND: + error = ESRCH; + break; + default: + error = ENXIO; + break; + } + + return (error); +} + /* Callback arg for our implementation of walking the namespace. */ struct acpi_device_scan_ctx { acpi_scan_cb_t user_fn; @@ -1138,6 +1317,34 @@ acpi_device_scan_cb, &ctx, NULL)); } +/* + * Even though ACPI devices are not PCI, we use the PCI approach for setting + * device power states since it's close enough to ACPI. + */ +static int +acpi_set_powerstate_method(device_t bus, device_t child, int state) +{ + ACPI_HANDLE h; + ACPI_STATUS status; + int error; + + error = 0; + h = acpi_get_handle(child); + if (state < ACPI_STATE_D0 || state > ACPI_STATE_D3) + return (EINVAL); + if (h == NULL) + return (0); + + /* Ignore errors if the power methods aren't present. */ + status = acpi_pwr_switch_consumer(h, state); + if (ACPI_FAILURE(status) && status != AE_NOT_FOUND + && status != AE_BAD_PARAMETER) + device_printf(bus, "failed to set ACPI power state D%d on %s: %s\n", + state, acpi_name(h), AcpiFormatException(status)); + + return (error); +} + static int acpi_isa_pnp_probe(device_t bus, device_t child, struct isa_pnp_id *ids) { Index: sys/dev/acpica/acpi_if.m =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_if.m,v retrieving revision 1.2 diff -u -r1.2 acpi_if.m --- sys/dev/acpica/acpi_if.m 15 Jul 2004 16:29:08 -0000 1.2 +++ sys/dev/acpica/acpi_if.m 30 Nov 2004 20:32:31 -0000 @@ -109,6 +109,26 @@ }; # +# Get the highest power state (D0-D3) that is usable for a device when +# suspending/resuming. If a bus calls this when suspending a device, it +# must also call it when resuming. +# +# device_t bus: parent bus for the device +# +# device_t dev: check this device's appropriate power state +# +# int *dstate: if successful, contains the highest valid sleep state +# +# Returns: 0 on success, ESRCH if device has no special state, or +# some other error value. +# +METHOD int pwr_for_sleep { + device_t bus; + device_t dev; + int *dstate; +}; + +# # Rescan a subtree and optionally reattach devices to handles. Users # specify a callback that is called for each ACPI_HANDLE of type Device # that is a child of "dev". Index: sys/dev/pci/pci.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v retrieving revision 1.264 diff -u -r1.264 pci.c --- sys/dev/pci/pci.c 2 Jul 2004 13:42:36 -0000 1.264 +++ sys/dev/pci/pci.c 30 Nov 2004 20:33:15 -0000 @@ -60,6 +60,10 @@ #include "pcib_if.h" #include "pci_if.h" +#include +#include +#include "acpi_if.h" + static uint32_t pci_mapbase(unsigned mapreg); static int pci_maptype(unsigned mapreg); static int pci_mapsize(unsigned testval); @@ -169,15 +173,15 @@ SYSCTL_NODE(_hw, OID_AUTO, pci, CTLFLAG_RD, 0, "PCI bus tuning parameters"); static int pci_enable_io_modes = 1; -TUNABLE_INT("hw.pci.enable_io_modes", (int *)&pci_enable_io_modes); +TUNABLE_INT("hw.pci.enable_io_modes", &pci_enable_io_modes); SYSCTL_INT(_hw_pci, OID_AUTO, enable_io_modes, CTLFLAG_RW, &pci_enable_io_modes, 1, "Enable I/O and memory bits in the config register. Some BIOSes do not\n\ enable these bits correctly. We'd like to do this all the time, but there\n\ are some peripherals that this causes problems with."); -static int pci_do_powerstate = 0; -TUNABLE_INT("hw.pci.do_powerstate", (int *)&pci_do_powerstate); +static int pci_do_powerstate = 1; +TUNABLE_INT("hw.pci.do_powerstate", &pci_do_powerstate); SYSCTL_INT(_hw_pci, OID_AUTO, do_powerstate, CTLFLAG_RW, &pci_do_powerstate, 0, "Power down devices into D3 state when no driver attaches to them.\n\ @@ -1015,43 +1019,78 @@ int pci_suspend(device_t dev) { - int numdevs; - device_t *devlist; - device_t child; + int dstate, error, i, numdevs; + device_t acpi_dev, child, *devlist; struct pci_devinfo *dinfo; - int i; /* - * Save the pci configuration space for each child. We don't need - * to do this, unless the BIOS suspend code powers down the bus and - * the devices on the bus. + * Save the PCI configuration space for each child and set the + * device in the appropriate power state for this sleep state. */ + acpi_dev = NULL; + if (pci_do_powerstate) + acpi_dev = devclass_get_device(devclass_find("acpi"), 0); device_get_children(dev, &devlist, &numdevs); for (i = 0; i < numdevs; i++) { child = devlist[i]; dinfo = (struct pci_devinfo *) device_get_ivars(child); pci_cfg_save(child, dinfo, 0); } + + /* Suspend devices before potentially powering them down. */ + error = bus_generic_suspend(dev); + if (error) + return (error); + + /* + * Always set the device to D3. If ACPI suggests a different + * power state, use it instead. If ACPI is not present, the + * firmware is responsible for managing device power. Skip + * children who aren't attached since they are powered down + * separately. Only manage type 0 devices for now. + */ + for (i = 0; acpi_dev && i < numdevs; i++) { + child = devlist[i]; + dinfo = (struct pci_devinfo *) device_get_ivars(child); + if (device_is_attached(child) && dinfo->cfg.hdrtype == 0) { + dstate = PCI_POWERSTATE_D3; + ACPI_PWR_FOR_SLEEP(acpi_dev, child, &dstate); + pci_set_powerstate(child, dstate); + } + } free(devlist, M_TEMP); - return (bus_generic_suspend(dev)); + return (0); } int pci_resume(device_t dev) { - int numdevs; - device_t *devlist; - device_t child; + int i, numdevs; + device_t acpi_dev, child, *devlist; struct pci_devinfo *dinfo; - int i; /* - * Restore the pci configuration space for each child. + * Set each child to D0 and restore its PCI configuration space. */ + acpi_dev = NULL; + if (pci_do_powerstate) + acpi_dev = devclass_get_device(devclass_find("acpi"), 0); device_get_children(dev, &devlist, &numdevs); for (i = 0; i < numdevs; i++) { + /* + * Notify ACPI we're going to D0 but ignore the result. If + * ACPI is not present, the firmware is responsible for + * managing device power. Only manage type 0 devices for now. + */ child = devlist[i]; dinfo = (struct pci_devinfo *) device_get_ivars(child); + if (acpi_dev && device_is_attached(child) && + dinfo->cfg.hdrtype == 0) { + ACPI_PWR_FOR_SLEEP(acpi_dev, child, NULL); + pci_set_powerstate(child, PCI_POWERSTATE_D0); + } + + /* Now the device is powered up, restore its config space. */ pci_cfg_restore(child, dinfo); } free(devlist, M_TEMP); --==_Exmh_20371033920--