Red Hat Bugzilla – Bug 513597
UMS:R420:X800 Colour palette borked on ATI Radeon X800 in 16bpp mode
Last modified: 2010-12-07 08:48:07 EST
Description of problem:
When choosing a colour depth of 16, then the GNOME desktop is very dark and colours are distorted. Only the mouse cursor visible on top of it exhibits normal brightness and colours.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start GNOME session.
Desktop and application windows appear dark and the colour palette looks unbalanced.
Normal aspect of GNOME desktop.
Already observed for xorg-x11-drv-ati-6.12.2-19.fc12.x86_64.
The GDM login screen shows the same effect.
Created attachment 355011 [details]
Custom xorg.conf for ATI Radeon X800 and 21" CRT HP A4576A
Created attachment 355012 [details]
Xorg.0.log for ATI Radeon X800 and 21" CRT HP A4576A
Normal colours can be recovered in 16 bpp mode by enabling KMS [which is again possible as of xorg-x11-server-Xorg-1.6.99-26.20090804.fc12.x86_64].
Created attachment 356990 [details]
Xorg.0.log for ATI Radeon X800 and 21" CRT HP A4576A at 15bpp
For 15bpp, colours are correct [as they are for 24bpp].
Created attachment 360161 [details]
Xorg.0.log for ATI Radeon X800 and 21" CRT HP A4576A on F11 w/updates
Colours are correct at 16bpp on a fully updated F11 system including packages:
Thanks for letting us know.
(In reply to comment #7)
The previous comment was meant to inform you that F11 is -not- affected by this issue in contrast with F12/rawhide.
No improvement for current F12-rawhide:
can you try with kernel 220.127.116.11-65 from koji? and ati -7 from rawhide?
No improvement for latest builds:
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
No improvement for the latest "rawhide" builds:
which is not surprising since the Radeon driver hasn't been updated recently.
Joachim do you have issue with kms ? We are focussing on fixing KMS issue.
(In reply to comment #15)
According to comment #4, the answer is no.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
In my environment (radeon driver with ES1000 at F12), this issue was reproduced.
F11 didn't have this problem.
- 1600x1200 @ 16bpp shows very dark display.
- 1280x1024 @ 24bpp shows good.
(In reply to comment #18)
Can you confirm that this issue is related to kernel option "nomodeset", whereas it does not show up when KMS is enabled?
(In reply to comment #19)
No, it doesn't related to "nomodeset" option.
I test with and without "nomodeset" with 16bpp,
both of them showed same dark screens.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Booting the system with kernel option "nomodeset" still triggers the issue for a fully updated F13 including packages:
Does system work without "nomodeset", i.e. in full KMS mode? If yes, this should be WONTFIXed. nomodeset was just a crutch for situation when KMS doesn't work. If KMS works, we don't care about the crutch anymore.