Bug 399638 - 2nd stage installation - X and network not working
Summary: 2nd stage installation - X and network not working
Status: RESOLVED DUPLICATE of bug 339024
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: RC 3
Hardware: x86-64 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Jozef Uhliarik
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-12 12:28 UTC by Christian Hueller
Modified: 2008-09-23 11:08 UTC (History)
2 users (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
hwinfo of affected machine (423.03 KB, application/octet-stream)
2008-06-12 12:33 UTC, Christian Hueller
Details
log files from affected machine (849.41 KB, application/x-compressed-tar)
2008-06-12 12:34 UTC, Christian Hueller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Hueller 2008-06-12 12:28:42 UTC
Description:

I installed OpenSUSE11.0 RC4 and after the first reboot into the second stage install I get an error message about X not being able to start. The installer is therefor in ncurses mode. After some steps also the download of updates failes as the network card is not available.

Howto repeat:

Install 11.0RC4 on my workstation
Comment 1 Christian Hueller 2008-06-12 12:33:22 UTC
Created attachment 221769 [details]
hwinfo of affected machine
Comment 2 Christian Hueller 2008-06-12 12:34:22 UTC
Created attachment 221770 [details]
log files from affected machine
Comment 3 Stephan Kulow 2008-06-12 12:48:54 UTC
perhaps because it boots into XEN kernel?
Comment 4 Christian Hueller 2008-06-12 14:01:37 UTC
I finished the installation and I can't see anymore what it booted into. I had the xen pattern selected and it might have happened. Does not the log files provide this information. However if it by default boots the xen kernel once that pattern gets selected upon 1st stage install I'd also consider it as bug.

And it is indeed a xen kernel, clicking through the logs revealed:

-----------------------------snip----------------------------------
Inspecting /boot/System.map-2.6.25.5-1.1-xen
Loaded 27109 symbols from /boot/System.map-2.6.25.5-1.1-xen.
Symbols match kernel version 2.6.25.
No module symbols loaded - kernel modules not enabled.

klogd 1.4.1, log source = ksyslog started.
<5>Linux version 2.6.25.5-1.1-xen
-----------------------------snip----------------------------------

So bugreport must be renamed to "Selectin Xen pattern upon installation causes second stage install to be text only"

Why the network card was not detected I do not know, after the next boot with starting the xen kernel it got detected and works. If this is also an effect of the xen kernel then I'd leave the bugreport as critical (not blocker due to the new bug handling process).
Comment 5 Christian Hueller 2008-06-12 14:03:28 UTC
Needed info provided (although it was already there ;)
Comment 6 Stephan Kulow 2008-06-12 14:11:18 UTC
in any case, it's very unlikely that this is my bug
Comment 7 Christian Hueller 2008-06-12 15:13:27 UTC
sorry, I thought you were in charge of the release and as this was some possible stopper I assigned it to you, as this is the common practice with possible stopper bugs for business products - we assign them to the release manager so he has a chance to decide quickly. If it is not you who is/was the release manager? 
Comment 8 Stephan Kulow 2008-06-13 09:07:13 UTC
yes, but openSUSE is no business product.
Comment 9 Jason Douglas 2008-06-23 15:00:07 UTC
Every way that I look at this, this is an Installation issue (not a xen issue).  First off, similar bugs have been entered in the past and the proposed fix was to NOT boot into XEN for the second half of the install, hence this would be a bug in the installer.

However, if you really want to boot into XEN and have a graphical display for the second half of the install, then a framebuffer has to be setup for XEN.  This is done by adding vga=mode-0x317, for example, to the hypervisor line.  This again would have to be handled by the installer.

Therefore, I am reassigning this bug to the Installation component.
Comment 10 Jozef Uhliarik 2008-07-11 07:29:18 UTC
Christian, boot sections are created by post-install script of kernel. (via perl-Bootloader) If kernel for XEN is installed after default or pae kernel his boot section is set like the first boot section and default. The vgamode is read from install.inf and the value is 0x13a.

IMO it is correct.
Comment 11 Josef Reidinger 2008-09-23 11:08:20 UTC
this is duplicate of bug. We must find way how to boot between stages to correct system.

*** This bug has been marked as a duplicate of bug 339024 ***