Handssolow
June 5th, 2008, 10:57 PM
What's been happening to acpi handling with recent kernels? Here on 5th February 2008 my Gutsy kernel upgrade from 2.6.22-14.47 to 2.6.22-14.51 left my 32 bit system unbootable, landing me with the ever popular Busybox and intramfs lines. To get it to boot I had to select an earlier kernel in menu.lst for several weeks whilst I awaited for HHeron to come along and hopefully cure this problem.
When HHeron did arrive the new kernel wasn't any better, my 32 bit OS didn't boot. However, I read on the Forum about there being an issue with acpi handling and by adding pci=noacpi I could boot. This has also been a required extra with every subsequent kernel update. Whilst I may have solved my boot problem, now I have to manually turn off the power switch at shutdown.
In contrast to my 32 bit Hardy Heron, my 64 bit on a Sata works faultlessly without any additional pci=noacpi to my kernel line. Initially I reported this a Launchpad bug #224268 assuming that this was likely to be a hardware problem but considering that 64 bit works, there must be another explanation.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/224268
Looking in the Forum, laptops seem to be mostly affected by these acpi related issues. Frequently I see solutions being offered to members who after an upgrade aren't able to boot but need to disable acpi in one way or another. Ive seen no explanation why previous kernels worked but not the more recent ones.
What happened to acpi handling from kernel 2.6.22-14.51 onwards?
When HHeron did arrive the new kernel wasn't any better, my 32 bit OS didn't boot. However, I read on the Forum about there being an issue with acpi handling and by adding pci=noacpi I could boot. This has also been a required extra with every subsequent kernel update. Whilst I may have solved my boot problem, now I have to manually turn off the power switch at shutdown.
In contrast to my 32 bit Hardy Heron, my 64 bit on a Sata works faultlessly without any additional pci=noacpi to my kernel line. Initially I reported this a Launchpad bug #224268 assuming that this was likely to be a hardware problem but considering that 64 bit works, there must be another explanation.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/224268
Looking in the Forum, laptops seem to be mostly affected by these acpi related issues. Frequently I see solutions being offered to members who after an upgrade aren't able to boot but need to disable acpi in one way or another. Ive seen no explanation why previous kernels worked but not the more recent ones.
What happened to acpi handling from kernel 2.6.22-14.51 onwards?