Bug 196758

Summary: nv: DDC fails on laptop LCD, works on external LCD
Product: [Fedora] Fedora Reporter: Andy Burns <fedora>
Component: xorg-x11-drv-nvAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-29 22:06:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xorg log shows failure to choose correct resolution with DDC on internal LCD none

Description Andy Burns 2006-06-26 22:22:00 UTC 
Description of problem:

I'm not sure if this should be logged against Xorg-server, or Xorg-drv-nv?

On encountering screen resolution issue, I was advised by Jesse Keating that
using DDC was the preferred option for FC6, so I should comment out
HorizSync/vertRefresh from xorg.conf to force DDC.

Xorg then *does* use correct 1280x1024 resolution on external DVI LCD Sony
XDM-82 *with* DDC, when it failed without it.

Conversely Xorg then *fails* to use 1280x800 resolution on internal Dell WXGA
LCD *with* DDC, but picks good resolution without DDC.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg.i386                1.1.0-22
xorg-x11-drv-nv.i386                     1.1.2-1

How reproducible:

100%
Comment 1 Andy Burns 2006-06-26 22:22:01 UTC 
Created attachment 131574 [details]
xorg log shows failure to choose correct resolution with DDC on internal LCD
Comment 2 Adam Jackson 2006-08-04 23:09:28 UTC 
Kindly paste or attach the output of running:

find /proc/acpi/video -type f

I'm hoping nv laptops tend to have EDID blocks in ACPI, in which case I have
code to fix this that should be pretty easy to integrate.
Comment 3 Andy Burns 2006-08-04 23:19:16 UTC 
Here is the output for the machine while undocked using onboard LCD panel, do
you need this repeating while it is docked using an external LCD?

[andy@andylaptop ~]$ find /proc/acpi/video -type f
/proc/acpi/video/VID/DVI/EDID
/proc/acpi/video/VID/DVI/brightness
/proc/acpi/video/VID/DVI/state
/proc/acpi/video/VID/DVI/info
/proc/acpi/video/VID/LCD/EDID
/proc/acpi/video/VID/LCD/brightness
/proc/acpi/video/VID/LCD/state
/proc/acpi/video/VID/LCD/info
/proc/acpi/video/VID/CRT2/EDID
/proc/acpi/video/VID/CRT2/brightness
/proc/acpi/video/VID/CRT2/state
/proc/acpi/video/VID/CRT2/info
/proc/acpi/video/VID/CRT/EDID
/proc/acpi/video/VID/CRT/brightness
/proc/acpi/video/VID/CRT/state
/proc/acpi/video/VID/CRT/info
/proc/acpi/video/VID/TV/EDID
/proc/acpi/video/VID/TV/brightness
/proc/acpi/video/VID/TV/state
/proc/acpi/video/VID/TV/info
/proc/acpi/video/VID/DOS
/proc/acpi/video/VID/POST
/proc/acpi/video/VID/POST_info
/proc/acpi/video/VID/ROM
/proc/acpi/video/VID/info
Comment 4 Adam Jackson 2006-08-04 23:35:55 UTC 
Nah, I'm only interested in the LCD panel info.

What do you get from cat /proc/acpi/video/VID/LCD/EDID ?  Real data, or
something like <not supported> ?
Comment 5 Andy Burns 2006-08-05 07:43:26 UTC 
(In reply to comment #4)

> What do you get from cat /proc/acpi/video/VID/LCD/EDID ?  Real data, or
> something like <not supported> ?

I get <not supported>
Comment 6 Adam Jackson 2006-08-07 02:26:49 UTC 
Rrgh, that's less cool.  Do any of the EDID files give anything else?
Comment 7 Andy Burns 2006-08-07 07:44:10 UTC 
Nope :-(

$ cat /proc/acpi/video/VID/*/EDID
<not supported>
<not supported>
<not supported>
<not supported>
<not supported>

is this an ACPI BIOS shortcoming?
Comment 8 Adam Jackson 2006-09-29 22:06:22 UTC 
Yeah, it is.

As of xorg-x11-drv-nv 1.2.0-4, we will notice the native panel size reported by
the BIOS and expand the sync ranges to cover it.  So at least we'll get the
native mode size right.  There's really no fixing that the machine has no way to
report DDC though.

Please test 1.2.0-4 and reopen this bug if it doesn't work automagically for
you.  Thanks!