Re: /proc/acpi/battery

"Francisco J. Guidi Moggia" <[email protected]> Mon, 25 Aug 2003 21:32:04 -0400
Newsgroups gmane.linux.hardware.sony
Message-ID <[email protected]>
--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 25, 2003 at 09:25:50PM -0400, Francisco J. Guidi Moggia wrote:
> On Mon, Aug 25, 2003 at 05:58:53PM -0500, Kimbrell, Roy wrote:
> > Yes, I have other /proc/acpi directories:
> >=20
> > embedded_controller
> > power_resource
> >=20
> > I'm pretty sure acpi is running.  I went through that when I was=20
> > building kernels.  I found out that if apm was configured, acpi wouldn'=
t=20
> > run.  I get acpi messages in /var/log/messages that indicate that acpi=
=20
> > is mapping the interrupts and so on.
> Absolutely remove APM from kernel; don't leave it there, not even as
> modules.
>=20
> > >>>>>I get "No such device."  No messages in dmesg or
> > >>>>>/var/log/messages. More specifically, I get
> > >>>>>
> > >>>>>/lib/modules/2.4.21/kernel/drivers/acpi/battery.o: init_module:=20
> Have you tried patching the kernel 2.4.21 tree with kernel.org's
> 2.4.22rc2 patch and then applying acpi's (http://sf.net/projects/acpi)
> 2.4.22rc2_to_20030813 patch? if that doesn't work try the kernel.org's
> 2.4.22rc3 patch which I'm almost sure includes the latest acpi stuff.
>=20
> The error you are getting has nothing to do with acpid, for it is a
> low level error (kernel unable to find the battery "device").
>=20
> You might also try to recompile the kernel including the battery part (not
> as a module).
Didn't realize, 2.4.22 its out (today), compile that and enable ACPI,
try as kernel part and as modules (do not enable APM).

Greetings,
--=20
Francisco J. Guidi Moggia
[email protected]
http://www.guidi.com

--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/SriUZC4WAbFE+VsRArZlAJwKZdTTzX3fGBWl4uRU9BwYGU2SFgCgvuXX
fADmzO4JCVdKDFdOb8CehSE=
=XIsj
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--