I used FedUp to upgrade an old Dell Inspiron 8600 laptop (2Gb RAM, 500Gb SATA) from F17 to F18. FedUp seemed to work fine, but, after the final process finished, and I tried to reboot using the new 3.7 kernel from the GRUB2 menu (which works as expected), all I could see was a white screen with a few thin vertical lines.
When I rebooted using one of the F17 kernels that FedUp hadn't removed, the X-server did not start. However, the normal boot messages (I don't use the rhgb
linux-line option.) were displayed, but the X-server failed to start.
It that point, I could do a Ctrl-Alt-F2 (etc.) to start another TTY, and, from there, the usual startx
could be used to run the X-server.
So I thought that my problem was a bug in the 3.7.2-201 kernel. But then the 3.7.2-204 kernel was released, and it didn't fix the problem.
After that disappointment I thought to download the KDE spin LiveCD. I burned it to a disk, and booted it. The live CD booted, but it also failed to start the X-server. However, the screen wasn't clobbered, so I copied the 3.6.10-4 kernel files from the LiveCD iso file to the /boot directory, ran grub2-mkconfig
, and tried to boot using that kernel.
O.K., maybe it's dracut
. No, I was using the initramfs
from the LiveCD, and the LiveCD display worked.
Since then, I've been playing around with the /etc/vconsole.conf
settings, but I can't seem to find any one that makes a difference.
Oh, I did a full yum upgrade
and, as of today, everything is current.
Any suggestions would be appreciated.