From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 19:01:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51EBA16A4CE for ; Mon, 12 Jul 2004 19:01:50 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F302743D31 for ; Mon, 12 Jul 2004 19:01:49 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6CJ1kJU021846; Mon, 12 Jul 2004 15:01:46 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6CJ1cJP021843; Mon, 12 Jul 2004 15:01:46 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Mon, 12 Jul 2004 15:01:38 -0400 (EDT) From: Andre Guibert de Bruet To: Scott Long In-Reply-To: <40F15A41.4070505@samsco.org> Message-ID: <20040712145732.H2496@alpha.siliconlandmark.com> References: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> <40F15A41.4070505@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: ahc driver now borked in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 19:01:50 -0000 Scott, The board in question was an older Asus A7V with BIOS 1007. Upgrading to 1011 fixed the problem. Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > On Sun, 11 Jul 2004, Scott Long wrote: > Andre Guibert de Bruet wrote: >> Jordan, >> >> I have seen something similar on one of my systems just a few days ago. >> ACPI turned out to be the culprit. It would boot with it disabled, and >> wouldn't with until I upgraded the BIOS. > > Does this mean that upgrading the BIOS resulting in everything working with > ACPI again? What system and BIOS versions? > > Scott >