| Summary: | xserver-xorg-video-ati (1:6.7.197-1): manual edit of xorg.conf is required. xrandr and xdpyinfo do not correspond to correct ddcprobe EDID info | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Bryan Cebuliak <bryan.cebuliak> | ||||||||
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | a.rottmann | ||||||||
| Version: | 7.3 (2007.09) | ||||||||||
| Hardware: | x86 (IA32) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Bryan Cebuliak
2008-01-08 02:03:32 UTC
Still looks to me like the EDID data from your monitor is bogus. It wouldn't be the first which has the size correct (in cm) in the basic display information block, but fails to provide the correct value (in mm) in the detailed timing blocks. Though that's assuming that EDID 1.0 even has that information (EDID 1.1 certainly does). Please attach your xorg. It looks like your monitor has a bad edid. Created attachment 13599 [details]
Xorg.0.log
Created attachment 13600 [details]
xorg.conf
Attached please find my Xorg.0.log and xorg.conf I do not understand exactly what in the EDID 1.0 output makes you say the EDID is "bad". There appears to be display dimensions in cm and timing data on the ddcprobe in a similar way to my other system's newer monitor using EDID 1.3. Why can not the xorg ati server cope when it did before randr and it does now only with manual editing of xorg? Your bleeding user, Bryan (In reply to comment #1) > Still looks to me like the EDID data from your monitor is bogus. It wouldn't be > the first which has the size correct (in cm) in the basic display information > block, but fails to provide the correct value (in mm) in the detailed timing > blocks. Though that's assuming that EDID 1.0 even has that information (EDID > 1.1 certainly does). > I do not know if the correct information is in the detailed timing blocks. That is why I have sent my logs and ddcprobe and xrandr probes to you programmers to decipher. However, if the driver now so precariously depends on inconsistently formated hardware display information yet the correct size information in cm is still there as you say. Why don't you adapt the driver software accordingly? This issue is not isolated to my old monitor or my ATI graphics card as you know. It is part of a rather large regression of function I think related to the change to Randr. Similar bugs are previously reported for example in Ubuntu and upstream on Intel drivers. See: https://bugs.freedesktop.org/show_bug.cgi?id=10304 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/107320/comments/39 Is this still an issue with a newer xserver? It should handle broken edids better. (In reply to comment #8) > Is this still an issue with a newer xserver? It should handle broken edids > better. > I can confirm that this issue still exists in the following configuration: - On-Board Radeon chip; lspci info: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics - Monitor: Samsung SyncMaster 2333SW (vendor "SAM", prod_id 1246) - radeonhd driver 1.2.5 - xorg-server 1.6.1.901 (from experimental) * Symptoms - ddcprobe shows correct dimensions: "screensize: 51 29" - Xorg seems to know proper size (from Xorg.0.log): (II) RADEONHD(0): Max Image Size [cm]: horiz.: 51 vert.: 29 - But later it somehow comes up with incorrect numbers, which propagate into xpdyinfo: (II) RADEONHD(0): clock: 138.5 MHz Image Size: 477 x 268 mm - xdpyinfo: dimensions: 1920x1080 pixels (477x268 millimeters) - xrandr has the wrong numbers as well: DVI-D_1 connected 1920x1080+0+0 (0x3d) normal (normal left inverted right x axis y axis) 477mm x 268mm I tried adding the monitor to quirk_detailed_use_maximum_size(), but that didn't change anything. I'm getting basically the same thing with X.Org Server 1.4.2 11 June 2008 ATI Technologies Inc RV280 [Radeon 9200 PRO] [1002:5960] Card Shuttle X17 Monitor. By messing with xorg.conf I can get it to a video mode that produces tearing (rather than so far out of sync the monitor bails). But not to a working setup. Created attachment 27750 [details]
ddcprobe of Shuttle XP17 Monitor via DVI
(In reply to comment #10) > I'm getting basically the same thing with > > X.Org Server 1.4.2 11 June 2008 > ATI Technologies Inc RV280 [Radeon 9200 PRO] [1002:5960] Card > Shuttle X17 Monitor. > > By messing with xorg.conf I can get it to a video mode that produces tearing > (rather than so far out of sync the monitor bails). But not to a working > setup. > This is a different issue. Please file a different bug and attach your xorg log and config. not a driver issue. Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server. |
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.