From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 31 18:37:37 2004 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 3611E16A4CE for ; Wed, 31 Mar 2004 18:37:37 -0800 (PST) Received: from krusty.eaglequest.com (krusty.eaglequest.com [209.103.128.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C47F43D49 for ; Wed, 31 Mar 2004 18:37:36 -0800 (PST) (envelope-from jjy@eaglequest.com) Received: (qmail 91696 invoked from network); 1 Apr 2004 03:06:49 -0000 Received: from unknown (HELO eaglequest.com) (216.234.125.10) by krusty.eaglequest.com with SMTP; 1 Apr 2004 03:06:49 -0000 Message-ID: <406B814C.2020408@eaglequest.com> Date: Wed, 31 Mar 2004 21:41:16 -0500 From: James User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: XFree86@XFree86.org Subject: FreeBSD 5.2.1 and XFree86-4.x ati driver lockup problem -- Solution 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: Thu, 01 Apr 2004 02:37:37 -0000 To the FreeBSD team, I struggled with this one for quite a while before figuring it out, so here goes... I had been using FreeBSD 4x for quite some time on my Compaq Presario 1800. And, XFree86-3.6x worked nicely with the laptop's ATI Rage Mobility graphics chip. Unfortunately, the FreeBSD 4x branch didn't support the Atheros chipsets in some of the newer networking cards like the Netgear WG511, so I upgraded to FreeBSD 5.2.1. After that, I couldn't get XFree86-4x to work reliably with my laptop. It turned out that the X instability, which included complete system lockup, was caused by the ACPI module being loaded upon boot-up. Sometimes the Xserver would start-up sometimes not. Also, there was a guaranteed system lockup if you exited Xwindows and then re-entered Xwindows at a later time. In other words, you only got one Xsession per boot! So, after trying all sorts of things in XF86Config, and upgrading to XFree86-4.4 from XFree86-4.3 it turned out that all I needed to do was add the following line to my /boot/device.hints file... hint.acpi.0.disabled="1" After that everything worked great! Xwindows is stable, and my new Netgear WG511 card is working like a charm. By the way the "beastie" menu incorrectly shows "boot with ACPI enabled" as it's second choice. In actuality it disables ACPI! That's how I first solved the problem -- by booting with beastie-menue item "2" selected, finding Xwindows working correctly for a change, and then doing a kldstat to find that the acpi.ko kernel module wasn't loaded. Best regards, and thanks for the great operating system! Jim Yuzwalk