Bug 578512

Summary: xorg fail to start at boot time for the Intel Mobile Intel® GM45 Express Chipset on a lenovo T500 laptop
Product: [openSUSE] openSUSE 11.3 Reporter: gérald Maricau <novell.maricau>
Component: X.OrgAssignee: Forgotten User Wum0mkMcd8 <forgotten_Wum0mkMcd8>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Major    
Priority: P3 - Medium CC: lchiquitto
Version: Factory   
Target Milestone: Factory   
Hardware: x86-64   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: xorg log file

Description gérald Maricau 2010-02-09 21:20:14 UTC
Created attachment 341615 [details]
xorg log file

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6

Xorg fail to start with this error in the log "/var/log/Xorg.0.log": "No kernel modesetting driver detected...Screen(s) found, but none have a usable configuration...Fatal server error: no screens found"

Reproducible: Always

Steps to Reproduce:
1. Default boot or Normal boot in runlevel 5 (with network and Xorg)
Actual Results:  
Xorg is not starting (the same result if i have a /etc/X11/xorg.conf file or does not have the configuration file)

Expected Results:  
Xorg starting

A temporary workaround (with or without an /etc/X11/xorg.conf file) login in and run this command : rmod i915;init 3;sleep 4;init 5;sleep 15;exit
Comment 1 Leonardo Chiquitto 2010-02-10 09:58:11 UTC
You're running 11.3 (Factory) and not 11.2, right?
Comment 2 gérald Maricau 2010-02-10 11:22:28 UTC
Yes, i think so but i'm not sure why i'm having the 11.3 now.
Is this the consequence of entering this command :
zypper dup
zypper dist-upgrade
Comment 3 Leonardo Chiquitto 2010-02-10 11:30:21 UTC
It depends on the repositories you have configured in your machine. You can check this on YaST -> Software Repositories.

Adjusting bug product.
Comment 4 Leonardo Chiquitto 2010-02-10 11:32:00 UTC
Thanks for taking the time to report this problem. There's an ongoing effort to fix it in bug #577000, so I'm marking this one as a duplicate.

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