Description of problem:
I've been using "nomodeset" for a while, but today's combination of packages seems to crash with it. I'm not sure which component it is, so I'm guessing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot to runlevel 3 with "nomodeset" (I was also using "enforcing=0", but I don't think that would make a difference here)
2. Log in at the console
3. Run startx
X server crashes
Created attachment 424190 [details]
Xorg.0.log from failed run
Did you have issue with kms ie without nomodeset ? You should consider booting with nomodeset kind of unsupported as it goes right to the bottom of long list of bugs.
Without "nomodeset", the server starts up correctly, yes.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
Created attachment 453068 [details]
Xorg log with the crash
Same issue for me with ATI Radeon X1200 (ChipID = 0x791f). X starts without nomodeset but 3D is funky (as in bugs 579615 and 638779).
Created attachment 462464 [details]
Screenshot of garbled X session with modesetting enabled
Same issue here with:
01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series]
I've been using nomodeset (Since modesetting was initially enabled by default) with the radeon driver to avoid the issue visible in my attachment. Since X will no longer start with nomodeset enabled, I have to start with modesetting which causes my screen to constantly get garbled requiring me to restart X.
Same exact problem here with a fresh insatll of F14 on a Gateway LT3114u with x1270 ATI Radeon hardware. Skipped F13, used nomodeset on f12 to get desired results. Can anything be done or am I stuck with F12?
we don't support nomodeset, we will only fix kms bugs