Bug 675626

Summary: [Cantiga] Intel DisplayPort probes only 640x480 resolution
Product: [Fedora] Fedora Reporter: Gordon Messmer <gordon.messmer>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: ajax, caz, desmond.armstrong, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: [cat:rendering]
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:01:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Intel video ROM
none
Xorg log
none
dmesg output after DisplayPort monitor connected
none
messages log from boot until after DisplayPort monitor connected
none
output of intel_reg_snapshot before DisplayPort monitor connected
none
output of intel_reg_snapshot after DisplayPort monitor connected
none
output of smoltSendProfile before DisplayPort monitor connected
none
output of smoltSendProfile after DisplayPort monitor connected none

Description Gordon Messmer 2011-02-07 00:16:05 UTC
Description of problem:
Testing was done on Fedora 14, with the addition of the Linux kernel from "development".  The current Fedora 14 kernel merely loops when DP monitors are connected, indicating that the EDID is corrupt.  The kernel from development doesn't have that specific problem.

The system tested is a Dell Latitude E4200, which has an Intel GM45 chipset.  Additionally, a Dell EPort Plus dock provides two DisplayPort connections.

When a DisplayPort monitor is attached to the system, Xorg records two modelines provided by DDC, "1440x900" and "640x480".  It then reports only "640x480" in the probed modes.  xrandr will show only "640x480" as an available resolution.  According to the smolt output, I believe system memory decreases by 16M when the DisplayPort monitor is connected.

Version-Release number of selected component (if applicable):
kernel 2.6.38-0.rc3.git4.1.fc15.x86_64
xorg-x11-server-Xorg-1.9.3-4.fc14.x86_64
xorg-x11-drv-intel-2.12.0-6.fc14.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Connect DisplayPort monitor
2. Check available resolutions in xrandr or the GNOME monitor application
  
Actual results:
Only 640x480 is listed as an available resolution for the monitor.

Expected results:
The native resolution of 1440x900 should be available and used.

Additional info:

Comment 1 Gordon Messmer 2011-02-07 00:16:55 UTC
Created attachment 477354 [details]
Intel video ROM

Comment 2 Gordon Messmer 2011-02-07 00:17:39 UTC
Created attachment 477355 [details]
Xorg log

Comment 3 Gordon Messmer 2011-02-07 00:18:30 UTC
Created attachment 477356 [details]
dmesg output after DisplayPort monitor connected

Comment 4 Gordon Messmer 2011-02-07 00:19:13 UTC
Created attachment 477357 [details]
messages log from boot until after DisplayPort monitor connected

Comment 5 Gordon Messmer 2011-02-07 00:20:25 UTC
Created attachment 477359 [details]
output of intel_reg_snapshot before DisplayPort monitor connected

Comment 6 Gordon Messmer 2011-02-07 00:21:11 UTC
Created attachment 477360 [details]
output of intel_reg_snapshot after DisplayPort monitor connected

Comment 7 Gordon Messmer 2011-02-07 00:22:01 UTC
Created attachment 477361 [details]
output of smoltSendProfile before DisplayPort monitor connected

Comment 8 Gordon Messmer 2011-02-07 00:22:36 UTC
Created attachment 477362 [details]
output of smoltSendProfile after DisplayPort monitor connected

Comment 9 Desmond 2011-05-30 19:21:04 UTC
Have fedora 15 running on my eee but, whereas the resolution of the screen is 1024x600 it only displays at 800x600.
Surely there should be a utility for setting this?

Comment 10 Matěj Cepl 2011-06-06 15:46:05 UTC
(In reply to comment #0)
> The kernel from development doesn't have that specific problem.

Did you try upgrading to Fedora 15 when it was released by chance? How did it go?

Comment 11 Gordon Messmer 2011-06-06 16:06:55 UTC
I have. I think all of the conditions reported are the same, as I was already using the kernel from F15.  There is still no OOPS, as there was with the F14 kernel.  The display is still initialized at 640x480, and the X setup tools treat this as the only valid resolution.

Comment 12 caz 2011-09-11 23:07:28 UTC
Have you tried with "X.org X Server 1.10.3" which is in f15? I have f15 and my Xorg.0.log has Sandybridge in the line of "intel: Driver for Intel Integrated Graphics Chipset:" while your one does not. I believe the problem is caused by that your X server does not support Sandybridge while your kernel supports Sandybridge.

Comment 13 Gordon Messmer 2011-09-17 22:02:12 UTC
Yes, a fully patched F15 system (1.10.4) exhibits the same behavior.  Sandybridge support is indicated in the Xorg log.

Comment 14 Gordon Messmer 2011-09-17 22:04:41 UTC
... and to clarify, the problem is specific to DisplayPort.  I don't have similar problems with VGA connected displays.

Comment 15 Fedora End Of Life 2012-08-16 12:02:03 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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