On 12/20/2011 09:35 AM, Don Zickus wrote:
My experience with the upgrading to F16 was the new grub2 was causing the
problems. However, the way the install scripts were written, they update
both grub.conf (grub1) and grub2.cfg (grub2). grub.conf is updated
correctly, it is just the grub2.cfg isn't (in fact it is empty, hence the
warning). Because my system still uses grub1 in the bootloader (not sure
how to force it to use grub2), everything boots fine for me (for now :-/
). So I just ignore the warning.
Does your systemp use UEFI to boot? At one point grub2 was not able to
correctly handle EFI and grub1 was used - I am not sure of the current
grub2 state of affairs with regard to EFI.
That -may- explain why grub1 is still being used ... grub experts will
know more .... :-)
gene