From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 10:20: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 5AC1816A4CE for ; Sat, 10 Jan 2004 10:20:50 -0800 (PST) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id D44A243D5D for ; Sat, 10 Jan 2004 10:20:45 -0800 (PST) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1AfNiz-0008Q4-00; Sat, 10 Jan 2004 19:20:41 +0100 Date: Sat, 10 Jan 2004 19:20:41 +0100 To: Peter Schultz Message-ID: <20040110182041.GX14031@poupinou.org> References: <3FFFD0C5.9070508@web.de> <40001321.4060908@bis.midco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40001321.4060908@bis.midco.net> User-Agent: Mutt/1.5.4i From: Ducrot Bruno cc: freebsd-current@freebsd.org cc: stef Subject: Re: ACPI error message FreeBSD 5.2-RC2 ABIT BP6 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: Sat, 10 Jan 2004 18:20:50 -0000 On Sat, Jan 10, 2004 at 08:58:41AM -0600, Peter Schultz wrote: > stef wrote: > >Pawel Worach : "ACPI errors on my desktop PC (floppy not found)" > > >Take a look at PR kern/48494, there is a patch for the AML there for > > >the ABIT BP6 board. I belive other ABIT boards have the similar > > >Store(Local0, Local0) problem. That fixed the floppy problem for me. > > > >my abit.dsdt looks maybe different. > >i got : > > > > Maybe your BIOS revision is different? > > There's this patch: > http://acpi.sourceforge.net/dsdt/view.php?id=129 > > You could also try fixing the errors and warnings yourself. ;-) > > http://www.cpqlinux.com/acpi-howto.html#fix_broken_dsdt > I remember that someone had that in a asl: Scope (\_PR) { Processor (\_PR.CPU, ...) {...} ... } Just replacing CPU by CPU0 solved a thermal trouble initialization IIRC. -- Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care.