Ask Your Question

Preupgrade Fedora 15 to 16 fails on reboot with blank screen

asked 2011-11-15 11:03:12 -0500

Zug gravatar image

I'm attempting to install Fedora 16 via preupgrade. I had done so from Fedora 14 to 15 previously.

Upon reboot, anaconda is launched and then my screen goes blank and nothing happens. System hangs. Cannot switch to virtual console. Forced to power cycle Asus laptop.

Initially, on reboot garbled images appeared. I found a log which appeared to indicate that the proprietary Nvidia driver was conflicting/monopolizing the display. So, I UNinstalled it via Nvidia's script, which was the way I had installed it. I was not using Fusions rpm.

64 bit install. NVIDIA GeForce GTS 360M video card. Intel I5 cpu. 4 GB's RAM.

I believe this is still a video driver issue. I don't know if it's Nouveau that is dying or what. It wouldn't shock me since I've never been able to get Nouveau to work on NVIDIA hardware.

Is there a way I can force Anaconda to not use Nouveau? Can I make it use the old "nv" driver?

I get no error messages. I can't find a log with an issue it it anymore.

edit retag flag offensive close merge delete

3 Answers

Sort by ยป oldest newest most voted

answered 2011-11-22 16:15:18 -0500

Zug gravatar image

The answer to my problem can be found in the following thread...

Basically, I needed to pass the "nomodeset" parameter to the anaconda installer via grub. That allowed the installation to continue. I needed to do an update using yum via a virtual console as well afterward. In addition, the Nvidia kernel module also had to be installed for the new kernel.

edit flag offensive delete link more

answered 2011-11-22 21:45:50 -0500

I had the same problem. I was able to resolve it by downloading the install DVD. Then I booted from the DVD. When the first menu comes up choose


In that screen choose Basic Video. After that, the installation/upgrade process started normally.

edit flag offensive delete link more

answered 2011-11-15 23:51:18 -0500

asto gravatar image

Did you try reinstalling the proprietory driver? That usually works. Do check if they have a more recent driver before you reinstall the one you already have

edit flag offensive delete link more

Question Tools


Asked: 2011-11-15 11:03:12 -0500

Seen: 2,363 times

Last updated: Nov 22 '11