On Sunday 28 March 2004 07:28 am, Margot wrote:
Tom Brinkman wrote:
On Thursday 25 March 2004 02:03 am, Tony S. Sykes wrote:
http://www.iki.fi/tmb/Cooker/kernel-tmb-2.6.4-1.tmb.3mdk-1-1 m dk.i586.rpm http://www.iki.fi/tmb/Cooker/kernel-tmb-2.6.4-1.tmb.3mdk-1-1 m dk.nosrc.rpm
Well, some success... I managed to download and install the new kernel (without getting cut off this time), and the shutdown now goes past the original hang point, but now it gets to this:
md: md0 switched to read-only mode. Power down.
...but it doesn't actually switch off!
I assume that it is safe to just hit the power switch at this point, but is there some setting I could change so it will switch off automatically?
Margot
No sooner did I post the link to Thomas' kernel, than he released an updated version 2.6.4-1.tmb.4mdk
Well, I've now experimented with several kernels, and the one which works best so far is 2.6.4-1.tmb.3mdk - machine still doesn't actually switch off, but everything else seems pretty stable.
Perhaps now is the time to look at the acpi and apic settings that Tony suggested. I've seen these mentioned in other threads, but mainly relating to laptops. Mine's a desktop machine.
I believe the general trend with 2.4.x kernels would be to disable apic and/or acpi. With 2.6.x and newer hardware, I believe it'll be to make sure they're both enabled. The only exception to that I currently know of is nForce chipset systems which don't handle them properly. You've got a VIA chipset which will.
Are there any standard settings for acpi and apic for different types of machine, or is is just a question of trying various combinations until I find one that works?
Yep, trial'n error
I know that the settings appear in the append line in lilo.conf, but is this where I actually edit them, or is there another file for the settings which transfers the details into lilo.conf?
No, edit lilo.conf, and try not to forget to run 'lilo' to write the changes before you reboot. (we all do sometimes ;)
Margot, the behavior you describe is probly a hardware or bios configuration deficiency. Specially if you close all applications you don't want to start on the next boot, open a term and su to root, and type 'halt'. You might also experiment with 'reboot'. In any event, yes, you're probly OK to use the power switch, particularly if you don't see any file system warnings on the next boot.
On an ATX motherboard, try either "4 sec delay" or "instant off" bios settings to see if one works better than the other.
Is ATX a brand name, or is it some sort of specification? Mine's a Shuttle Spacewalker MV42N - I don't want to start fiddling with bios settings until I have some idea of what I'm doing!
Margot
A specification. Your Shuttle is a micro ATX. ....and the system is up to date enough, that I believe with 2.6.x kernels, you should (even need/want to) enable apic and acpi. You do so by removing any 'noapic', 'nolapic', and 'acpi=off' (or acpi-=ht) from the 2.6.x kernel stanza in your lilo.conf. These features are built into the kernel, no need to explicitly enable them.
After sorting out some other problems, I finally found time to look at this again. I'm now using the tmb.5 kernel, tried all the possible combinations of acpi and apic settings I could think of, and have found that with the option "acpi=on" and no mention of apic or lapic, the computer now switches off automatically, the way I wanted it to.
Thanks for your help. Now I just have to get the sound working... ;-)
Margot
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
