Created attachment 328626 [details] Xorg.0.log from broken session Description of problem: Currently in F11 I am getting a black screen for X. The Xorg.0.log file has a complaint about an agp related kernel module. I don't see that module loaded for F10, but maybe it is built in to the kernel. It was working about a week ago and stopped working after a kernel change, so it might really be a kernel bug. vt's work OK. As usual I have to rebuild xorg-x11-drv-ati to work around the driver not liking EDID not being done properly by my monitor. Without this the screen is black because of no signal, with the change I am currently getting a signal, but the screen is still black. I'll be attaching various files from my F10 and F11 instances. Things are working in F10 currently. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.10.0-1.fc11.i386 kernel-2.6.29-0.24.rc0.git13.fc11.i686 How reproducible: 100% Steps to Reproduce: 1. Boot into F11 2. 3. Actual results: Black screen for X display Expected results: Normal session information appearing on display Additional info:
Created attachment 328627 [details] Xorg.0.log from working session on F10
Created attachment 328628 [details] Sorted output from lsmod for broken session on f11
Created attachment 328629 [details] Sorted lsmod output from working session on f10
Created attachment 328630 [details] xorg.conf file I double checked to confirm that the xorg.conf files were identical for F11 and F10. So I am only attaching one of them.
Note that I am able to get the radeon (and vesa driver for F11) working by passing nomodeset using 2.6.29-0.6.rc3.fc10.i686 or 2.6.29-0.73.rc3.git2.fc11.i686.
In rawhide things have now reversed. With kernel 2.6.29-0.78.rc3.git5.fc11.i686 I now must NOT use the nomodeset parameter in order for things to work with the radeon driver. (I didn't retest the vesa driver.)
I am still having modeset problems with this card, but I don't think it is the same problem as this was so I am going to close this bug.