Date: Sun, 18 Nov 2007 16:58:39 -0800 From: Nate Lawson <nate@root.org> To: Reko Turja <reko.turja@liukuma.net> Cc: freebsd-acpi@freebsd.org Subject: Re: Using ACPI causes panics and crashes on Tyan 1832 tiger 100 Message-ID: <4740DFBF.8010503@root.org> In-Reply-To: <086301c82a45$ed75ced0$0a0aa8c0@endor.swagman.org> References: <078f01c82a3f$8c5e36b0$0a0aa8c0@endor.swagman.org> <4740DAEC.6050308@root.org> <086301c82a45$ed75ced0$0a0aa8c0@endor.swagman.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Reko Turja wrote: > From: "Nate Lawson" <nate@root.org> > To: "Charlie Root" <root@liukuma.net> > Cc: <freebsd-acpi@freebsd.org> > Sent: Monday, November 19, 2007 2:38 AM > Subject: Re: Using ACPI causes panics and crashes on Tyan 1832 tiger 100 > >>> Is there any hope on getting this system running on ACPI, or is the BIOS >>> hosed for good? If I can supply any extra assistance or information I'm >>> at your service and access to the box can be provided if needed. >> >> Upgrade your BIOS to the last known version. If it still has problems, >> it's likely your system does not support acpi. Just set >> hint.acpi.0.disabled="1" in /boot/loader.conf and be done with it. > > BIOS is the latest (from 2001...), the machine in question ran under > ACPI multiprocessor in Windows quite happily though, but I guess FreeBSD > ACPI is a no-go then. Windows has a number of workarounds for buggy systems and if you mean W2K, avoids implementing certain features on such systems. I can either spend time trying to hack around old buggy systems or new ones. I think most users prefer the latter. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4740DFBF.8010503>