Bug 22916

Summary: [855GM UMS] Output LVDS enabled but has no modes
Product: xorg Reporter: Frederic Peters <fpeters>
Component: Driver/intelAssignee: ykzhao <yakui.zhao>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: michael.fu
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
2.8.0, without any xorg.conf none

Description Frederic Peters 2009-07-23 11:28:58 UTC 
Created attachment 27957 [details]
2.8.0, without any xorg.conf

After an upgrade from 2.3.2 to 2.8.0 X stopped working for me, it displays this error:

  FATAL: Module i915 not found.
  (EE) intel(0): Output LVDS enabled but has no modes
  (EE) intel(0): No valid modes.
  (EE) Screen(s) found, but none have a usable configuration.

  Fatal server error: no screens found

Debugging further, which binary packages, I found it worked with 2.7.99.901, but failed with 2.7.99.902; then I went out with git and found master to also have the problem.

I tested earlier versions and found 2ebc7d32 to have the problem as well, but couldn't got further as f6f79eb62 and earlier didn't build for me.

>   CC    i830_dri.o
> i830_dri.c: In function ‘I830DRI2CreateBuffer’:
> i830_dri.c:224: error: ‘struct <anonymous>’ has no member named ‘format’
> i830_dri.c: In function ‘I830DRI2ScreenInit’:
> i830_dri.c:422: warning: assignment from incompatible pointer type
> i830_dri.c:423: warning: assignment from incompatible pointer type
Comment 1 Gordon Jin 2009-07-23 18:24:57 UTC 
Can you bisect between .901 and .902 to find which commit breaks your machine?
Comment 2 ykzhao 2009-07-23 20:12:17 UTC 
Will you please try the patch in https://bugs.freedesktop.org/show_bug.cgi?id=22787#C14 and see whether the issue still exists?

It seems that this is a duplicate bug of 22787.
So this bug will be marked as the duplicated bug of 22787.
Thanks.

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

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.