Bug 114676 - yast2 - graphical interface could not be started after first reboot
Summary: yast2 - graphical interface could not be started after first reboot
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-09-01 11:15 UTC by Martin Mrazik
Modified: 2005-09-09 09:33 UTC (History)
0 users

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

Attachments
y2logs (168.66 KB, application/x-tgz)
2005-09-01 11:17 UTC, Martin Mrazik 		Details
hwinfo (131.25 KB, text/plain)
2005-09-01 11:19 UTC, Martin Mrazik 		Details
Xorg.0.log (13.83 KB, text/plain)
2005-09-01 12:43 UTC, Martin Mrazik 		Details
View All 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 Martin Mrazik 2005-09-01 11:15:44 UTC 
While installing beta4, after the first reboot (before I'm able to set root  
password for example) yast complains about the GUI:   
"Graphicaal interface could not be started".   
  
Yast thinks that my graphic card is not properly supported. But prior the  
reboot my installation started in graphical mode and everything went fine.  
Thus it seems weird to me why the GUI could not be started now. 
 
y2logs & hwinfo following. If you need any other logs/configs please let me 
know.
Comment 1 Martin Mrazik 2005-09-01 11:17:57 UTC 
Created attachment 48433 [details]
y2logs
Comment 2 Martin Mrazik 2005-09-01 11:19:07 UTC 
Created attachment 48436 [details]
hwinfo
Comment 3 Martin Mrazik 2005-09-01 12:43:07 UTC 
Created attachment 48452 [details]
Xorg.0.log
Comment 4 Jiri Srain 2005-09-09 09:33:32 UTC 
The loader type was set to "none" - basically, do not install any bootloader. 
 
The result is that the system booted just by accident - there was correct data 
at correct sectors of the disk. 
 
Unfortunatelly, the data wasn't good enough to start framebuffer. 
 
You must set to install a bootloader or boot the system WITH framebuffer 
manually, otherwise X cannot start during installation.