Bug 34059

Summary: [855GM] modesetting error
Product: xorg Reporter: KJ Loh <kjloh71>
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: blocker    
Priority: medium CC: mengmeng.meng
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
screenshot
none
dmesg for jumbled screen
none
dmesg for good display none

Description KJ Loh 2011-02-08 22:28:25 UTC
Created attachment 43147 [details]
screenshot

I am using acer travelMate 380 laptop, the graphic adapter is intel 82852/82855 GM/GME Graphics Controller. After upgrading to Natty 11.04 kernel 2.6.38.1/2, the login screen cannot display properly. and there is no way to login to the system. pls kindly see the attached screenshot

there is no such problem when I use the kernal 2-6-37-12.

Pls feel free to let me know if there is further information I need to provide assist to get resolve the issue.

I have created an entry in launchpad at ubuntu and there is some log collected using ubuntu-bug when I booted using 2-6-37-12.  I wonder if it is useful.

thank you very much
Comment 1 KJ Loh 2011-02-08 22:30:17 UTC
sorry the URL at the launchpad is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/714634?comments=all
Comment 2 Chris Wilson 2011-02-09 01:22:18 UTC
Add drm.debug=0xe to your grub boot parameters and attach the dmesg.

Does this only happen with X or is the entire boot jumbled?
Comment 3 KJ Loh 2011-02-09 01:29:40 UTC
I shall do as per your instruction when I get to the machine later.




Hope I  understand your question correctly, the splashscreen did come up and it happened when it reached the login part.

by the way, I am not using a xorg.conf now.

thanks.
Comment 4 KJ Loh 2011-02-09 07:48:09 UTC
Created attachment 43164 [details]
dmesg for jumbled screen
Comment 5 KJ Loh 2011-02-09 07:48:58 UTC
Created attachment 43165 [details]
dmesg for good display
Comment 6 KJ Loh 2011-02-11 18:19:06 UTC
Hi Chris, it fixed after I applied the .38.3 this morning.

thanks.
Comment 7 Chris Wilson 2011-02-12 10:24:28 UTC
I'm not sure which actual patch it was that fixed it, so I hope it remains fixed as 2.6.38 comes out...
Comment 8 Chris Wilson 2011-03-04 12:04:11 UTC
*** Bug 34421 has been marked as a duplicate of this bug. ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.