kernel ignores "acpi=force" with quiet option on older BIOS

Bug #186325 reported by Christian González
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-server

I've the above kernel running on a Compaq Deskpro EN Series SFF, with an older BIOS (before 2000). (Dapper,Feisty,Gutsy now.)
until now it wasn't possible to power-off the computer correctly, because the kernel complained that the bios is too old and recommended to switch on the acpi=force option.

I did that - but no change.
The kernel IGNORES the "acpi=force" option.
part of my my grub.conf:

title Ubuntu 7.10, kernel 2.6.22-14-server
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-server root=UUID=XXXXXXX ro acpi=force quiet splash
initrd /boot/initrd.img-2.6.22-14-server

Then I discovered (by accident) that if I cut the "quiet" option, THE ACPI=FORCE WORKS.

That's very strange - maybe it should be that way, but I didn't find anything, so I file that bug here.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Christian,

I've seen other bug reports commenting on similar issues regarding the BIOS being too old: https://bugs.launchpad.net/ubuntu/+bug/126863 . You may want to try the workarounds mentioned there.

Regarding the acpi=force option only working if you remove the 'quiet' option, that does seem like a bug. The Hardy Heron Alpha series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists in the Hardy Alpha release or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!

Changed in linux-source-2.6.22:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.