Activity log for bug #298094

Date Who What changed Old value New value Message
2008-11-14 15:55:50 Malte S. Stretz bug added bug
2008-11-14 15:55:50 Malte S. Stretz bug added attachment 'Xorg.0.log' (X log file)
2008-11-14 15:56:21 Malte S. Stretz bug added attachment 'ddc.txt' (ddcprobe output)
2008-11-14 15:56:50 Malte S. Stretz bug added attachment 'edid.dat' (get-edid output)
2008-11-20 18:38:31 Malte S. Stretz xrandr: bugtargetdisplayname xrandr (Ubuntu) xserver-xorg-video-ati (Ubuntu)
2008-11-20 18:38:31 Malte S. Stretz xrandr: bugtargetname xrandr (Ubuntu) xserver-xorg-video-ati (Ubuntu)
2008-11-20 18:38:31 Malte S. Stretz xrandr: statusexplanation This seems to be a bug in the xserver-xorg-video-radeon driver becasue with xserver-xorg-video-radeonhd I get the full resolution (though other bugs like a wrong frequency of only 60 MHz instead of the needed 108 MHz. I'll open another bug for that issue.
2008-11-20 18:38:31 Malte S. Stretz xrandr: title Bug #298094 in xrandr (Ubuntu): "Wrong resolution though correct EDID/DDC info exists" Bug #298094 in xserver-xorg-video-ati (Ubuntu): "Wrong resolution though correct EDID/DDC info exists"
2008-11-20 18:51:11 Malte S. Stretz bug added attachment 'viewsonic-800pro.html' (viewsonic-800pro.html)
2008-11-20 18:57:20 Malte S. Stretz bug added attachment 'Xorg.0.log' (Xorg.0.log (with radeonhd))
2008-12-03 19:03:17 Bryce Harrington title Wrong resolution though correct EDID/DDC info exists Wrong resolution with RS690 and Nokia 800 Pro+
2008-12-03 19:04:08 Bryce Harrington xserver-xorg-video-ati: status New Confirmed
2008-12-03 19:04:08 Bryce Harrington xserver-xorg-video-ati: importance Undecided Medium
2008-12-03 19:04:08 Bryce Harrington xserver-xorg-video-ati: statusexplanation This seems to be a bug in the xserver-xorg-video-radeon driver becasue with xserver-xorg-video-radeonhd I get the full resolution (though other bugs like a wrong frequency of only 60 MHz instead of the needed 108 MHz. I'll open another bug for that issue.
2009-01-02 23:42:25 Bryce Harrington title Wrong resolution with RS690 and Nokia 800 Pro+ [RS690] Wrong resolution and Nokia 800 Pro+
2009-01-08 04:41:16 Bryce Harrington description Binary package hint: xrandr I've got a Nokia 800 Pro+ monitor here, connected via DVI (with a P&D adapter). It is autoconfigured at a resolution of 1152x864 even though the native resolution is 1280x1024. The latter is also reported both by ddcprobe and read-edid (I'll attach the output). mss@Otherland:~$ xrandr Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 disconnected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1152x864 (0x4e) 81.6MHz h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz v: height 864 start 865 end 868 total 895 clock 60.0Hz mss@Otherland:~$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 mss@Otherland:/usr/src/read-edid-2.0.0$ apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.4~5ubuntu3 Candidate: 1:7.4~5ubuntu3 Version table: *** 1:7.4~5ubuntu3 0 500 http://de.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status Binary package hint: xrandr I've got a Nokia 800 Pro+ monitor here, connected via DVI (with a P&D adapter). It is autoconfigured at a resolution of 1152x864 even though the native resolution is 1280x1024. The latter is also reported both by ddcprobe and read-edid (I'll attach the output). mss@Otherland:~$ xrandr Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 disconnected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1152x864 (0x4e) 81.6MHz h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz v: height 864 start 865 end 868 total 895 clock 60.0Hz mss@Otherland:~$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 mss@Otherland:/usr/src/read-edid-2.0.0$ apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.4~5ubuntu3 Candidate: 1:7.4~5ubuntu3 Version table: *** 1:7.4~5ubuntu3 0 500 http://de.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status parse-edid: parse-edid version 1.4.1 parse-edid: EDID checksum passed. # EDID version 1 revision 2 Section "Monitor" # Block type: 2:0 3:fd # Block type: 2:0 3:ff # Block type: 2:0 3:fc Identifier "NOKIA 800PRO" VendorName "NOK" ModelName "NOKIA 800PRO" # Block type: 2:0 3:fd HorizSync 31-65 VertRefresh 58-62 # Max dot clock (video bandwidth) 110 MHz # Block type: 2:0 3:ff # Block type: 2:0 3:fc # DPMS capabilities: Active off:yes Suspend:yes Standby:yes Mode "1280x1024" # vfreq 60.020Hz, hfreq 63.981kHz DotClock 108.000000 HTimings 1280 1328 1440 1688 VTimings 1024 1025 1028 1066 Flags "+HSync" "+VSync" EndMode # Block type: 2:0 3:fd # Block type: 2:0 3:ff # Block type: 2:0 3:fc EndSection vbe: VESA 3.0 detected. oem: ATI ATOMBIOS vendor: (C) 1988-2005, ATI Technologies Inc. product: RS690 01.00 memory: 16384kb mode: 640x400x256 mode: 640x480x256 mode: 800x600x256 mode: 1024x768x256 mode: 1280x1024x256 mode: 640x480x64k mode: 800x600x64k mode: 1024x768x64k mode: 1280x1024x64k mode: 320x200x64k mode: 1600x1200x256 mode: 1600x1200x32k mode: 1600x1200x64k edid: edid: 1 2 id: 1803 eisa: NOK1803 serial: 00001c27 manufacture: 47 2000 input: analog signal. screensize: 36 29 gamma: 2.200000 dpms: RGB, active off, suspend, standby timing: 720x400@70 Hz (VGA 640x400, IBM) timing: 640x480@75 Hz (VESA) timing: 1024x768@87 Hz Interlaced (8514A) dtiming: 1280x1024@70 monitorrange: 31-65, 58-62 monitorserial: H047007207 monitorname: NOKIA 800PRO
2009-01-08 05:33:11 Bryce Harrington xserver-xorg-video-ati: status Confirmed Triaged
2009-01-08 05:33:11 Bryce Harrington xserver-xorg-video-ati: statusexplanation Hmm, you're right that it's interesting that the resolution is being detected differently by each of the three drivers, and the inconsistency may indeed point to some sort of issue with -ati; I'll upstream it to them for that reason. However, from your description it seems that none of the drivers get it quite perfect. I note that both -ati and -fglrx are seeing the physical screen size as 0x0 mm, which suggests bad EDID; yet -radeonhd is getting valid looking measurements. But you say that radeonhd is getting the wrong refresh rate, which suggests that even it isn't quite perfect. My guess is that your monitor provides EDID that is just slightly out of wack from what the xserver expects, and it's mis-parsing it. Perhaps each of the drivers has some correction code that handles the error condition in a slightly different way, thus causing the range of different results.
2009-01-08 05:44:48 Bryce Harrington xserver-xorg-video-ati: status Triaged Incomplete
2009-01-08 05:44:48 Bryce Harrington xserver-xorg-video-ati: bugtargetdisplayname xserver-xorg-video-ati (Ubuntu) xorg-server (Ubuntu)
2009-01-08 05:44:48 Bryce Harrington xserver-xorg-video-ati: bugtargetname xserver-xorg-video-ati (Ubuntu) xorg-server (Ubuntu)
2009-01-08 05:44:48 Bryce Harrington xserver-xorg-video-ati: statusexplanation Hmm, you're right that it's interesting that the resolution is being detected differently by each of the three drivers, and the inconsistency may indeed point to some sort of issue with -ati; I'll upstream it to them for that reason. However, from your description it seems that none of the drivers get it quite perfect. I note that both -ati and -fglrx are seeing the physical screen size as 0x0 mm, which suggests bad EDID; yet -radeonhd is getting valid looking measurements. But you say that radeonhd is getting the wrong refresh rate, which suggests that even it isn't quite perfect. My guess is that your monitor provides EDID that is just slightly out of wack from what the xserver expects, and it's mis-parsing it. Perhaps each of the drivers has some correction code that handles the error condition in a slightly different way, thus causing the range of different results. Notice how the h/v rates don't match the vendor's advertised capabilities: Via EDID: HorizSync 31-65 VertRefresh 58-62 Via DDC: monitorrange: 31-65, 58-62 Xorg.0.log (radeonhd): (II) RADEONHD(0): Ranges: V min: 58 V max: 62 Hz, H min: 31 H max: 65 kHz, PixClock max 110 MHz Advertised specifications: * Frequency Fh:29-82kHz, Fv:55-86Hz So, what happens if you plug in these values into your xorg.conf? Section "Monitor" ... HorizSync 29 - 82 VertRefresh 55 - 86 EndSection
2009-01-08 05:44:48 Bryce Harrington xserver-xorg-video-ati: title Bug #298094 in xserver-xorg-video-ati (Ubuntu): "[RS690] Wrong resolution and Nokia 800 Pro+" Bug #298094 in xorg-server (Ubuntu): "[RS690] Wrong resolution and Nokia 800 Pro+"
2009-02-11 09:49:00 Bryce Harrington xorg-server: status Incomplete Invalid
2009-03-27 16:26:45 Malte S. Stretz xorg-server: status Invalid Confirmed
2009-03-27 16:26:45 Malte S. Stretz xorg-server: statusexplanation Notice how the h/v rates don't match the vendor's advertised capabilities: Via EDID: HorizSync 31-65 VertRefresh 58-62 Via DDC: monitorrange: 31-65, 58-62 Xorg.0.log (radeonhd): (II) RADEONHD(0): Ranges: V min: 58 V max: 62 Hz, H min: 31 H max: 65 kHz, PixClock max 110 MHz Advertised specifications: * Frequency Fh:29-82kHz, Fv:55-86Hz So, what happens if you plug in these values into your xorg.conf? Section "Monitor" ... HorizSync 29 - 82 VertRefresh 55 - 86 EndSection Sorry, I didn't have time to investigate further (except that adding the lines you wrote didn't help). fglrx worked fine so I didn't have to work on this issue. Until today I upgraded to jaunty where fglrx is obiously broken. Bad news: After I removed every trace of fglrx from my system, both radeon and radeonhd are broken as well. radeonhd displayed a distorted screen, radeon nothing at all. I'll attach the Xorg.logs, both with and without the config lines you posted.
2009-03-27 16:28:21 Malte S. Stretz bug added attachment 'Xorg.0.log.orig' (Xorg.0.log without the sync-lines)
2009-03-27 16:29:03 Malte S. Stretz bug added attachment 'Xorg.0.log' (Xorg.0.log with the sync-lines)
2009-03-27 16:38:19 Malte S. Stretz bug added attachment 'Xorg.0.log' (Xorg.0.log with radeonhd and without the sync lines (ie. default almost-empty xorg.conf works))
2009-05-02 14:30:17 Malte S. Stretz affects xorg-server (Ubuntu) xserver-xorg-video-ati (Ubuntu)
2009-05-02 14:31:51 Malte S. Stretz bug watch added https://bugs.freedesktop.org/show_bug.cgi?id=21521
2009-05-02 14:31:51 Malte S. Stretz bug task added xserver-xorg-driver-ati
2009-05-02 14:37:21 Malte S. Stretz attachment added Xorg.0.log (with radeon 6.12.2-0ubuntu1~xup~1) http://launchpadlibrarian.net/26251546/Xorg.0.log
2009-05-02 15:00:22 Bug Watch Updater xserver-xorg-driver-ati: status Unknown Confirmed
2009-05-02 15:23:21 Malte S. Stretz attachment added Xorg.0.log (with forced screen modes from read-edid, doesn't work) http://launchpadlibrarian.net/26252838/Xorg.0.log
2009-05-03 22:11:21 Tormod Volden xserver-xorg-video-ati (Ubuntu): status Confirmed Fix Committed
2009-05-04 14:12:31 Bug Watch Updater xserver-xorg-driver-ati: status Confirmed Fix Released
2009-05-05 02:42:45 Bryce Harrington xserver-xorg-video-ati (Ubuntu): status Fix Committed In Progress
2009-05-05 02:43:22 Bryce Harrington summary [RS690] Wrong resolution and Nokia 800 Pro+ [RS690] (Needs new -ati) Wrong resolution and Nokia 800 Pro+
2009-05-05 16:27:40 Malte S. Stretz attachment added xserver-xorg-video-ati_6.12.2-0ubuntu1~xup~2~mss.debdiff http://launchpadlibrarian.net/26360896/xserver-xorg-video-ati_6.12.2-0ubuntu1%7Exup%7E2%7Emss.debdiff
2009-05-05 18:22:29 Bryce Harrington xserver-xorg-video-ati (Ubuntu): status In Progress Fix Committed
2009-05-05 18:25:07 Launchpad Janitor xserver-xorg-video-ati (Ubuntu): status Fix Committed Fix Released
2010-01-13 04:46:11 Launchpad Janitor branch linked lp:ubuntu/xserver-xorg-video-ati
2010-09-14 05:17:46 Bug Watch Updater xserver-xorg-driver-ati: importance Unknown Medium
2011-01-25 15:45:05 Bug Watch Updater xserver-xorg-driver-ati: importance Medium Unknown
2011-02-03 18:48:28 Bug Watch Updater xserver-xorg-driver-ati: importance Unknown Medium