Bug 464284 - default xorg.conf causes wrong pixel clock range to be detected
Summary: default xorg.conf causes wrong pixel clock range to be detected
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-27 06:27 UTC by Matt Hirsch
Modified: 2009-07-14 16:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 16:49:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The default xorg.conf installed by the Fedora 9 installer (590 bytes, text/plain)
2008-09-27 06:27 UTC, Matt Hirsch
no flags Details
The Xorg log file when the xorg.conf file is present (29.73 KB, text/plain)
2008-09-27 06:28 UTC, Matt Hirsch
no flags Details
The Xorg log file when the xorg.conf file is not present (34.52 KB, text/plain)
2008-09-27 06:29 UTC, Matt Hirsch
no flags Details

Description Matt Hirsch 2008-09-27 06:27:22 UTC
Created attachment 317850 [details]
The default xorg.conf installed by the Fedora 9 installer

Description of problem:

The wrong pixel clock is detected for an onboard intel 82810E graphics card when the default xorg.conf is used. When the default xorg.conf file (attached) is used by the X server, the maximum pixel clock is set to 136MHz:

(II) intel(0): Clock range:   9.50 to 136.00 MHz

When the xorg.conf file is removed, the correct pixel clock is set.

(II) intel(0): Clock range:   9.50 to 163.00 MHz

Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-2.3.2-2.fc9.i386

How reproducible:
always


Steps to Reproduce:
1. Install Fedora 9 on system with intel 82810E graphics card
2. Start X server
  
Actual results:

the maximum pixel clock is detected as 136 MHz, preventing 1920x1080 resolution on my monitor:

(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.6 kHz)
...
(II) intel(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan)

(It's requesting a pixel clock of 138.5 MHz)

Expected results:

the maximum pixel clock should be detected as 163 MHz (as happens when xorg.conf is removed), allowing the above auto-detected modeline to be used.

Additional info:

#lcpci | grep VGA
00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133 (CGC) Chipset Graphics Controller (rev 03)

The display is a Samsung HDTV.

There is a second bug here as well: when the wrong pixel clock is detected (136MHz), the driver reduces the display to a resolution that is not supported by the display:

(WW) intel(0): Shrinking virtual size estimate from 1920x1080 to 1400x1050
(--) intel(0): Virtual size is 1400x1050 (pitch 1408)

Notice that 1400x1050 is not in the list of DDC detected resolutions - the driver should pick the next smallest supported resolution.

(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.6 kHz)
(II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 491 520 -hsync -vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0   78.80  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(II) intel(0): Modeline "1600x1200"x60.0  160.96  1600 1704 1880 2160  1200 1201 1204 1242 -hsync +vsync (74.5 kHz)
(II) intel(0): Modeline "1280x1024"x60.0  108.88  1280 1360 1496 1712  1024 1025 1028 1060 -hsync +vsync (63.6 kHz)
(II) intel(0): Modeline "1024x768"x60.0   64.11  1024 1080 1184 1344  768 769 772 795 -hsync +vsync (47.7 kHz)

Comment 1 Matt Hirsch 2008-09-27 06:28:37 UTC
Created attachment 317851 [details]
The Xorg log file when the xorg.conf file is present

Comment 2 Matt Hirsch 2008-09-27 06:29:28 UTC
Created attachment 317852 [details]
The Xorg log file when the xorg.conf file is not present

Comment 3 Adam Jackson 2008-09-30 15:14:22 UTC
This is because the default color depth is normally 24cpp, but i810 is crippled and really only works well at 16bpp.  However I didn't think the default config file wrote out a DefaultDepth line anymore.  Hmm.

Comment 4 Bug Zapper 2009-06-10 02:49:31 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-07-14 16:49:40 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.