EDID

[Val]

I had a very similar problem with my upgrade to Ubuntu Fiesty. Although
I didn't figure out how to override the erroneous info coming from the
CRT's EDID, I configured the NVIDIA driver to suppress many of the
checks it does on a candidate graphical mode before putting it into the
mode pool. This works if you already know what modes your CRT can do.

I don't know if you use nvidia, but I assume ATI will have some sort of
an equivalent:

Option "ModeValidation" "CRT-1: NoVertRefreshCheck,
NoDFPNativeResolutionCheck, NoMaxPClkCheck, NoEdidMaxPClkCheck,
NoHorizSyncCheck, NoVirtualSizeCheck;"


On Fri, 2007-06-07 at 14:39 +1000, Russell Shaw wrote:
> Hi,
> I get a corrupt edid with get-edid. I've got a left-hand DVI LCD monitor and
> a right-hand VGA CRT, both of which should work. I was using dual-head merged framebuffer
> ok, but after a debian dist-upgrade, X now only does clone mode because it can't
> configure the VGA CRT.
> 
> 
> get-edid version 1.4.1
> 
>          Performing real mode VBE call
>          Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
>          Function supported
>          Call successful
> 
>          VBE version 200
>          VBE string at 0x11110 "ATI RADEON 9200"
> 
> VBE/DDC service about to be called
>          Report DDC capabilities
> 
>          Performing real mode VBE call
>          Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
>          Function supported
>          Call successful
> 
>          Monitor and video card combination does not support DDC1 transfers
>          Monitor and video card combination does not support DDC2 transfers
>          0 seconds per 128 byte EDID block transfer
>          Screen is not blanked during DDC transfer
> 
> Reading next EDID block
> 
> VBE/DDC service about to be called
>          Read EDID
> 
>          Performing real mode VBE call
>          Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
>          Function supported
>          Call failed
> 
> The EDID data should not be trusted as the VBE call failed
> EDID claims 19 more blocks left
> EDID blocks left is wrong.
> Your EDID is probably invalid.
> parse-edid: parse-edid version 1.4.1
> parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
> parse-edid: first bytes don't match EDID version 1 header
> parse-edid: do not trust output (if any).
> 
>          # EDID version 19 revision 19
> Section "Monitor"
>          Identifier "DXS:1313"
>          VendorName "DXS"
>          ModelName "DXS:1313"
>          # DPMS capabilities: Active off:no  Suspend:no  Standby:no
> 
>          Mode    "275x275"       # vfreq 43.295Hz, hfreq 45.979kHz
>                  DotClock        48.830000
>                  HTimings        275 294 313 1062
>                  VTimings        275 276 327 1062
>          EndMode
>          Mode    "275x275"       # vfreq 43.295Hz, hfreq 45.979kHz
>                  DotClock        48.830000
>                  HTimings        275 294 313 1062
>                  VTimings        275 276 327 1062
>          EndMode
>          Mode    "275x275"       # vfreq 43.295Hz, hfreq 45.979kHz
>                  DotClock        48.830000
>                  HTimings        275 294 313 1062
>                  VTimings        275 276 327 1062
>          EndMode
>          Mode    "275x275"       # vfreq 43.295Hz, hfreq 45.979kHz
>                  DotClock        48.830000
>                  HTimings        275 294 313 1062
>                  VTimings        275 276 327 1062
>          EndMode
> EndSection
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg