Date: Wed, 28 Feb 2007 22:44:52 +1100 From: Timothy Bourke <timbob@bigpond.com> To: freebsd-current@freebsd.org Subject: Re: psm(4) doesn't work with custom kernel config Message-ID: <20070228114452.GA771@triptrop> In-Reply-To: <20070225184351.GM2479@obiwan.tataz.chchile.org> References: <20070221205331.GB2479@obiwan.tataz.chchile.org> <D6E156A8-586A-4AEF-8FAC-85509C4E344E@siliconlandmark.com> <20070225184351.GM2479@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--6c2NcOVqGQ03X4Wi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Feb 25 at 19:43 +0100, Jeremie Le Hen wrote:
> On Fri, Feb 23, 2007 at 02:49:17AM -0500, Andre Guibert de Bruet wrote:
> > Try booting with ACPI disabled. Something does not appear sane with =20
> > your ACPI config using your custom kernel:
> > acpi: bad write to port 0x080 (32), val 0xaa
>=20
> Indeed, removing device acpi from my custom kernel config file resolves
> the problem. However, if I enable option SMP along ACPI, psm(4) works.
I just had a similar problem on a ThinkPad R52. Adding:
device acpi_ibm
to the kernel config breaks the psm;
but putting:
acpi_ibm_load=3D"YES"
in /boot/loader.conf works.
I don't know why. Perhaps something similar would work with the base
acpi driver?
Tim.
--6c2NcOVqGQ03X4Wi
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)
iD8DBQFF5Ws0tKVK1sFb0ecRAmU3AJ9PQV+WIxRPP/HYaexWq1agpwrBKgCdGuoE
kpBxT1bAhejhqgE5Hkun/ec=
=Dqtc
-----END PGP SIGNATURE-----
--6c2NcOVqGQ03X4Wi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070228114452.GA771>