Bug 12844 - Gutsy: Display is washed out, too bright. No adjustment will correct for over bright display
Summary: Gutsy: Display is washed out, too bright. No adjustment will correct for over...
Status: RESOLVED DUPLICATE of bug 1082
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 12912 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-17 21:01 UTC by Bryan Cebuliak
Modified: 2007-11-16 08:05 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg log (198.93 KB, patch)
2007-10-18 12:59 UTC, Bryan Cebuliak
no flags Details | Splinter Review
Xorg log file (49.41 KB, text/plain)
2007-10-22 01:08 UTC, Vincent Bernat
no flags Details
Xorg log of the affected X session (38.52 KB, text/x-log)
2007-10-22 02:18 UTC, Mart Raudsepp
no flags Details

Description Bryan Cebuliak 2007-10-17 21:01:13 UTC
See:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-driver-ati/+bug/152312
Following an upgrade from Feisty on Kubuntu, the display now appears too washed out such that "greyed-out" text is invisible in most colour schemes (the text in this window is only just visible!). No amount of adjustment of the monitor controls will bring the display back to it's former state under Feisty. Altering the gamma setting in /etc/X11/x.org.conf or via xgamma to a value of about 0.4 - 0.5 will improve matters slightly but this was not required in previous releases.

I installed the "ubuntu-desktop" meta package and got the same results under GDM/Gnome desktop.

Hardware is a Asus Pundit-R with onboard ATI Radeon 9100 IGP

x.org driver is "ati"
 Bryan Cebuliak wrote 21 hours ago: (permalink)

I can confirm this bug also following a recent network upgrade from Feisty to Gutsy. Moreover, the auto adjust button on my Polyview V293 LCD adjusts nicely then is immediately over ridden.
my lspci :
lspci
00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02)
00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge
00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01)
00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01)
00:13.2 USB Controller: ATI Technologies Inc EHCI USB Controller (rev 01)
00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 17)
00:14.1 IDE interface: ATI Technologies Inc ATI Dual Channel Bus Master PCI IDE Controller
00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c
00:14.4 PCI bridge: ATI Technologies Inc Unknown device 4342
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP
02:05.0 RAID bus controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
02:06.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)

my xorg.conf:
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc104"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "ATI Technologies Inc Radeon 9100 IGP"
 Driver "ati"
 BusID "PCI:1:5:0"
EndSection

Section "Monitor"
 Identifier "CMC 19 AD"
 Option "DPMS"
 HorizSync 30-82
 VertRefresh 56-76
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI ...

Read more...
 Bryan Cebuliak wrote 4 hours ago: (permalink)

Note the Gutsy xorg packages used:
Package xserver-xorg-core
   * gutsy (x11): X.Org X server -- core server
     2:1.3.0.0.dfsg-12ubuntu8: amd64 i386 powerpc
Package xserver-xorg-video-ati
   * gutsy (x11): X.Org X server -- ATI display driver
     1:6.7.195-1ubuntu2: amd64 i386 powerpc

Compared to Feisty packages:
Package xserver-xorg-core
   * feisty (x11): X.Org X server -- core server
     2:1.2.0-3ubuntu8: amd64 i386 powerpc
Package xserver-xorg-video-ati
   * feisty (x11): X.Org X server -- ATI display driver
     1:6.6.3-2ubuntu6: amd64 i386 powerpc

Using the gutsy VESA driver fixes the washout problem at the cost of
poorer resolution.
The same system has no problem running current Debian Sid with
xserver-xorg-video-ati 1:6.6.6.193-3 and xserver-xcore 2:1.4-3.
 Bryan Cebuliak wrote 1 hours ago: (permalink)

I note that the 1:6.7.195-1ubuntu2 is from Debian experimental [ !?] which has been updated since due to this bug which may or may not be relevant:
https://bugs.freedesktop.org/show_bug.cgi?id=12720

see also :
http://packages.debian.org/changelogs/pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.7.195-2/changelog
and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445746
Comment 1 Marcus Better 2007-10-18 00:33:12 UTC
This looks similar to my problem [1] with washed-out colours on the external VGA monitor (but the laptop panel is fine). Can someone confirm if it's likely to be the same bug?

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440174
Comment 2 Alex Deucher 2007-10-18 06:56:25 UTC
(In reply to comment #1)
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440174
> 

This looks like the same bug.  Bryan, can you attach your xorg log?
Comment 3 Bryan Cebuliak 2007-10-18 12:59:29 UTC
Created attachment 12110 [details] [review]
xorg log

Attached is Xorg.0.log
Note this was created using:
     xserver-xorg-video-ati_6.7.195~git20071017tv
the "upstream update"
from:
https://wiki.ubuntu.com/XorgOnTheEdge
http://ppa.launchpad.net/tormodvolden/ubuntu/pool/main/x/xserver-xorg-video-ati/

Which made no difference at all to the washed out appearance compared
to the current standard gutsy deb.
Comment 4 Vincent Bernat 2007-10-22 01:08:33 UTC
Created attachment 12146 [details]
Xorg log file

I have the same problem with ATI Radeon 7500 and two Dell E176FP.
Comment 5 Mart Raudsepp 2007-10-22 02:18:04 UTC
Created attachment 12148 [details]
Xorg log of the affected X session

I experience problems that I would describe in the same way. That's with a ATI Technologies Inc RC410 [Radeon Xpress 200] over an analog CRT link. The same monitor used to work fine over a DVI link with a radeon 9250, but unfortunately didn't try the CRT link at the time. The Xpress is lacking a DVI output connector.
Comment 6 Alex Deucher 2007-10-22 08:03:27 UTC
Does switching to another VT and back again to X fix it?  How about blanking the monitors with dpms?
Comment 7 Marcus Better 2007-10-22 23:09:37 UTC
Switching to another VT and back does not help for me.
Comment 8 Vincent Bernat 2007-10-23 04:12:53 UTC
(In reply to comment #6)
> Does switching to another VT and back again to X fix it?  How about blanking
> the monitors with dpms?
> 

Blanking with DPMS does not help. Switching to VT freezes the station.
Comment 9 Alex Deucher 2007-10-24 21:14:44 UTC
*** Bug 12912 has been marked as a duplicate of this bug. ***
Comment 10 Alex Deucher 2007-11-12 14:55:27 UTC

*** This bug has been marked as a duplicate of bug 1082 ***
Comment 11 Simon 'corecode' Schubert 2007-11-12 15:20:57 UTC
Are you sure this is a duplicate?  Bug 1082 is much older, but this one appeared only recently, so I don't think this is the same issue.

To recap, (from bug 12912), I was able to fix my problem to revert to an older driver version.
Comment 12 Arnaud Lacombe 2007-11-14 06:44:31 UTC
I'm also experiencing the regression in 6.7.19x. Here is a diff of the output of 'radeontool regs' from a working driver (IIRC 6.6.3) and almost latest.

% diff -u working fail
--- working     2007-11-14 14:25:11.000000000 +0000
+++ fail        2007-11-14 14:32:58.000000000 +0000
@@ -1,10 +1,10 @@
 RADEON_DAC_CNTL=ff002102
-RADEON_DAC_CNTL2=00000023
-RADEON_TV_DAC_CNTL=00280203
-RADEON_DISP_OUTPUT_CNTL=10000000
+RADEON_DAC_CNTL2=00000022
+RADEON_TV_DAC_CNTL=00000203
+RADEON_DISP_OUTPUT_CNTL=00000000
 RADEON_CONFIG_MEMSIZE=08000000
 RADEON_AUX_SC_CNTL=00000000
-RADEON_CRTC_EXT_CNTL=00008048
+RADEON_CRTC_EXT_CNTL=00008040
 RADEON_CRTC_GEN_CNTL=03210600
 RADEON_CRTC2_GEN_CNTL=02210680
 RADEON_DEVICE_ID=00075c63
@@ -14,4 +14,4 @@
 RADEON_GPIO_CRT2_DDC=00000300
 RADEON_GPIO_DVI_DDC=00000300
 RADEON_GPIO_VGA_DDC=00000300
-RADEON_LVDS_GEN_CNTL=0880000a
+RADEON_LVDS_GEN_CNTL=0800000a
Comment 13 Arnaud Lacombe 2007-11-14 07:19:41 UTC
heads-up: I tracked down the regression to somewhere between ati-6.6.192 and ati-6.6.192
Comment 14 Alex Deucher 2007-11-14 07:28:50 UTC
(In reply to comment #12)
> I'm also experiencing the regression in 6.7.19x. Here is a diff of the output
> of 'radeontool regs' from a working driver (IIRC 6.6.3) and almost latest.

We'll need to see a full dump of regs (./radeontool regdump '*').  grab the latest version of radeontool here:
http://gitweb.freedesktop.org/?p=users/airlied/radeontool.git;a=summary

*** This bug has been marked as a duplicate of bug 1082 ***
Comment 15 Alex Deucher 2007-11-14 07:30:07 UTC
(In reply to comment #13)
> heads-up: I tracked down the regression to somewhere between ati-6.6.192 and
> ati-6.6.192
> 

Ummm, looks like a typo.  Can you identify the commit(s)?
Comment 16 Arnaud Lacombe 2007-11-14 07:44:54 UTC
yes, sorry for the typo, I meant .193. I 'git bisect' it, and tracked it down to 104105fee5c3945d3f210e6a4cb73ab492c61543.
Comment 17 Alex Deucher 2007-11-14 08:00:03 UTC
(In reply to comment #16)
> yes, sorry for the typo, I meant .193. I 'git bisect' it, and tracked it down
> to 104105fee5c3945d3f210e6a4cb73ab492c61543.
> 

Thank you for tracking this down. Looks like we are setting up the tv dac wrong wrong.  I'll commit a fix soon.
Comment 18 Alex Deucher 2007-11-15 20:28:54 UTC
please try again with ati git master.  I think I've fixed this.
Comment 19 Vincent Bernat 2007-11-16 01:05:10 UTC
(In reply to comment #18)
> please try again with ati git master.  I think I've fixed this.
> 

I have applied the latest patch from git and this works for me. The screen is now darker but this is far more reasonable.
Comment 20 Mart Raudsepp 2007-11-16 06:21:19 UTC
(In reply to comment #18)
> please try again with ati git master.  I think I've fixed this.

Works great with `git diff a94123f..49055d8` (your MT and BGADJ/DACADJ fixes in two commits) applied on top of 6.7.196. Brightness is fine too, just as expected to my current brightness setting in LCD onscreen settings. So basically as good picture as with 6.6.3 (which I finally got to work two days ago here for a bearable picture), just with all the other improvements (not requiring a custom modeline for starters). So, many thanks!

/me awaits a release and considers poking dberkholz to let him include this in gentoo tree meanwhile
Comment 21 Arnaud Lacombe 2007-11-16 08:05:21 UTC
works fine for me also, thanks alex :)


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.