Can't boot into F16 after updates

[gallicbear]

I am a frustrated newbie. Have an HP g6-1660us Notebook with a radeon HD 6480G video card. My newly installed system was working great after fixing the video card problems thru a proprietary driver. Then I downloaded updates and installed them. Since then I have not been able to boot into Fedora 16. My grub2 bootloader shows a menu with 2 different kernels and 2 recovery items, but neither one gets me into the system. The GRub2 loader goes through its process and then I get a black screen. I can boot into the recovery console and wonder if editing the xorg.conf will help. But I do not know how to do that. Please help! Thanks and regards.

[SteveGYBE]

Sounds like a common issue with Radeon. Does this help get you working again?

Originally Posted by Fenrin

when the grub menu appears at boot, try to edit the fedora entry (select it and press e) and then add 3 to the line where it says:

linux /boot/vmlinuz[...] rhgb quiet

so that it looks like this:

linux /boot/vmlinuz[...] rhgb quiet 3

of course [...] is just a gap; there is something different, which you should keep like it is.
to boot it, press the F10 key (in grub legacy it's different, but I assume you use grub 2, which is used in Fedora 16)

Then it should boot into console mode. Login as root or user and as root use the following command to uninstall kmod-catalyst:

yum remove *catalyst*

and update your system, maybe your problems are solved if you use a newer kernel:

yum update

[gallicbear]

Thanks. I was able to login as root with appending a 3. However, it is telling me there is no catalyst to remove.
I have tried aticonfig --initial; it is telling me there is a gl-- something in my preferences, and it saved some backup for my xorg.conf. Then I ran Xorg. Nothing... Just a black screen.

[Elmware]

I've had this problem whenever XORG is updated. To resolve it, I boot into single user mode and reinstall the drivers then reboot and everything is back to normal.

If you don't know how to boot into single user mode, then check this link out.

[gallicbear]

Thanks, Elmware. That is what I did. And it worked. Although I first uninstalled the faulty driver. Somehow, after much research I found out that xorg.conf was messed up with wrong settings. After the uninstall, I had a generic driver with vesa. That gave me a graphical screen again. From there I reinstalled the ati/amd driver and now things are fine. I'll know next time this happens.