[r200] Strange tremor on the monitor

[Javier Jardón]

Binary package hint: xserver-xorg-driver-ati

Ubuntu Lucid with ATI FireGl 8800 card (r200 chip).

lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QH [Radeon 8500] (rev 80)

My monitor model is an HP p1120
-HorizSync 30-121
-VertRefresh 48-160

Since I installed intrepid I have a temblor in my monitor (In the other Ubuntu releases it works great). It is especially visible at the edges of the windows.
It is very strange because all seems to be correct (with the default xorg.conf configuration):
 - Resultion is on the default 1600x1200
 - The vertical refresh rate is on the default 85Hz
 - The horizontal refresh rate is on 106.3kHz

I try to configure the HorizSync and VertRefresh manually editing the /etc/X11/xorg.conf file but nothing changes

The tremor is only in 1600x1200 resolution.
The others resolutions works well

In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is no tremor

[Tormod Volden (tormodvolden)]

Thanks for your bug report. Would you be able to attach a log from a Ubuntu release where it worked fine?

This could be a problem with calculated PLL values, AFAIK.

[Javier Jardón (jjardon)]

Sure, attached Xorg.0.log from Ubuntu8.04.1 Live/CD

[Tormod Volden (tormodvolden)]

Thanks. I could not spot anything in particular. Can you please try adding
 Option "ModeDebug" "true"
to the Device section of xorg.conf, and attach the two new logs?

[Javier Jardón (jjardon)]

I tried with Ubuntu 8.10 LiveCD to see if it's a kwin problem but the problem persist

[Tormod Volden (tormodvolden)]

Looks like in the "good" case, an initial resolution of 1280x1024 is picked, versus 1600x1200 in the bad case. I guess it looks as good in 8.10 if you choose 1280x1024 as it does in 8.04.1?

Can you please verify, with for instance "xrandr" which resolutions you are using in the different cases?

[Tormod Volden (tormodvolden)]

The "DDC gathered Modelines" are a bit different in the two cases.

And there's "Using hsync ranges from config file" in the bad case. Do you have sync ranges in your xorg.conf? Please use the same (or empty) xorg.conf in both cases.

[Javier Jardón (jjardon)]

Hello Tormod,

>Looks like in the "good" case, an initial resolution of 1280x1024 is picked, versus 1600x1200 in the bad case. I guess it >looks as good in 8.10 if you choose 1280x1024 as it does in 8.04.1?

No, if I change the resolution in 8.10 the problem persist.
(8.04.1 LiveCD uses 1280x1024 and not the best resolution 1600x1200, instead 8.10 LiveCD uses the best resolution 1600x1200)

>And there's "Using hsync ranges from config file" in the bad case. Do you have sync ranges in your xorg.conf? Please use >the same (or empty) xorg.conf in both cases.

No, both xorg.conf files are empty

[Javier Jardón (jjardon)]

I installed the latest drivers from your PPA (xserver-xorg-video-radeon_1:6.9.0.91+git20081227.eccf3fed-0ubuntu0tormod~intrepid_i386.deb) and the problem persist.

[Javier Jardón (jjardon)]

Upgraded to you latest PPA packages:

 - xserver-xorg-video-ati_6.10.0-1~intrepid_i386.deb
 - xserver-xorg-video-radeon_6.10.0-1~intrepid_i386.deb

And the problem persist. Xorg.0.log attached

[Bryce Harrington (bryce)]

There are some modeline differences between the good and bad cases:

-(II) RADEON(0): Modeline "1800x1440"x80.0 298.50 1800 1944 2136 2472 1440 1443 1450 1510 -hsync +vsync (120.8 kHz)
-(II) RADEON(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
-(II) RADEON(0): Modeline "1280x1024"x84.8 159.50 1280 1376 1512 1744 1024 1027 1034 1078 -hsync +vsync (91.5 kHz)
-(II) RADEON(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
-(II) RADEON(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
-(II) RADEON(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
+(II) RADEON(0): Modeline "1800x1440"x80.0 299.95 1800 1944 2144 2488 1440 1441 1444 1507 -hsync +vsync (120.6 kHz)
+(II) RADEON(0): Modeline "1600x1200"x75.0 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -hsync +vsync (94.0 kHz)
+(II) RADEON(0): Modeline "1280x1024"x85.0 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -hsync +vsync (91.4 kHz)
+(II) RADEON(0): Modeline "1024x768"x85.0 94.39 1024 1088 1200 1376 768 769 772 807 -hsync +vsync (68.6 kHz)
+(II) RADEON(0): Modeline "800x600"x85.0 56.55 800 840 928 1056 600 601 604 630 -hsync +vsync (53.5 kHz)
+(II) RADEON(0): Modeline "640x480"x85.0 35.71 640 672 736 832 480 481 484 505 -hsync +vsync (42.9 kHz)

-(II) RADEON(0): Modeline "1800x1440"x80.0 298.50 1800 1944 2136 2472 1440 1443 1450 1510 -hsync +vsync (120.8 kHz)
-(II) RADEON(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
-(II) RADEON(0): Modeline "1280x1024"x84.8 159.50 1280 1376 1512 1744 1024 1027 1034 1078 -hsync +vsync (91.5 kHz)
-(II) RADEON(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
-(II) RADEON(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
-(II) RADEON(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
+(II) RADEON(0): Modeline "1800x1440"x80.0 299.95 1800 1944 2144 2488 1440 1441 1444 1507 -hsync +vsync (120.6 kHz)
+(II) RADEON(0): Modeline "1600x1200"x75.0 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -hsync +vsync (94.0 kHz)
+(II) RADEON(0): Modeline "1280x1024"x85.0 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -hsync +vsync (91.4 kHz)
+(II) RADEON(0): Modeline "1024x768"x85.0 94.39 1024 1088 1200 1376 768 769 772 807 -hsync +vsync (68.6 kHz)
+(II) RADEON(0): Modeline "800x600"x85.0 56.55 800 840 928 1056 600 601 604 630 -hsync +vsync (53.5 kHz)
+(II) RADEON(0): Modeline "640x480"x85.0 35.71 640 672 736 832 480 481 484 505 -hsync +vsync (42.9 kHz)

I bet the modeline is just slightly invalid in this case, and that causes the trembling behavior.

[Bryce Harrington (bryce)]

Can you see what happens if you plug this modeline into your xorg.conf? If this makes the issue go away, then we can forward the issue usptream; perhaps the xserver is miscalculating things.

Modeline "1600x1200_75" 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync

[Javier Jardón (jjardon)]

No, the problem persist :-/

I use the gtf tool in hardy (my monitor works good):

$gtf 1600 1200 85

to generate the modelines:

# 1600x1200 @ 85.00 Hz (GTF) hsync: 107.10 kHz; pclk: 234.76 MHz
Modeline "1600x1200_85.00" 234.76 1600 1720 1896 2192 1200 1201 1204 1260 -HSync +Vsync

I put this in xorg.conf file and now the temblor is worse and, the most important, the horizontal refresh rate is on 107.10, not 106.3kHz.

Do you need any more log/test?

[Bryce Harrington (bryce)]

Hi torkiano,

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

[Javier Jardón (jjardon)]

Hello Bryce,

lspci -vvnn attached

[Javier Jardón (jjardon)]

Kubuntu Intrepid with ATI FireGl 8800 card (r200 chip)

lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QH [Radeon 8500] (rev 80)

My monitor model is an HP p1120
-HorizSync 30-121
-VertRefresh 48-160

Since I installed intrepid I have a temblor in my monitor (In the other Ubuntu releases it works great). It is especially visible at the edges of the windows.
It is very strange because all seems to be correct (with the default xorg.conf configuration):
 - Resultion is on the default 1600x1200
 - The vertical refresh rate is on the default 85Hz
 - The horizontal refresh rate is on 106.3kHz

I try to configure the HorizSync and VertRefresh manually editing the /etc/X11/xorg.conf file but nothing changes

In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is no tremor

Please see the bug reported in launchpad: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/313525

[Javier Jardón (jjardon)]

Tormod,

in the last log with latest xorg driver (Xorg.0.log_6.10.0-1) I can see:

(II) RADEON(0): Using EDID range info for horizontal sync
(II) RADEON(0): Using EDID range info for vertical refresh

[Tormod Volden (tormodvolden)]

Yes, it has been using EDID info all the time, but it interprets it differently. Like I said above, the "DDC gathered Modelines" are a bit different in the two cases. (The EDID is collected via DDC.)

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Of particular interest is that the "DDC gathered Modelines" are a bit different in the working and not working case:

-(II) RADEON(0): Modeline "1800x1440"x80.0 298.50 1800 1944 2136 2472 1440 1443 1450 1510 -hsync +vsync (120.8 kHz)
-(II) RADEON(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
-(II) RADEON(0): Modeline "1280x1024"x84.8 159.50 1280 1376 1512 1744 1024 1027 1034 1078 -hsync +vsync (91.5 kHz)
-(II) RADEON(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
-(II) RADEON(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
-(II) RADEON(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
+(II) RADEON(0): Modeline "1800x1440"x80.0 299.95 1800 1944 2144 2488 1440 1441 1444 1507 -hsync +vsync (120.6 kHz)
+(II) RADEON(0): Modeline "1600x1200"x75.0 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -hsync +vsync (94.0 kHz)
+(II) RADEON(0): Modeline "1280x1024"x85.0 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -hsync +vsync (91.4 kHz)
+(II) RADEON(0): Modeline "1024x768"x85.0 94.39 1024 1088 1200 1376 768 769 772 807 -hsync +vsync (68.6 kHz)
+(II) RADEON(0): Modeline "800x600"x85.0 56.55 800 840 928 1056 600 601 604 630 -hsync +vsync (53.5 kHz)
+(II) RADEON(0): Modeline "640x480"x85.0 35.71 640 672 736 832 480 481 484 505 -hsync +vsync (42.9 kHz)

-(II) RADEON(0): Modeline "1800x1440"x80.0 298.50 1800 1944 2136 2472 1440 1443 1450 1510 -hsync +vsync (120.8 kHz)
-(II) RADEON(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
-(II) RADEON(0): Modeline "1280x1024"x84.8 159.50 1280 1376 1512 1744 1024 1027 1034 1078 -hsync +vsync (91.5 kHz)
-(II) RADEON(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376 768 771 775 809 -hsync +vsync (68.7 kHz)
-(II) RADEON(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600 603 607 633 -hsync +vsync (53.7 kHz)
-(II) RADEON(0): Modeline "640x480"x84.6 35.00 640 664 728 816 480 483 487 507 -hsync +vsync (42.9 kHz)
+(II) RADEON(0): Modeline "1800x1440"x80.0 299.95 1800 1944 2144 2488 1440 1441 1444 1507 -hsync +vsync (120.6 kHz)
+(II) RADEON(0): Modeline "1600x1200"x75.0 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -hsync +vsync (94.0 kHz)
+(II) RADEON(0): Modeline "1280x1024"x85.0 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -hsync +vsync (91.4 kHz)
+(II) RADEON(0): Modeline "1024x768"x85.0 94.39 1024 1088 1200 1376 768 769 772 807 -hsync +vsync (68.6 kHz)
+(II) RADEON(0): Modeline "800x600"x85.0 56.55 800 840 928 1056 600 601 604 630 -hsync +vsync (53.5 kHz)
+(II) RADEON(0): Modeline "640x480"x85.0 35.71 640 672 736 832 480 481 484 505 -hsync +vsync (42.9 kHz)

[Javier Jardón (jjardon)]

Hello Tormod, thank you for your support

Upgraded to you latest PPA packages:

 - xserver-xorg-video-radeon_6.10.0.99+git20090114.0e69068a-0ubuntu0tormod~intrepid_i386.deb
 - xserver-xorg-video-ati_6.10.0.99+git20090114.0e69068a-0ubuntu0tormod~intrepid_i386.deb

And the problem persist. Xorg.0.log_6.10.0.99+git20090114 attached

[Tormod Volden (tormodvolden)]

Thanks. It seems like this is a regression in the xserver then, independent of the driver version.

[Tormod Volden (tormodvolden)]

Actually it would be a better way to rule out the driver if you install the latest PPA ati/radeon driver on the Ubuntu 8.04 live CD and verify that it works fine.

[Javier Jardón (jjardon)]

Hello Tormod,

I've installed your latest ati drivers in a ubuntu 8.04.2 live CD. All work fine.

Xorg.0.log_8.04.2 and Xorg.0.log_8.04.2_latest attached

[Tormod Volden (tormodvolden)]

Thanks, that should prove that the regression really is in the xorg-server and not in the ati driver, since both old and new ati drivers work in Hardy.

[Javier Jardón (jjardon)]

I've installed latest ati drivers in a ubuntu 8.04.2 live CD. All work fine.That should prove that the regression really is in the xorg-server and not in the ati driver, since both old and new ati drivers work in Hardy.

See https://bugs.launchpad.net/bugs/313525 for more details

[Javier Jardón (jjardon)]

Hello,

I've tried jaunty alpha6 and the bug persist
Log Xorg.0.log_9.04_alpha6 attached

[Javier Jardón (jjardon)]

Hello,

I've tried jaunty alpha6 and the bug persist
Log Xorg.0.log_9.04_alpha6 attached

[Javier Jardón (jjardon)]

Tried in Ubuntu jaunty (9.04) with latest updates and the problem persist

xorg version: Version: 1:7.4~5ubuntu18

[Javier Jardón (jjardon)]

Hello Bryce,

I've removed the kubuntu tag because this is not a specific kubuntu bug.
I'm using Ubuntu Jaunty actually.

Regards

[Javier Jardón (jjardon)]

I've installed the latest xorg-core package from here: https://launchpad.net/~xorg-edgers/+archive/ppa

xorg-server - 2:1.6.3+git20090805+server-1.6-branch.f274e595-0ubuntu0sarvatt3~jaunty

and the problem persist :/

[Javier Jardón (jjardon)]

Tried in latest Ubuntu Karmic (9.10) and the problem persist

xserver-xorg-core version: Version: 2:1.6.3-1ubuntu4

[Javier Jardón (jjardon)]

The tremor is only in 1600x1200 resolution.
The others resolutions works well

[Javier Jardón (jjardon)]

In Ubuntu karmic now: the problem persiste, but only when I set 1600x1200 resolution (monitor default)

[Javier Jardón (jjardon)]

xserver-xorg-core Version: 2:1.6.3-1ubuntu5

[Javier Jardón (jjardon)]

Updated to latest packages from here: https://launchpad.net/~xorg-edgers/+archive/ppa
and the problem persist

Xorg_1.6.3+git20090805+server-1.6-branch.f274e595-0ubuntu0sarvatt.log attached

[Javier Jardón (jjardon)]

Tested in 1.6.4 version and the bug is still valid

[Javier Jardón (jjardon)]

Tested with 1.7.99.2~git20091211 and the bug is still valid

[Javier Jardón (jjardon)]

This is still a valid bug in karmic final

[Javier Jardón (jjardon)]

Still valid in the latest xserver package: 1.7.99.2~git20091211.a72c65e9-0ubuntu0tormod (using xorg-edgers PPA)

[Javier Jardón (jjardon)]

Xorg.0.log for 1.7.99.2~git20091211 driver

[Jeremy Sequoia (jeremyhu)]

Can you provide a server log for a working state and a broken state for
comparison? What version change introduces the problem? A new radeon driver
or a new server?

[Bugzi11-fdo-tormod (bugzi11-fdo-tormod)]

The reporter answered these questions in comment 2. The logs in the downstream bug indicates it broke between xserver 1.4.0.90 and 1.5.2.

[penalvch (penalvch)]

Javier Jardón, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ajax-a (ajax-a)]

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.

[Paul White (paulw2u)]

The Ubuntu task has been incomplete for over eight years
Upstream report was closed over four years ago due to inactivity
Reporter did not respond with requested information in comment #45
Closing as 'Invalid'