The recent kernel upgrade to 2.6.22.7-85.fc7 apparently breaks video on a Dell Inspiron 6400 with an ATI Mobility Radeon X1400 GPU. When the boot process reaches the point where it would usually switch to graphics instead of text mode the screen goes blank, and the display stays black even when GDM starts. It looks as if it tries to switch between text and graphical mode a couple of times as when the X server is misconfigured. Downgrading to 2.6.22.5-76 makes video work fine again.
I also have problems with kernel-2.6.22.7-85.fc7 - 2.6.22.9-91.fc7 and my Radeon 7200. I boot to run level 3 and all is fine and X starts ok but when I try to drop out of X either by Ctrl+Alt+Fn or ending the X session My monitor displays "Out of Range"--at this point I can restart X by typing in the dark so to speak but the console is unusable until I restart the machine.
Please attach contents of /var/log/dmesg after booting with each kernel.
Created attachment 218181 [details] kernel-2.6.22.9-91.fc7 dmesg after starting X twice.
The DRM issue that appears to be reported in the dmesg attached above could be causing my problems as well. On a kernel before -85, Xorg.0.log contains drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) whereas -85 and -91 go drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed
Created attachment 220081 [details] dmesg from kernel-2.6.22.7-85.fc7 after starting X twice
(In reply to comment #5) > Created an attachment (id=220081) [edit] > dmesg from kernel-2.6.22.7-85.fc7 after starting X twice > Please post dmesg from after starting X with the kernel that works.
The recent 2.6.23.1-10.fc7 update seems to fix the problem on my machine - at least X is able to start again. I still get the entries in Xorg.0.log about it being unable to open /dev/dri/card0, but that's a minor issue relative to X not being able to start at all.