Bug 725725 - Grafical Installation fails when updating depending kernel modules, no grafical boot possible, no kdm and kde autostart and no login possible
Summary: Grafical Installation fails when updating depending kernel modules, no grafic...
Status: RESOLVED FIXED
: 725727 (view as bug list)
Alias: None
Product: openSUSE 12.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 1
Hardware: i586 SUSE Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords: German, Public_Beta
Depends on:
Blocks:
 
Reported: 2011-10-21 10:21 UTC by Daniel Barthel
Modified: 2011-10-27 11:05 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: No
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Barthel 2011-10-21 10:21:01 UTC 
The Grafical Installation fails when updating depending kernel modules (after calling fonts) and i get a black screen, telling me there is no device or folder for the named kernel. Practing a manuall restart after this brings the grub, which  dont allow to switch keybord or langange style. The Grafical Boot fails with black-screen (with cursor). Thex-server and the kdm dont start automaticly. Text-based boot and manuall boot brings bootsplash and the login-screen (even automaticly login selected in setup) and even if password for user and for root is correct, i cant login, neither grafical-based or text-based.
Comment 1 Bryan Webb 2011-10-21 20:31:55 UTC 
I believe I had this same problem (on 12.1 Beta 1 Build0315).

I was installing under (the latest) Oracle VirtualBox Version 4.1.4 on a Windows 7 laptop.

This failure occurred twice.  In my cases, the screen did not go black, instead my system showed a messed up window looking like incorrect raster scan settings.

I wasn't sure if it was failing during the
    Updating kernel module dependencies...
which may have occurred very quickly, or the following
    Copying X Window System configuration into system...
step, so I tried an experiment.  On the virtual box, I tried another installation from scratch.  When it got to the
    Initializing fonts...
step, I told VirtualBox to slow down the single allocated CPU to only 8% of its rated speed.  BUT, this time there was no failure, and I was able to complete the installation.

In my case, I always set to Run Level 3.  After logging in as root, then I startx.
After my X windows/KDE stuff, I exit my session.  Upon return to the text screen, I find that it is a messed up screen -- the video mode settings are screwed up, in the same way the installation looked screwed up.

So, I would say this same failure occurs under Windows7/VirtualBox on my hardware, but maybe this gives someone a clue.
Comment 2 Bryan Webb 2011-10-21 22:22:30 UTC 
My problem (having screen problem while installing on VirtualBox) appears to be fixed on RC1 (repeated twice).  I note that Daniel wrote a similar bug against RC1, so maybe the problem isn't completely fixed.
Comment 3 Stephan Kulow 2011-10-24 09:14:41 UTC 
I miss some log files
Comment 4 Stephan Kulow 2011-10-24 09:15:12 UTC 
*** Bug 725727 has been marked as a duplicate of this bug. ***
Comment 5 Daniel Barthel 2011-10-24 10:19:06 UTC 
can find any log files. sorry.
Comment 6 Daniel Barthel 2011-10-24 10:27:41 UTC 
maybe u can assist me some, and let me knew how and where i could get some usefull logs
Comment 7 Andreas Jaeger 2011-10-27 11:05:10 UTC 
This was fixed for RC1.