On Tue, Jan 08, 2013 at 02:03:31PM -0700, Chris Murphy wrote:
>
> On Jan 8, 2013, at 12:45 PM, Chris Murphy <li...@colorremedies.com> wrote:
>
> >
> > On Jan 8, 2013, at 12:34 PM, Matthew Garrett <mj...@srcf.ucam.org> wrote:
> >
> >> On Tue, Jan 08, 2013 at 12:16:52PM -0700, Chris Murphy wrote:
> >>
> >>> cp /boot/efi/EFI/fedora/grubx64.efi
> >>> /boot/efi/EFI/System/Library/CoreServices/boot.efi
> >>> grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> >>
> >> Make sure that the config is using linuxefi and initrdefi, not linux and
> >> initrd.
> >
> > It does, but contrary to what I said earlier, I think I made a mistake
> > moving the grub2-install created grubx64.efi file, because that one now
> > clearly works. Whereas the one the grub2-efi package puts in
> > /boot/efi/EFI/fedora doesn't work.
>
> OK so it appears to be a conflict between kernel 3.6.11-1 and GRUB 2.00 that
> I'm not clearly understanding, because adding to the confusion I just
> realized that one of the grub2's (mine or the prebaked one) was actually
> using a residual fedup vmlinuz-fedup kernel, which is actually kernel 3.6.6.
> So it seems at least there's a regression in nouveau occurring between
> grub2-efi and kernel 3.6.11, but not with 3.6.6.
>
> grub-efi (legacy) can boot either kernel fine.
This most likely has nothing to do with grub2 at all.
--
Peter
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
