Red Hat Bugzilla – Bug 174113
screen drawing problems in 24/32bit mode
Last modified: 2007-11-30 17:11:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.10) Gecko/20050811 Fedora/1.7.10-1.1.1.legacy
Description of problem:
Incorrect colours and multiply drawn icons when in millions of colours mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
accept instalation default bit depth.
Actual Results: As description
Expected Results: properly drawn screen
My video card is an ATI Radeon 6800 Pro
Why is it using the vesa driver.
I will attach my xorg.conf file later.
Created attachment 121459 [details]
conf file shows 16 bit only (as the result of a second install after all the
.iso immages had been downloaded)
I suspect that the vesa driver is a leftover from the install process (failsafe)
and at firstboot when you select the resolution and bit depth the vesa driver
gets carried over.
All the video problems dissapearfor me on editing xorg.conf to use the radeon
However there is still a problem using the vesa driver with this hardware.
Should anything be filed against anaconda or firstboot regarding the wrong
I think this is a dupe of bug 174101.
Altered to FC5T2 as this behaviour is still seen on a fresh install of FC5T2.
The significant differance is that the vesa driver now seems to support 24/32
bit colour OK on this hardware.
2 problems here.
1) that vesa driver is getting used instead of radeon
2) bug in fb code which causes display corruption.
There is a bug tracking each of these issues already, although I don't have the
bug ID's handy. The first problem should be fixed in the next driver update,
which should happen sometime this week. The second problem should happen
in a future server package update, sometime in the next week or so.
I'll update the report once both issues are released to rawhide.
Thanks for the report.
Ok, both #1 and #2 from comment #5 are resolved in the latest rpms in
rawhide. They'll be in rawhide on Saturday around noon EST roughly.
*** This bug has been marked as a duplicate of 173357 ***