[Bug 331007] New: Unable to make openSuse 10.3 start
https://bugzilla.novell.com/show_bug.cgi?id=331007 Summary: Unable to make openSuse 10.3 start Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lschmitz@pt.lu QAContact: jsrain@novell.com Found By: Customer First part of installation runs without any problems. After reboot, second part of installation only works when booting with XEN-Kernel and in text-only mode. After complete installation, again only XEN-Kernel boots (neither normal nor failsafe works), until the login screen should appear. The screen turns black (slightly flickering) and there is a watch cursor (black and withe, not animated, not the blue animated watch cursor from 10.2). In fact I had the same problems with 10.2, except that the login screen appeared when using XEN-Kernel, so at least I was able to use openSuse 10.2. Thanks for your help -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331007#c1
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=331007#c2
--- Comment #2 from Luc Schmitz
what is the exact problem when booting the default kernel?
When I select the default kernel, the screen simply turns black as soon as I hit Enter and nothing else happens (no disk activity). What I found out is that the system boots normally if I choose "Repair installed system", then "Boot installed system". Could it be that there are special kernel parameters that make the system work in this case ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331007#c3
Christian Boltz
https://bugzilla.novell.com/show_bug.cgi?id=331007#c4
--- Comment #4 from Luc Schmitz
Luc, please always select the "This comment provides the needed information" checkbox when providing information...
Dear Christian, I apologize for my faux-pas, but I don't have the checkbox you mentioned. I found out another thing: I now installed the 32-bit version of 10.3. It went exactly the same way as the 64-bit version of 10.2: The installer starts in graphical mode. I choose my partitions, online sources, .. The only package I add to the default package selection is the XEN virtualization, as it is the only way since 10.2 that I can get the system to boot. Everything works fine until the reboot after installation of the packages. Although 3 options are available (default, XEN and failsafe), the system tries to boot the default kernel which hangs immediately. After resetting the PC, I can choose the XEN kernel which starts the second part of the installation. As soon as Yast starts (in text mode), there is a message informing me that the graphical system cannot be started. So I progress through the second part of the installation in text mode, but without any other problems (root password, system configuration, ...). After finishing the installation, this is what happens when I choose the different options: Default kernel: system hangs immediately (32- and 64-bit version). XEN-kernel: system loads, daemons and services are started, the screen turns black with a black and white watch cursor (32- and 64-bit version). At this point the 64-bit version hangs whereas the 32-bit version changes the cursor into a standard arrow cursor and after 1-2 seconds the login screen appears and I am able to use the 32-bit XEN-kernel version of 10.3. Failsafe mode: the screen shows some information (no error messages) about the file system, the kernel with its parameters and initrd, then it hangs (32- and 64-bit version). Used hardware: XPC Shuttle with Intel Core Duo 6400 2,13 GHz, 1 GB memory, hard disk 320 GB (no other systems installed), nVidia GeForce 7600 (same behaviour with onboard graphics) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331007#c5
Matej Horvath
https://bugzilla.novell.com/show_bug.cgi?id=331007#c6
Luc Schmitz
https://bugzilla.novell.com/show_bug.cgi?id=331007
Matej Horvath
https://bugzilla.novell.com/show_bug.cgi?id=331007#c7
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=331007#c8
Luc Schmitz
Ok, all of the boot messages are from the Xen kernel. That's expected, since if the machine hasn't booted successfully, those files wouldn't be generated.
Can you boot into the Xen system and post the results of "rpm -qa|grep kernel" ? I'd like to verify which kernel you're using.
Can you also try booting your non-Xen image with "acpi=off"?
Here is the output of "rpm -qa | grep kernel": kernel-xen-2.6.22.9-0.4 nfs-kernel-server-1.1.0-8 kernel-default-2.6.22.9-0.4 linux-kernel-headers-2.6.22-19 Using "acpi=off" with the default kernel has no effect (screen turns black, system hangs). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=331007
User roland.kletzing@materna.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=331007#c9
roland kletzing
https://bugzilla.novell.com/show_bug.cgi?id=331007
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=331007#c10
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=331007
User lschmitz@pt.lu added comment
https://bugzilla.novell.com/show_bug.cgi?id=331007#c11
Luc Schmitz
https://bugzilla.novell.com/show_bug.cgi?id=331007
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=331007#c12
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=331007
User lschmitz@pt.lu added comment
https://bugzilla.novell.com/show_bug.cgi?id=331007#c13
Luc Schmitz
participants (1)
-
bugzilla_noreply@novell.com