[Bug 604043] New: Automatic configuration with non-ACPI BIOS causes installation to halt with errors at 1st reboot
http://bugzilla.novell.com/show_bug.cgi?id=604043 http://bugzilla.novell.com/show_bug.cgi?id=604043#c0 Summary: Automatic configuration with non-ACPI BIOS causes installation to halt with errors at 1st reboot Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: terence.silk@tesco.net QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 During clean install from a fully validated DVD (created from a fully validated iso image), if automatic configuration was left selected, then a non-ACPI BIOS was not identified as such and on 1st reboot, the OS/installer reported that it could not find the ACPI information in RAM that it expected to find and the configuration came to a halt. Reproducible: Always Steps to Reproduce: 1.Clean install openSUSE 11.2 x86-64 on any non-ACPI BIOS PC. 2.Do not attempt to facilitate the installation using the acpi=off option or equivalent (please note that this stipulation makes sense when you read the preferred solution to this problem in the Additional Information section). 3.Proceed to the 1st reboot point and observe the error messages which clearly indicate that the installer has failed to the BIOS type properly in automatic configuration mode. Actual Results: On screen error messages about missing ACPI information appeared and the computer froze. Expected Results: The installation should have proceeded to a configuration screen. The problem was solved with all 3 of my non-ACPI BIOS machines by clearing the "use Automatic Configuration" option box on the "Installation Mode" screen during the installation. I did not have to resort to using the acpi-off option which would undesirably disable PowerNow! processor control. After installation by this method completed, the PowerNow! functions were clearly in good health. Whilst I accept that Automatic Configuration is a "nice to have" it is extremely puzzling why the behaviour reported here occurs in an automatic configuration and yet does not occur when automatic is deselected. It must be very off-putting for Linux newcomers. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604043
http://bugzilla.novell.com/show_bug.cgi?id=604043#c1
--- Comment #1 from Terence Silk
http://bugzilla.novell.com/show_bug.cgi?id=604043
http://bugzilla.novell.com/show_bug.cgi?id=604043#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=604043
http://bugzilla.novell.com/show_bug.cgi?id=604043#c
Lukas Ocilka
http://bugzilla.novell.com/show_bug.cgi?id=604043
http://bugzilla.novell.com/show_bug.cgi?id=604043#c2
--- Comment #2 from Terence Silk
http://bugzilla.novell.com/show_bug.cgi?id=604043
http://bugzilla.novell.com/show_bug.cgi?id=604043#c3
Greg Kroah-Hartman
participants (1)
-
bugzilla_noreply@novell.com