Re: [ACPI-sppt] inspiron 2500

On Sun, 2003-09-21 at 14:11, Derek Broughton wrote:
> >
> > I have an inspiron 2500 that I am trying to get working with acpi.  sleep
> mose
> > P1 works just fine.  But I dont have any batter support, and the
> 
> Me too.   I've been looking at it, on and off, for two years now...  The
> DSDT in the bios has no battery support - because it's broken.  If you've
> recompiled the DSDT, then I think you have to have fixed it enough to at
> least have minimal battery support.  However, if you've just got it fixed
> enough to compile, you still won't have a workable
> /proc/acpi/battery/BAT0/info, which is where most of the information you
> want is found.
> 

It works!  I recompiled the kernel with all the battery/button/etc. in
the kernel and not as modules.  I also rebuilt the DSDT.  But I think
the key was the kernel recompile because after that everything showed up
with 'dmesg'. Plus there was only about 2 bugs in the DSDT, so that
shouldn't have blocked everything.


> >  anyway my proc dir is like this
> >
> > /proc/acpi/
> > /proc/acpi/alarm
> > /proc/acpi/dsdt
> > /proc/acpi/event
> > /proc/acpi/fadt
> > /proc/acpi/sleep
> > /proc/acpi/power_resource/
> > /proc/acpi/embedded_controller/EC0/info
> 
> What version of ACPI are you using, and which BIOS?  I don't have a
> power_resource - I have an ac_adapter and a battery.  Did you compile the
> ACPI modules into the kernel, or as separate modules?  If they're modules,
> you probably haven't insmodded the battery (can't remember what it's called,
> because I found in the early days that I _had_ to compile them into the
> kernel or I'd get a segfault).

yes, the batt applet would segfault if the driver is not there.  Once I
saw that it worked when built in, i realized that probably I needed to
do modprobe or insmod on the modules...

kernel 2.4.20-9
acpi-20021212-2.4.20.diff (I think I had to manually do one of the
failed hunks)
linux-2.4.18-acpi-20020709-dsdt.patch
BIOS A14 (I think, its the latest as of today-its old anyway)

> >
> > Also, acpid tells you to use events, but conviently does not tell you what
> > events exist, nor where to find it out. Any idea??
> 
> Well, when you install acpid the default script logs all the events received
> in /proc/acpi/events, so you just look for the messages.  The simple way to
> see what you're looking for is to open a console, "tail /var/log/syslog -f"
> (or wherever the syslog might be on your system), and close the lid.  When
> you open it again you'll see two standard ACPI event messages.  acpid
> _can't_ tell you what events exist, because they tend to have machine
> dependent names (they're all specified in the DSDT).
> >
> > I been working on this for about 3 days straight.  making small steps, but
> im
> > not there yet...
> 
> Hey, if you get there, let me know :-)  I tried the 2.5 kernels in an
> attempt to get closer but it never really helped.  I think it really
> requires fixing the DSDT beyond what I'm capable of.
> 
> derek

hmm, well then maybe the fixed dsdt did contribute.  I can send it to
you.



-- 
Thank you,


CL Gilbert
"Then said I, Wisdom [is] better than strength: nevertheless the poor
man's wisdom [is] despised, and his words are not heard." Ecclesiastes
9:16

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD  19AE 55B2 4CD7 80D2 0A2D
GNU Privacy Guard http://www.gnupg.org (Encryption and Digital
Signatures)

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

iD8DBQA/bgecVbJM14DSCi0RAvijAKD/Fz2NQT/h8bHHc7nPj0D5empymACeIJO0
CZD8zR6H8oBLD+CkoXTJeKo=
=HDfl
-----END PGP SIGNATURE-----