On 2016-10-30 20:33, Ken Moffat wrote:
On Sun, Oct 30, 2016 at 06:55:56PM -0400, jacob wrote:
I've changed grub-install to add the --modules flag, so it's now ran
as
grub-install --target=x86_64-efi --efi-directory=/boot/efi
--bootloader-id=LFS --modules=part_gpt --recheck --debug
Here is my grub.cfg, although it attempted to boot into blind mode
without
loading efi_gop and efi_uga. I believe the grub configuration is
irrelevant
because I can chainload off my arch linux install, and still come to
the
same issue.
I might be *wildly* mistaken here (I don't use UEFI, and I recall
loads of problems for people trying to use it), but doesn't
chainload cause (Arch's) grub to transfer to another bootloader ?
If so, I guess that second bootloader is the LFS grub, and therefore
the way it was compiled, and its config file, are still relevant ?
I also remember that distros such as Fedora do not support chainload
because it might not work (and I think the notworking examples in
their bug that caused that were UEFI).
ĸen
--
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
Not exactly, a bootloader won't load another bootloader.
Grub on either LFS or Arch, or any linux distro will always execute the
linux kernel with generated configurations.
Thanks, Jacob.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
