I am running Mandrake 10.0 Discovery on my PC with KDE 3.2 and a 2.6.3-7 kernel. I have an Abit IC7-G motherboard in an Antec 660AMG case.

I have been using Linux for about a month now and have ironed out many of the issues that faced me. However, there is one minor thing that bugs me: when I select 'logout' from the KDE menu and then select 'Turn off computer', it does not power down. It goes through all the shutdown sequence, and kills all the processes and so on, but the machine doesn't actually power off - it just comes to the end of the shutdown sequence and then displays 'Power down' as the last message, at which point I have to manually switch the machine off.

I know this is only a small thing, but I would much prefer it to switch off when it has completed shutting down.

Could anybody please give me some pointers as to what I would have to change to achieve this?

uncomment apm in the /etc/modules.conf file. Or try:
modprobe apm and the do the shutdown sequence to see if it solves your problem.

I can see no apm line in the modules.conf file.

When I type modprobe apm, it says 'FATAL: Module apm not found.'

Having looked at various websites, I thought I had solved it:

There was a line in the lilo.conf file. I deleted the part that said acpi=ht and then ran lilo

This worked - when i shutdown, the system powered off on it's own. I tested it several times and it worked fine. However, without having changed anything, it has now stopped working and I can't even power off now when I push the power button. very odd

That is odd! Did you try running lilo again just to see what happens?

I've tried redoing the whole thing, and it's just plain weird.

Sometimes it switches off ok and other times it hangs with the last command showing as 'acpi_off called' (or something like that).

Nothing changes in the meantime though - I'm just logging on and then logging straight off to test it. I don't understand it.

Yep, I have Exactly the same issue now with Mandrake 10.1 OE. The final line is just power down.
Wonder what it can be..
Anyone having anymore suggestions ?

It should go back to a problem with acpi or apm based on my past experiences. You might try looking for patches to acpi since you don't use apm. It might be a hardware compatibility issue that could be fixed through a patch.

I don't know, I've tried some searches on the web, but can't find anything to help.

The odd thing is that I can't see anything that says acpi is even running, though from my investigations I see that acpi is apparently part of the 2.6.3-7 mandrake kernel. I can see a directory /lib/modules/2.6.3-7mdksmp/kernel/drivers/acpi with a bunch of files in it, so something is there.

Would acpi show up as a service running?

I would build a new kernel like the 2.6.9 and try acpi only. If that does not work rebuild and try apm. Acpi should do it. Don't try 2.6.10 unless you are ready to make changes to udev and other items.

Brian1
" Google the Linux way @ http://www.google.com/linux "

Hmm... I recently upgraded to 10.1 official.. and the I have the same problem..

I have other problems to solve now, but please post here if you get it working