From tclug1 at whitleymott.net Fri May 14 11:17:19 2021 From: tclug1 at whitleymott.net (gregrwm) Date: Fri, 14 May 2021 11:17:19 -0500 Subject: [tclug-list] disable rhel grub fallback? Message-ID: the centos8 grub setup is bugging me, i'm trying to add a working entry to boot the pfsense iso from disk on a rhel8 install, and when testing my menuentry, whenever it fails, within a few short seconds grub quickly boots into linux again. how do i disable that? i want it to just sit there and leave the error message showing until i'm ready. and if anyone has a working entry for booting the pfsense iso that would be nice too -------------- next part -------------- An HTML attachment was scrubbed... URL: From iznogoud at nobelware.com Wed May 19 13:13:41 2021 From: iznogoud at nobelware.com (Iznogoud) Date: Wed, 19 May 2021 18:13:41 +0000 Subject: [tclug-list] disable rhel grub fallback? In-Reply-To: References: Message-ID: <20210519181341.GA27295@nobelware.com> > > and if anyone has a working entry for booting the pfsense iso that would be > nice too Have you got anywhere with this? Generally GRUB (1 and 2) want one of two styles of booting, pointing to a kernel and root filesystem and maybe an initial ramdisk, or the Windows style chainloader. You likely want the second. You just have to take a generic (GRUB1) entry that points to a kernel, sends kernel parameters to it, points to ramdisk. You are done. I would like to see other solutions. From tclug1 at whitleymott.net Wed May 19 17:05:23 2021 From: tclug1 at whitleymott.net (gregrwm) Date: Wed, 19 May 2021 17:05:23 -0500 Subject: [tclug-list] disable rhel grub fallback? In-Reply-To: <20210519181341.GA27295@nobelware.com> References: <20210519181341.GA27295@nobelware.com> Message-ID: > > and if anyone has a working entry for booting the pfsense iso that would > be > > nice too > > Have you got anywhere with this? > > Generally GRUB (1 and 2) want one of two styles of booting, pointing to a > kernel and root filesystem and maybe an initial ramdisk, or the Windows > style chainloader. You likely want the second. You just have to take a > generic (GRUB1) entry that points to a kernel, sends kernel parameters to > it, points to ramdisk. You are done. > recent freebsd ISOs no longer work with memdisk. if copied to a thumb drive it boots for either efi or bios. might you clarify how you'd boil down the iso to distill a grub entry that works, preferably also for either efi or bios? -------------- next part -------------- An HTML attachment was scrubbed... URL: From iznogoud at nobelware.com Thu May 20 14:30:38 2021 From: iznogoud at nobelware.com (Iznogoud) Date: Thu, 20 May 2021 19:30:38 +0000 Subject: [tclug-list] disable rhel grub fallback? In-Reply-To: References: <20210519181341.GA27295@nobelware.com> Message-ID: <20210520193038.GA3494@nobelware.com> > > recent freebsd ISOs no longer work with memdisk. if copied to a thumb > drive it boots for either efi or bios. might you clarify how you'd boil > down the iso to distill a grub entry that works, preferably also for either > efi or bios? Yes, this makes sense (needing no ramdisk when booting from a thumb drive). I do not have an ISO handy to look in it myself. Mount it (loopback) to something like /mnt/tmp and go in there and see what it does. You should be able to locate the kernel (in what would be [ROOT_FS]/boot for example). You will find where all the startup scripts are; the "/" where they would live is what your root filessytem will be for the GRUB entry. I am thinking a GRUB1 entry that looks like one of these two: title Slackware64 14.1 gflat root (hd0,0) kernel /vmlinuz-3.10.17_slackwareIN ro root=/dev/sda3 rhgb title Slackware64 14.1 vr root (hd0,0) kernel /vmlinuz-3.10.17_slackwareIN ro root=/dev/sda2 rhgb Points to the very first partition for finding all of its crap, then kicks in that 3.10.17 kernel that I built, and uses /dev/sda2 as the root fs. I love GRUB1. Simple and reliable if you do not need EFi.