Actually over the weekend I did some more investigating of the problem and found that it is not rhgb, but rather it appears to be the use of the framebuffer X modules with my All-In-Wonder Radeon card. I found that even after I had disabled rhgb I still saw the same problem, only now I had to restart the X server to do it. This explains why initially after loading up without rhgb I saw no problems with the virtual terminal, where as with rhgb I saw them immediately after load up, rhgb starts an X server instance and then once it's done the X server is restart for the first login. Considering this I did a few things. I removed all options within XF86config and added nofb to the boot options. Since I also needed to replace my X drivers with the ones from the gatos project so that I can could make use of my video features I did this as well recognizing the chance that this might help also. With the changes I was able to finally make the problem go away and was even able to re-enable rhgb seeing as there is no longer a problem with restart the X server. I intend to investigate this further so that I can isolate exactly what combination of changes are need to alleviate this issue. Once I have, I will post my findings and so that the appropriate people can try to see if there is a better solution that does not require the disabling of any features. As it is, unless a way can be found to make the gatos km module and the Radeon framebuffer device compatible I intend to not make use of the framebuffer, so this will not be a big issue for me. Jason Corekin > Jason Corekin <jason@xxxxxxxxxxxxxxxxx> writes: > >> I just installed Fedora Core 1 and ran into this awesome graphical load up that you were responsible for. Unfortunately I found that after the machine had finished loading up and I went to switch to the first virtual console my screen was completely messed up. > > Strange. Can you file this in bugzilla? > > -Jonathan >
