Bug 17038 - Intel-Mobile 965 GM and LCD: black screen
Summary: Intel-Mobile 965 GM and LCD: black screen
Status: RESOLVED DUPLICATE of bug 11368
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2008-08-08 06:29 UTC by thunderfox
Modified: 2008-08-13 01:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (5.17 KB, text/plain)
2008-08-09 07:42 UTC, thunderfox
no flags Details
Xorg.0.log (36.95 KB, text/x-log)
2008-08-09 07:43 UTC, thunderfox
no flags Details
Xorg.0.log.first (24.06 KB, text/plain)
2008-08-11 23:50 UTC, thunderfox
no flags Details
Xorg.0.log.second (24.01 KB, text/plain)
2008-08-11 23:51 UTC, thunderfox
no flags Details

Description thunderfox 2008-08-08 06:29:51 UTC
I installed openSUSE 11.0 on a barebone with Intel-Mobile Chipset 965 GM. My LCD is connected via DVI-Port, but it is possible to connect a monitor with a VGA-cable to the barebone DVI-Port using adapter DVI->VGA (DVI-I Port)

The configuration with Sax is possible, Sax says during test 1280x1024@60 but the test-card has only 1024x768@80 (monitor information). When starting the x-server after finishing sax the monitor says "out of range: vsync at 170 hz" and I got a black screen.

While Sax uses the "intel"-driver, I installed with sax2 -m 0=vesa the "vesa"-driver: everything worked fine, I got 1280x1024@60 but no 3D. Installing the old "i810"-driver did not work.

Later I installed (K)Ubuntu 8.4.1 with the same result (LCD with vsync 170) and I started Knoppix 5.3.1 from DVD also with the same result. A friend of mine own the same barebone but from last year with the 945 GM chipset. He uses openSUSE 10.2 with the "i810"-driver and it works out of the box. With openSUSE 10.3 and 11.0 using the "intel"-driver, he reports the same problems (LCD with vsync 170 hz).

I discussed my problem at the "xorg@lists.freedesktop.org" mailing list and I was told, that the problem might be the DVI-I port.

"if you truly have a DVI-I (carrying analog signal as well as digital),
then the intel driver might not expect that. From what i've heard in
the past DVI-I is rare for intel hw. Someone from intel might be able
to give his/her final word on the matter."

I was told to send a bug-report.

The original manufactor of my barebone called Mini EPC is FIC, more informations could be found here: http://www.fic.com.tw/product/ge2.aspx
Here in germany I bought it via Lynx-PC: http://www.lynx-pc.de/pcs/lypc_silent_mpi.php

Please feel free to contact me via e-mail: thunderfox@gmx.net
Comment 1 Gordon Jin 2008-08-08 23:19:26 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.
Comment 2 thunderfox 2008-08-09 07:42:27 UTC
Created attachment 18189 [details]
xorg.conf
Comment 3 thunderfox 2008-08-09 07:43:13 UTC
Created attachment 18190 [details]
Xorg.0.log
Comment 4 thunderfox 2008-08-09 07:54:38 UTC
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.
Comment 5 Gordon Jin 2008-08-09 19:01:40 UTC
(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


Comment 6 thunderfox 2008-08-11 23:50:58 UTC
Created attachment 18230 [details]
Xorg.0.log.first
Comment 7 thunderfox 2008-08-11 23:51:27 UTC
Created attachment 18231 [details]
Xorg.0.log.second
Comment 8 thunderfox 2008-08-11 23:53:11 UTC
(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.
Comment 9 Gordon Jin 2008-08-12 02:32:17 UTC
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
Comment 10 thunderfox 2008-08-13 01:05:48 UTC
(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 ***
Comment 11 Gordon Jin 2008-08-13 01:43:30 UTC
(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.