Red Hat Bugzilla – Bug 105713
Bad X config from anaconda
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b)
Gecko/20030516 Mozilla Firebird/0.6
Description of problem:
Anaconda display works correctly when installing but ultimately boots into
"garbage display". I've tried a number of generic settings and the anaconda
default. If I remove my Xconfig file and run redhat-config-xfree86 if seems to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Linux
2. Boot into Linux
3. Graphical boot and first boot are not displaied correctly.
4. Remove X config file.
Actual Results: Display is garbage before doing redhat-config-xfree86.
Expected Results: Display works in anaconda, it sould also work on first boot.
Created attachment 94764 [details]
Anaconda X config file
Here is the file anaconda generates.
Added the Xconfig file anaconda generates.
Can you add the working XFree86 config file as well?
Created attachment 94769 [details]
Working config created to redhat-config-xfree86
Addached working config created by redhat-config-xfree86. It uses a generic
monitor, but I can then go in and select Dell M991 or something else and it
So, if you use the one generated by anaconda, and switch it to 16bpp, does it work?
16 as is Depth and DefaultDepth under the screen section? No that did not work.
Update: I rebotted with the 16 bit setting and its working now. I guess I didn't
fully restart X or something perviosuly.
To clarify... The anaconda file with 16bit depth is working after reboot.
Tested again using all anaconda defaults (+ generic monitor) and the X config
was hosed. Changed to 16bpp and restared X and it was working again. Perhaps
anaconda should write the default to be 16bpp.
Yep, still a problem in test3.
Fixed in CVS so that some older chips will get 16bpp by default instead of 24