My distro is Mandrake 10.1 and my pc case is Aopen H600B, its powersuply is 300W ATX 12V.
When i turn off the linux, it does not turn the computer off, it says just "Power down", i wait for turning it off, but i think, wait for i switch it off from button .
I look System/Configuration/KDE/Power Control, but there is nothing to adjust...
Why linux doesn't turn the computer off...
Thanks for any help...

Does your kernel have support for APM/ACPI?

hi,

the solution to this will depend on whether you're using the 'lilo' or 'grub' bootloader - i'm running mandrake 10.0 and use 'lilo'; i did try 10.1 but i can't remember whether it still used lilo by default.

perhaps you could post back and let us know which one you're using.

(if you're unsure, go to mandrake control center, 'boot', then 'bootloader'... you should see which one is currently in use.)

What is APM and ACPI?

Lilo with graphical menu.
I saw APIC and ACPI, what are these?

hi,

ok so you're using Lilo.

You need to edit the file /etc/lilo.conf (you'll need to do this as the root user)

When you open the file, you should see a number of sections headed 'image=....' For clarity, i'll post part of my lilo.conf file here -

what you need to do is change the acpi entry on the line beginning 'append=' to 'acpi=force' (as above). it probably reads 'acpi=ht' or similar at the moment. then save your changes, and from the command line, as root, run the command 'lilo' (you might need to actually run '/sbin/lilo') to update your lilo configuration.

now when you shut down, the computer should power off...

as for apm / acpi, they're BIOS power management features, which the operating system can access to control various things (such as power off...). unfortunately, certain BIOS versions don't implement things fully, so that's why you need to change your lilo file. i had the same problem, and making the change above resolved matters.

My lilo config file there is no apm???
Do you think i should change it...
I mean should i add apm in?
By the way what is devfs=mount

default="linux"
boot=/dev/sda
map=/boot/map
keytable=/boot/us.klt
prompt
nowarn
timeout=30
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="linux"
root=/dev/sda10
initrd=/boot/initrd.img
append="acpi=ht resume=/dev/sda5 splash=silent"
vga=788
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/sda10
initrd=/boot/initrd.img

No, i don't think so. Just change the 'acpi' bit as suggested and you should be away.

Thanks for your help...

You're welcome..

Oh, you might find that the first time you shutdown the computer after making the change, it might still not power off correctly; but the next time you boot, the system should be correctly set up...

I have a problem about CPU Temperature. After changing lilo.conf kernel gave message that the CPU temperature is above the treshold. And then gave another message that the CPU is working in something... mode. After this situation I reboot the computer and then I opened the System Monitor and saw that CPU usage is above %55 and kernel gives the same messages over and over. After opening the task manager I couldn't saw anything using so much CPU. Do you think that this maybe related to changing the lilo.conf file. And can I find a software that monitors the CPU or all the hardware usage and fan speed also.
Please help... Now I can't courage to boot the sytem.

hi,

this doesn't sound good.. it could be due indeed to changes to lilo.conf, at least as far as the system now reporting low-level stuff like fan speed etc, which would previously perhaps have gone unnoticed?

i'm not qualified to suggest further - you could try changing lilo.conf back again (remember to run 'lilo' afterwards..) and see what happens - and check cpu usage afterwards, too...

i've made the 'acpi=force' change on my machine, with no adverse effects, and this was on the advice of something i read elsewhere (i think it was a red hat forum..)

the only thing i can suggest is go back to what you had before. it's also very highly unlikely indeed that you will have damaged your system - if the processor overheats, the system will shut down to protect itself.

perhaps others might like to comment?

If your BIOS has broken, incomplete, or nonexistant ACPI support that would otherwise be automatically disabled, adding acpi=force could cause the system to report problems it doesn't otherwise see. Generally, this would indicate that the problems probably don't even really exist.

I had a problem similar to this on my Gentoo box not too long ago. It turns out that the fan that came with my CPU (a P4 3Ghz boxed) wasn't spinning fast enough, and the temp was getting up to about 180 F at one time. All I had to do was repalce the fan with a better model and I haven't had any more warnings.