Bugzilla – Bug 587514
Problem initializing graphics during installation right after first reboot
Last modified: 2010-04-15 01:13:37 UTC
Created attachment 347955 [details] X log User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 The installation process fails to initialize the display during installation, after reboot, before autoconfiguration. The user sees a black screen. Workaround: - go to vt02 with [Ctrl+Alt+F2] - kill the Xorg process - installation contiues in text mode Surprisingly, after the installation is finished, the graphics works as if nothing was wrong. Reproducible: Always Steps to Reproduce: 1. install 11.3M3 with KDE Live-CD 2. after reboot, when the graphics is supposed to appear, there's only a black screen Actual Results: Installation stuck in a black screen Expected Results: Normal installation
A piece of information that is worth mentioning: this happens starting with M2. M1 didn't have this problem.
Meanwhile we've updated the radeon driver from 6.12.4 to 6.12.191 (6.13.0rc2). Let's assume the issue has been fixed. Otherwise please reopen. BTW, we no longer run sax2 for X.Org configuration during installation right before autoconfiguration since openSUSE 11.2. Thus the described behaviour sounds weird to me.
Bug still there in M4. And it's not related to the video card because I have replaced the ATI card with a Nvidia one. However, the bug is the same, black screen before autoconfiguration. The monitor is not out-of-range (power led would be amber), it just displays black (power led is green as in normal operation). This time, after pressing [Ctrl+Alt+F1] the installer sensed that it could not start the graphics and offered to continue installation in text mode. I still had to kill that process, because it was not allowing normal graphics to start.
Created attachment 351602 [details] Xorg process that displays black screen
Created attachment 351603 [details] That process hogs the tty7
This sounds like fbdev driver is no longer working after the kernel has been rebooted with KMS modules (radeon/nouveau depending on graphics hardware) is active. This would be bad. Could you verify that radeon/nouveau module is loaded with lsmod? Is KMS active? Check with 'cat /sys/module/radeon/parameters/modeset' resp. 'cat /sys/module/nouveau/parameters/modeset'.
The nouveau driver is not used because of something that looks like another bug: II) LoadModule: "nouveau" (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" compiled for 1.7.99.902, module version = 0.0.15 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 7.0 (EE) module ABI major version (7) doesn't match the server's version (6) (II) UnloadModule: "nouveau" (II) Unloading /usr/lib64/xorg/modules/drivers/nouveau_drv.so (EE) Failed to load module "nouveau" (module requirement mismatch, 0) The nv driver is used. II) Module vesa: vendor="X.Org Foundation" compiled for 1.7.6, module version = 2.2.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0
(In reply to comment #6) > This sounds like fbdev driver is no longer working after the kernel has been > rebooted with KMS modules (radeon/nouveau depending on graphics hardware) is > active. This would be bad. Could you verify that radeon/nouveau module is > loaded > with lsmod? Is KMS active? Check with 'cat > /sys/module/radeon/parameters/modeset' > resp. 'cat /sys/module/nouveau/parameters/modeset'. This can't be the reason on NVIDIA since we do not add nouveau kernel module to initrd at the moment - due to a seperate bug (already tracked). (In reply to comment #7) > The nouveau driver is not used because of something that looks like another > bug: That's a seperate issue, which should be fixed with M5. Here I'm talking about the nouveau kernel module. But as stated above that can't be the reason.
(In reply to comment #8) > (In reply to comment #6) > > This sounds like fbdev driver is no longer working after the kernel has been > > rebooted with KMS modules (radeon/nouveau depending on graphics hardware) is > > active. This would be bad. Could you verify that radeon/nouveau module is > > loaded > > with lsmod? Is KMS active? Check with 'cat > > /sys/module/radeon/parameters/modeset' > > resp. 'cat /sys/module/nouveau/parameters/modeset'. > > This can't be the reason on NVIDIA since we do not add nouveau kernel module > to initrd at the moment - due to a seperate bug (already tracked). Similar for ATI. aliases are missing in radeon module on kernel 2.6.33. So radeon module is not added to initrd with ATI graphics either.
Hmm. I cannot reproduce that issue with a Factory installation (something between M4 and M5) with ATI graphics. Thus closing as FIXED. Please do not reopen this one until you can reproduce the issue with M5. We updated radically X.Org and kernel between M4 and M5, which is likely the reason why it works now.
Bug is still there in M5. And it's not related to ATI, because I have an nVidia card in the computer right now. I have made a video recording of the bug. The file is 88 MB. Do you want me to upload it to bugzilla as a Big File?
It's not possible to attach such a big file to Bugzilla. Instead please reboot with kernel boot option 'nomodeset' to disable KMS. Then nv driver instead of nouveau should be loaded. In any case please attach /var/log/Xorg.0.log, e.g. by booting into runlevel 3.
That's a dup. testX (YaST has been waiting in an endless loop for its appearance) was simply missing due to sax2 packages having been removed from LiveCD. This has been fixed *after* M5. Only LiveCD is affected AFAIK. *** This bug has been marked as a duplicate of bug 585432 ***