ACPI Poweroff not working in Slackware12.2 - other threads, unresolved? Fedora does

Hello,
My machine will not auto poweroff in Slackware 12.2.
It will poweroff in Fedora(5,10).

I am dual booting. Fedora is chainloaded with its own Grub. Slackware is booted with lilo from first boot partition (problem existed even prior to dual boot scenario).

I was surprised to find that Fedora10 can still turn the machine off even when chainloaded.
However, Slackware does not turn it off.

I tried adding acpi=force to lilo.conf and it did not change status.
I might be doing it incorrectly or in the wrong place or with incorrect syntax.

I change user to root and give shutdown -hP now. The system halts but does not turn the machine off.

In bios, I have two options for ACPI, S1(pos) and S3(str).
There is also an APM option, yes/no. If yes, I can not manually turn the machine off with the power button, if no, I can power down manually.

Again, Fedora(5,10) succeeds in power down.
Thanks.
M

Technically 'acpi=force' is the proposed solution, are you sure that you ran '/sbin/lilo' after you edited lilo.conf to update the config ?

Also, make sure '/etc/rc.d/rc.acpid' is executable.

If not, then you could try using APM instead, by passing 'acpi=off', as long as APM is supported by the kernel.

Thank you H_TeXMeX_H.

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/hde
acpi=force

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/root
label = Linux
read-only
other = /dev/hde5
label = Fedora

# Linux bootable partition config ends

When I add the 'acpi=force' line,
'/sbin/lilo' returns

Unrecognized token "acpi" at or above line 8 in file '/etc/lilo.conf'

I checked and
'/etc/rc.d/rc.acpid' is executable. Do users need permission to execute, because they only have read and root has read & write?
M

Originally Posted by mitchellray append=" vt.default_utf8=0" boot = /dev/hde acpi=force Unrecognized token "acpi" at or above line 8 in file '/etc/lilo.conf'

That's because it's not correct, it should be:

append=" vt.default_utf8=0 acpi=force"
boot = /dev/hde

Thank you H_TeXMeX_H.

Poweroff is now working.
I will start a new thread to inquire as to how to allow users to 'shutdown'.

Mitchellray

I think you may find the answer to that question here:
http://www.linuxquestions.org/questi...=user+shutdown

Thank you again H_TeXMeX_H.
I followed the link and will have to study the thread closely to be certain I understand what I am doing.
I noticed that I do not seem to have a '.bashrc' in my user path.
A further query indicates that I must create the file and that it will somehow be read when needed per call by 'sudoer'.
It is still unclear to me, but I will read the thread again.
M

Alright, good luck.