On 2016-10-30 21:01, Ken Moffat wrote:
On Sun, Oct 30, 2016 at 08:43:54PM -0400, jacob wrote:
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.
Chainloading (in grub) is targetted at systems which do not support
multiboot. But I *have* used it (with problems caused by Fedora
attempting to prevent it) to load a Fedora grub (installed *after*
LFS, on the filesystem where I had put Fedora) from an LFS system -
after I used a rescue disk to reinstall the LFS grub. But that was
all a bios build of grub in LFS, not an EFI build.
So, you say you chainloaded and therefore I think Arch's grub is
looking for a bootloader on the filesystem you pointed it to. And
equally, you must have installed the LFS grub on the LFS filesystem
(if it was in the common place, you would not be using the Arch
grub).
On a BIOS system, the existing grub just needs to know where the
kernel for LFS is, and to have the correct root=. For EFI, I
imagine it would be similar, without using the chainload verb.
ĸen
--
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
I am using chainloading probably incorrectly here, sorry, I shall
explain a few things regarding my setup. I'm essentially attempting to
boot LFS through UEFI in 2 different ways - Through the LFS install with
LFS's grub, and through Arch grub. Unrelated to the issue, UEFI indeed
works on grub2, because I have an entry on my UEFI for arch linux that
successfully boots arch. UEFI booting also works on the arch iso from a
USB drive. However, I can't say UEFI works on LFS personally as of yet.
Referring to arch grub, I'm specifically pointing out the generated
entry for LFS to boot its kernel on it:
menuentry 'Linux From Scratch (7.10-systemd) (on /dev/sdc2)' --class
linuxfromscratch --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-simple-d6788259-f948-4164-ae29-d1b996ffd6d9' {
insmod part_gpt
insmod ext2
set root='hd2,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2
--hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2
d6788259-f948-4164-ae29-d1b996ffd6d9
else
search --no-floppy --fs-uuid --set=root
d6788259-f948-4164-ae29-d1b996ffd6d9
fi
linux /boot/vmlinuz-4.7.2-lfs-7.10-systemd
root=UUID=d6788259-f948-4164-ae29-d1b996ffd6d9 rootfstype=ext4 ro
}
Either way when booting from both entry's regardless of which grub it
fails to boot. linux /boot/vmlinuz-4.7.2-lfs-7.10-systemd
root=UUID=d6788259-f948-4164-ae29-d1b996ffd6d9 rootfstype=ext4 ro is the
exact same on the LFS grub entry even, with my latest slight
modifications for testing and revisioning.
--
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
