LinuxQuestions.org - ACPI on Dell 8600

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - ACPI on Dell 8600 (https://www.linuxquestions.org/questions/slackware-14/acpi-on-dell-8600-a-291685/)

ACPI on Dell 8600

How can I get ACPI working on my dell 8600? I'm using Slackware 10.1 and kernel 2.6.10. All the ACPI stuff is compiled as modules in the kernel.

What do I do now? I really want it to go into standby when I close the laptop screen.

(It is my understanding that ACPI must be compiled in the kernel and cannot be loaded as a module, as the previous APM could.)
If you are not compiling your own kernel then choose the bareacpi kernel

you can find it on disk 1 in <cdrom>/kernels/bareacpi.i/

copy the contents to /boot and setup your bootloader appropriately.

If after booting your new kernel the ACPI does not work (mostly old laptops/BIOS ... like mine) you can pass the kernel parameter "acpi=force" at boot. You can do this manually or configure your bootloader to do it.

The bareacpi.i kernel is only 2.4. I upgraded to 2.6.

So if I compile all the ACPI stuff into the kernel, instead of having them as modules, it will just work? I don't have to do anything else?

Ok. I recompiled the kernel. Now when I start kde it has the little battery icon in the taskbar so it is working.

But if I go into KDE Control Center > Power Control > Laptop Battery and Enable Stanbdy in the ACPI Config tab and then right click on the battery icon in the taskbar and select standby, the screen will just go black for like a second before coming back. What;s wrong?

I'm in the same boat. Anybody know what's wrong?

I can't get power button & lid close working on a Dell 5150. Now I'm googling for patched DSDT, but until now I didn't find anything.

Nobody knows? That makes me sad...

Quote:

Originally posted by Pig Monkey
Nobody knows? That makes me sad...

Me too. :(

I remember seeing this post last week when it first got created, and I have the same laptop, thought it'd help me get ACPI figured out. :o

I could never get ACPI working on my 4100. Hell, I couldn't even get the battery monitor to display. So I've used APM forever. Keep this thread in mind if anyone ever figures it out.

Hi,
I dunno if this will work for you, but I have recently found a solution for my laptop. After a couple of weeks of struggling with getting acpi to work on my IBM thinkpad R40, finally found this:
acpitool
Tried the slack package, but that didn't work, so I just compiled from source, rewrote the relevant event file in /etc/acpi/events to run acpitool -s (to suspend) when I close the lid or hit a special fn key combo (requires extra kernel support - so probably won't work on a Dell) and voila, it works!

for example I have a file called /etc/acpi/events/lid.conf that looks like so:

Code:

event=button/lid.*

action=/usr/local/bin/acpitool -s

to find out what acpi calls events look at /var/log/acipd

In case I screw things up there is another file called /etc/acpi/events/powerbutton.conf that enables me to shutdown gracefully with the powerbutton

Code:

event=button/power.*

action=/sbin/shutdown -h now

Hope that helps,
-geomatt

Running acpitool -s makes the following message flash, and then it returns to the command prompt:

Code:

Stopping tasks:

NVRM: ACPI: device not initialized!

Could not suspend device 0000:01:00.0: error -1

ACPI: PCI interrupt 0000:02:01.1[A] -> GSA 11 (level, low) -> IRQ 11

Restarting tasks... done

lspci returns this:

Code:

00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)

00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)

00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 01)

00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 01)

00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 01)

00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 01)

00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 81)

00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 01)

00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 01)

00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio Controller (rev 01)

00:1f.6 Modem: Intel Corp. 82801DB (ICH4) AC'97 Modem Controller (rev 01)

01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0324 (rev a1)

02:00.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)

02:01.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus Controller (rev 02)

02:01.1 FireWire (IEEE 1394): Texas Instruments PCI4510 IEEE-1394 Controller

02:03.0 Network controller: Intel Corp.: Unknown device 4220 (rev 05)

i have a dell 4150, and when i was compiling a custom 2.6.10 kernel a few weeks ago i noticed a kernel config option called suspend, which was listed as experimental. therefore i chose not to include it. is it possible that you need that option compiled into the kernel in order to make suspend work?

Pig Monkey,
What does it say in /var/log/acpid?

mcd,
That's suspend to disk or software suspend: s 4 (acpitool -S) as opposed to suspend to RAM: s 3 (acpitool -s). It's only the suspend to disk (that writes an image to the swap partition) that is experimental. Without it you should still be able to suspend to RAM.

-geomatt

I'm not sure what I did, but after lots of tinkering any many reboots, ACPI appears to be halfway working. Now, when I do acpitool -s, it appears to suspend correctly: the screen goes black, the power LED fades in and out. The trouble is, it won't come back. If I hit the power button, it sounds like it's powering up, the power LED becomes constant, and the screen lightens a bit, but nothing else happens. I have to hold down the power button to shutdown.

/var/log/acpid is long, so I uploaded it:
http://pig-monkey.com/nix/acpid

OK. Looks like you have one script that is being invoked by acpi called /etc/acpi/acpi_handler.sh. The way the system works is that when an event happens an action is triggered.
In your case the event is this:

Code:

event "button/lid LID 00000080 00000002"

which is this passed to the script in the /etc/acpi directory. So the thing to do would be to mess around with that script or just tweak the rules in /etc/acpi to do what you want without it. I think the acpi_handler.sh script is just a default that doesn't do much. My rules don't invoke that, they are much simpler and just call acpitool directly.

Code:

event=button/lid.*

action=/usr/local/bin/acpitool -s

the "button/lid.*" is just short for the full event name.

Oh, and for acpitool -s to work properly I think you need two of the same events to happen sucessively. So close the lid and reopen it, or once you set up a rule that calls it, press the little lid closing button once, wait and then press it again. The power button is a different event.

Cheers,
geomatt