Summary: | Intel-Mobile 965 GM and LCD: black screen | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | thunderfox <thunderfox> | ||||||||||
Component: | Driver/intel | Assignee: | Gordon Jin <gordon.jin> | ||||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
Severity: | normal | ||||||||||||
Priority: | medium | Keywords: | NEEDINFO | ||||||||||
Version: | unspecified | ||||||||||||
Hardware: | x86 (IA32) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
thunderfox
2008-08-08 06:29:51 UTC
Please attach xorg.conf and Xorg.0.log according to http://www.intellinuxgraphics.org/how_to_report_bug.html. This problem seems similar to bug#11368. You can try the workaround suggested in comment#38 there. Created attachment 18189 [details]
xorg.conf
Created attachment 18190 [details]
Xorg.0.log
I just attached xorg.conf and Xorg.0.log I tried the workaround described in comment#38 of bug#11368 but I am not sure what to do exactly. Every time when I started X, the X-Server reported an incomplete xorg.conf. Sorry, I am only a Linux beginner, and my English is very poor. (In reply to comment #4) > I tried the workaround described in comment#38 of bug#11368 but I am not sure > what to do exactly. So you are writing "Monitor[0]" instead of "LVDS" as suggested in comment#38. But that doesn't matter. The key point you were missing is that you should put "Ignore" line in the Monitor section, so it should be like: Section "Monitor" Identifier "Monitor[0]" Option "Ignore" "true" EndSection Created attachment 18230 [details]
Xorg.0.log.first
Created attachment 18231 [details]
Xorg.0.log.second
(In reply to comment #5) So I tried two different versions of my xorg.config. In the first version I just inserted the "Option Ignore true" line into the existing Monitor-section: Section "Monitor" DisplaySize 377 301 HorizSync 30-82 Identifier "Monitor[0]" ModelName "VIEWSONIC VP191B" Option "Ignore" "true" Option "PreferredMode" "1280x1024" VendorName "VIEWSONIC" VertRefresh 50-70 UseModes "Modes[0]" EndSection In the second Version the Monitor-section just has two lines: Section "Monitor" Identifier "Monitor[0]" Option "Ignore" "true" EndSection With both versions I got only error messages, no X-server could be started. You find attachments with both xorg.o.log files ending with "first" for my first version und with "second" for my second version. Sorry for having not made it clear. You should keep the external monitor (the original monitor in your xorg.conf), and add LVDS workaround, so it should be like: Section "Monitor" Identifier "Monitor[0]" ModelName "VIEWSONIC VP191B" Option "PreferredMode" "1280x1024" VendorName "VIEWSONIC" VertRefresh 50-70 UseModes "Modes[0]" EndSection Section "Monitor" Identifier "LVDS" Option "Ignore" "true" EndSection Section "Device" BoardName "965 GM" BusID "0:2:0" Driver "intel" Identifier "Device[0]" Option "monitor-VGA" "Monitor[0]" Option "monitor-LVDS" "LVDS" VendorName "Intel" Option "ModeDebug" "TRUE" EndSection (In reply to comment #9) It works!!! I am very happy to report this! Thank you for pointing me to the right direction. I thought that there could be only one Monitor section. So I marked my bug report as a duplicate of bug#11368, i hope this is the correct way. Just one question: is it possible that future versions of the intel-driver will function "out of the box"? My intel-driver which comes with openSUSE has the version-number 2.3.1 Once again, thank you very much!!! *** This bug has been marked as a duplicate of bug 11368 *** (In reply to comment #10) > So I marked my bug report as a duplicate of bug#11368, i hope this is the > correct way. Correct. > Just one question: is it possible that future versions of the intel-driver will > function "out of the box"? My intel-driver which comes with openSUSE has the > version-number 2.3.1 Yes, we want to fix it so it would work out of the box. That's why we keep bug#11368 open. I hope this could be fixed in next (2.5) release. |
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.