Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why do I need "nomodeset" in my dual-boot (F16, CentOS-6.2) grub?

I've got two Linux systems in my (old) Acer Aspire 3023 laptop. To begin with, they were CentOS-6.0 and Fedora 15. The CentOS system has separate /boot, /home and / (root) partitions, and the Fedora system is implemented with an LVM (logical volume manager). A few weeks ago I upgraded the Fedora system to Fedora 16. Everything still worked but when I updated the CentOS-6.1 to CentOS-6.2, the CentOS system would no longer boot properly. During the boot process, at some point the booting stops and a blank screen remains. At first this would look like a CentOS-6.2 problem but the boot loader in use is the grub2 of Fedora 16. To make a long story short, after some googling I appended the "nomodeset" command (right after 'rhgb quiet') to the /etc/grub.conf of CentOS-6.2 and ran '# grub2-mkconfig > /boot/grub2/grub.cfg' in Fedora 16 to make Fedora's grub2 take notice. Now the CentOS system boots OK even if CentOS-6 theme has changed to Fedora-10 type "growing white bar" at the bottom of the screen. Can anyone explain why the "nomodeset" command is needed in grub.cfg of Fedora 16? As an aside, why does grub2 assume the other OS is always 'msdos' if a computer is a dual-boot system? In my three dual-boot computers only one has Windows XP Pro as an alternative, all others are different Linux distros.

Why do I need "nomodeset" in my dual-boot (F16, CentOS-6.2) grub?

I've got two Linux systems in my (old) Acer Aspire 3023 laptop. To begin with, they were CentOS-6.0 and Fedora 15. The CentOS system has separate /boot, /home and / (root) partitions, and the Fedora system is implemented with an LVM (logical volume manager). A few weeks ago I upgraded the Fedora system to Fedora 16. Everything still worked but when I updated the CentOS-6.1 to CentOS-6.2, the CentOS system would no longer boot properly. During the boot process, at some point the booting stops and a blank screen remains. At first this would look like a CentOS-6.2 problem but the boot loader in use is the grub2 of Fedora 16. To make a long story short, after some googling I appended the "nomodeset" command (right after 'rhgb quiet') to the /etc/grub.conf of CentOS-6.2 and ran '# grub2-mkconfig > /boot/grub2/grub.cfg' in Fedora 16 to make Fedora's grub2 take notice. Now the CentOS system boots OK even if CentOS-6 theme has changed to Fedora-10 type "growing white bar" at the bottom of the screen. Can anyone explain why the "nomodeset" command is needed in grub.cfg of Fedora 16? As an aside, why does grub2 assume the other OS is always 'msdos' if a computer is a dual-boot system? In my three dual-boot computers only one has Windows XP Pro as an alternative, all others are different Linux distros.