eldiener
August 20th, 2009, 09:16 AM
I am using Paragon Partition Manager 10.0 Professional.
I successfully install Fedora 11. The /boot partition, setup to use GRUB, is in an extended partition on my first hard drive. The partition is labelled for easy identifying with Boot Manager.
When I reboot and the Boot Manager screen appears, it successfully shows me a boot manager item at the labelled boot partition. But instead of saying "GRUB", as two other Linux distributions which I can successfully boot from Boot Manager do, it says "Linux" instead. It strongly looks like it thinks this is a LILO boot rather than GRUB. When I try booting this partition, no GRUB screen appears, the first line says "This is an ancient...." something ( the screen scrolls too fast and the keyboard can not control it ), and the boot fails.
It looks like Boot Manager thinks this is LILO rather than GRUB and boots it incorrectly. Alternatively the installation may have been flawed but no one else has encountered this from the Fedora 11 installation that I can see.
Has anyone else encountered this problem with Boot Manager ? Is there a fix to this ?
I successfully install Fedora 11. The /boot partition, setup to use GRUB, is in an extended partition on my first hard drive. The partition is labelled for easy identifying with Boot Manager.
When I reboot and the Boot Manager screen appears, it successfully shows me a boot manager item at the labelled boot partition. But instead of saying "GRUB", as two other Linux distributions which I can successfully boot from Boot Manager do, it says "Linux" instead. It strongly looks like it thinks this is a LILO boot rather than GRUB. When I try booting this partition, no GRUB screen appears, the first line says "This is an ancient...." something ( the screen scrolls too fast and the keyboard can not control it ), and the boot fails.
It looks like Boot Manager thinks this is LILO rather than GRUB and boots it incorrectly. Alternatively the installation may have been flawed but no one else has encountered this from the Fedora 11 installation that I can see.
Has anyone else encountered this problem with Boot Manager ? Is there a fix to this ?