On 2006.01.28 19:30, Wayne Stallwood wrote:
On Sat, 2006-01-28 at 19:08 +0000, Barry Samuels wrote:
Ah! but it always used to work until I swapped the bits into a new case. Nothing else has changed.
Ooops sorry I read new case but registered new mainboard for some reason.
That is a bit odd, the only thing I can think of is that somehow you have made a slight mistake with the front panel headers and inadvertently shorted a sleep pin or something else that confuses ACPI
I'll check those again when I next dive into the case.
(you can almost hear the straw clutching)
I'd go for noacpi as my first try, just add this to your boot parameters (usually you can interrupt lilo or grub at boot and
add these manually)
If that doesn't work for you then you could try disabling the
apic as well (although it doesn't sound like an apic problem to me. If all else fails try noapic
Could be tricky - this is a dual CPU board. :-))
Erm yes that would be a bit of a problem *grin*
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain