On Sun, Oct 30, 2016 at 09:25:06PM -0400, jacob wrote:
>
> 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.
>
The LFS grub is probably incorrectly built for UEFI. But unless you
chainload, only one bootloader (i.e. Arch's grub, unless you
overwrite it) is likely to be used. Hmm, I suppose that might not
be true for UEFI - but first you need to get both your LFS kernel
and the stanza in Arch's grub.cfg to work.
Only after that should you think about installing grub from LFS.
> 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
I note you don't care about the recent Dirty COW vulnerability. But
since it doesn't boot, that kernel version is the least of your problems.
But when it does boot, safest to upgrade to any stable kernel
released after 20th October - my notes say 4.7.9, 4.8.3, 4.4.26 or
later - but for other people, some old stable kernels were also
fixed.
> root=UUID=d6788259-f948-4164-ae29-d1b996ffd6d9 rootfstype=ext4 ro
> }
>
Is the UUID correct for the LFS partition ?
> 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.
Does the Arch grub give you a graphical screen ? If so, try adding
'nomodeset' to the grub command line.
I also found an old (ubuntu) report that UEFI does not support
booting in text mode. Dunno, I've got enough trouble with BIOS
hardware.
ĸen
--
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
--
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
