Bug 23161 (rokkos75) - 855GME no LVDS output - Pipe B disabled
Summary: 855GME no LVDS output - Pipe B disabled
Alias: rokkos75
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: ykzhao
QA Contact: Xorg Project Team
Keywords: NEEDINFO
Depends on:
Reported: 2009-08-05 10:21 UTC by john
Modified: 2009-08-24 05:24 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

x server log (62.00 KB, text/plain)
2009-08-05 10:21 UTC, john
no flags Details

Description john 2009-08-05 10:21:32 UTC
Created attachment 28378 [details]
x server log

- chipset : intel 855GME, 32MB shared memory
- server 1.5.2 (latest version shows the same problem)
- driver intel (latest version shows the same problem)
- kernel 2.6.27 (2.6.30 shows the same problem)

I have no LVDS output (if I don't connect a VGA monitor X even refuses to start).
Reading the X log (attached here) it seems that the LVDS interface is activated and attached to pipe B, but pipe B is turned off for some reason. I've tryed with several linux distributions, several xorg configuration (even no configuration at all), and several server and driver versions, but the result is always the same. With the old i810 driver, all was fine, and I had by default both LVDS and VGA. Is this a but, or the driver needs a special setting to have LVDS output?
Thank you very much!

Comment 1 ykzhao 2009-08-05 22:07:41 UTC
Will you please attach the xorg.log when no external vga is connected?
Will you please try the latest intel driver and see whether the issue still exists?
Please also attach the output of vbios.dump.
Comment 2 Michael Fu 2009-08-06 00:43:13 UTC
pls follow http://intellinuxgraphics.org/how_to_report_bug.html. thanks.
Comment 3 Michael Fu 2009-08-14 02:09:56 UTC
Comment 4 Michael Fu 2009-08-24 05:24:37 UTC
assume this has been fixed by yakui's lid detection patch.

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.