Bug 6904

Summary: LKM-0162 (AZALEA): broken edid block.
Product: xorg Reporter: Alejandro Zaro <grapequade>
Component: Server/DDX/XorgAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED NOTABUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: libv
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Copy of the log posted at http://librarian.launchpad.net/2582579/Xorg.0.log
none
Copy of conf posted at http://librarian.launchpad.net/2582581/xorg.conf
none
Logs of get-edid, xorg.conf and xorg log file none

Description Alejandro Zaro 2006-05-13 09:54:42 UTC
I have a "Likom/Aqua/Multiscan" L4011ND monitor.
 This 14" monitor is working with 1024x768 only at 60Hz.

In log file of DDC/EDID this is detected correctly.

(II) VIA(0): 640x480@60Hz
(II) VIA(0): 640x480@75Hz
(II) VIA(0): 800x600@56Hz
(II) VIA(0): 800x600@60Hz
(II) VIA(0): 800x600@72Hz
(II) VIA(0): 1024x768@87Hz (interlaced)
(II) VIA(0): 1024x768@60Hz

I have tested with recent Ubuntu Flight 7 release.
It use other frequency (78 Hz or 75 Hz).

 In Control Center I can select 75, 70 and 60 Hz. With 60 Hz is work good.
Also I try to detect the monitor in Control Center (displayconfig) I get
"Plug'n'Play Monitor".

 May be Xorg also trying select interlace mode frequency at 75 Hz that is first
in list of modes, but this card/chip has not supported interlace mode (from
messages in log file Xorg.0.log).

********
This bug was submitted in Ubuntu and has also their log files:
https://launchpad.net/bugs/29291
Comment 1 Alejandro Zaro 2006-05-13 09:56:46 UTC
Sorry if I selected wrong component in bugzilla, please change to correct component.
   Thanks
Comment 2 Luc Verhaegen 2006-05-13 15:17:56 UTC
This is a broken EDID block, it reports:
(II) VIA(0): Ranges: V min: 47  V max: 104 Hz, H min: 30  H max: 65 kHz,
PixClock max 110 MHz

Please provide me with the output of get-edid (part of the read-edid package),
so that the resulting EDID block can feature on
http://people.freedesktop.org/~libv/edid/

Please also use a recent unichrome.sf.net driver version, this will use the edid
information more intelligently: it should be interesting to see how it responds
to your EDID block; it should choose the same resolution at this time though. A
recent unichrome.sf.net will correctly detect the size of your FB memory.
Comment 3 Luc Verhaegen 2006-05-13 15:20:29 UTC
Created attachment 5615 [details]
Copy of the log posted at http://librarian.launchpad.net/2582579/Xorg.0.log
Comment 4 Luc Verhaegen 2006-05-13 15:23:03 UTC
Created attachment 5616 [details]
Copy of conf posted at http://librarian.launchpad.net/2582581/xorg.conf
Comment 5 Alejandro Zaro 2006-05-21 01:34:46 UTC
Created attachment 5698 [details]
Logs of get-edid, xorg.conf and xorg log file 

I've got output of get-edid. 
Also I have put option "DumpDDC" en xorg.conf in Monitor and Device section,
but in /tmp directory I haven't a LKMxxx.edid file.
Comment 6 Alejandro Zaro 2006-05-28 02:23:29 UTC
In this case monitor has these frequencies:
(II) VIA(0): 1024x768@87Hz (interlaced)  - I don't know if this is write o wrong
(II) VIA(0): 1024x768@60Hz 
and videochip (or driver) can not support interlaced mode.

Xorg must select reshresh rate only of non-interlaced mode - it's all write?
Is a problem with "MODEVALIDATION" that pass incorrect mode?

 Which component of Xorg select best frequency of refresh rate for this case?
Is a VIA driver or other component of Xorg? 

PS: I have free time for my Linux machine only at Saturday :-).
Comment 7 Daniel Stone 2007-02-27 01:32:04 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 8 Adam Jackson 2010-05-10 11:11:23 UTC
That's not broken.  87Hz interlaced field rate is 43.5Hz frame rate.  We pick modes with higher frame rates by default.  The driver might not support interlaced modes correctly, but that's not an EDID bug.

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.