Comment 1 for bug 83111

Revision history for this message
Ronald Teune (zeekoe) wrote :

Today I accidentally booted 2.6.15-25, since it was still my default. It hung somewhere after the fsck (can't see where exactly, since on-screen logging verbosity has decreased a lot). Booting into 2.6.17 did also show the fsck screen for a short time, then going to X. So: acpi=force makes 2.6.15-25 fail to boot...

This makes it somewhat more complicated:
2.6.17 -> crash
2.6.15 -> boot (without acpi features)
2.6.17 acpi=force -> boot
2.6.15 acpi=force -> hang

2.6.x-pre-15 -> boot, with acpi features, without the need for acpi=force.