| Summary: | Intel driver 2.0 only does not detect 1680x1050 | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Brice Goglin <brice.goglin> | ||||||||||||||||
| Component: | Driver/intel | Assignee: | Hong Liu <hong.liu> | ||||||||||||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||
| Severity: | normal | ||||||||||||||||||
| Priority: | high | CC: | hong.liu, jbarnes, jcnengel, keithp, me | ||||||||||||||||
| Version: | 7.2 (2007.02) | ||||||||||||||||||
| Hardware: | Other | ||||||||||||||||||
| OS: | All | ||||||||||||||||||
| URL: | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420840 | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||||
| Bug Depends on: | |||||||||||||||||||
| Bug Blocks: | 13027 | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Brice Goglin
2007-04-27 15:44:48 UTC
Created attachment 9758 [details]
xorg.conf with DDC disabled
Created attachment 9759 [details]
Xorg.0.log with DDC disabled
Created attachment 9760 [details]
Xorg.0.log with DDC
Created attachment 9761 [details]
xrandr --verbose output
*** Bug 10844 has been marked as a duplicate of this bug. *** Hi, this bug is still present in version 2.1.0 of the Intel driver. Do you need further information to fix it? Hi, maybe I should mention that this computer is a Mac mini, not a laptop. So the DVI-out is the only video out available, and doesn't work for me as of 2.0.0. My concern is that the old driver that I have to use won't work anymore with upcoming versions of the Xorg server. I also reported this bug to the debian BTS. After upgrading to the 2.1 intel driver, 1366x768 stopped working (used to use i810 and 915resolution). xrandr reports 1024x768 as the max resolution. Log file and xconfig are at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435621. Has there been any progress on this? My wife is getting tired of using her laptop at 1024x768. ;-) Created attachment 11445 [details]
log with Option "DDC" "off"
This log was created with Option "DDC" "off". I got only 1280x768, not 1680x1050, despite the ModeLine for 1680x1050 that was in the config file.
Created attachment 11446 [details]
log with Option "DDC" "on"
This log was created with Option "DDC" "on". I got a black screen and my TFT says "57 Hz". Obviously, Xorg calculates wrong timings.
Hi, the above logfiles are created with a GIT version from 2007-09-05. I'd be glad if someone can give me a hint what else I could try to get a useable configuration with the Intel driver, or at least what further information is needed. Currently, I can't get a usable screen at the native TFT resolution (1680x1050) at all. Note that this is not a laptop, but a desktop computer, so the TFT is the only way to get video output to work with. Forgot to mention: The logfiles are now created with ModeDebug set to "yes". This looks like the sync polarities are backwards; we had a bug in the X server (not the driver) that would flip the polarities. You should try a custom mode line using +hsync -vsync as cvt -r 1680 1050 shows. Many LCD monitors get very confused when you use the wrong polarity... I tried with this modeline with and without DDC enabled. The result is the same. Actually, I didn't even see the supplied modeline mentioned in the log files. Could it be that the intel driver completely ignores modelines supplied by the user? Created attachment 11527 [details]
working config with a proper modeline
The attached config works gives me a working 1680x1050 mode.
However, when I tried quake3, it switched to a lower resolution, that also used non working parameters. I'll try again with more strict values for HorizSync when I have some spare time.
What is your monitor's model name? A quirk may be needed for this monitor... see bug# 12439. this seems to be the same problem with bug 12262. From the log: (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 -hsync +vsync (64.7 kHz) chosen: dotclock 115200 vco 2304000 ((m 120, m1 20, m2 8), n 3, (p 20, p1 2, p2 10)) the mode probled requires 119MHz dotclock while our driver can only find 115.2MHz which leads to the incorrect display you experienced. Change to use the configured mode you specified exceeds the capability of your monitor (not sure whether it will damage your monitor). (II) intel(0): Ranges: V min: 59 V max: 61 Hz, H min: 31 H max: 65 kHz, PixClock max 120 MHz We are working on fixing the dotclock programming issue now, hoping all the mode display issue will be fixed then :) *** This bug has been marked as a duplicate of bug 12262 *** |
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.