View previous topic :: View next topic |
Author |
Message |
FastTurtle Guru
Joined: 03 Sep 2002 Posts: 499 Location: Flakey Shake & Bake Caliornia, USA
|
Posted: Sat Nov 02, 2024 5:21 pm Post subject: Using Lilo with GPT and PartUUID |
|
|
Just found this on a Slackware Thread about how to get Lilo to work with a PARTUUID
Code: | append = " root=PARTUUID=00f34709-02" |
It's that simply but does require the lates Lilo V: 24.2
I'll be testing this by Year End (Christmas gift to myself) on a SuperMicro H12SSL based motherboard with an Epyc. Problem is that according to the Manual it's either Legacy (default) or EFI and my LSI 9300-16i is only visable in Legacy Mode if I want to boot and I can use GPT mode and now simply test the append and use the root=PARTUUID=xxxxxx-xxx as desired for the boot disk. It even gives me the option of multi booting the system using the partuuid of what ever I plan on testing while keeping all of my data safe on other drives. _________________ AsRock B550 Phantom Gaming 4
128GB 3200 Mhz memory
1TB NVME as the boot disk
4x 4TB Sata - 2x 2TB Sata SSD - 4x 450GB SaS - 3x 900GB SaS - 72GB SaS for Gentoo system disk
LSI 9300-16i in HBA mode for all spinning disks
Radeon 6800 (Non XT) for GPU |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Tue Nov 05, 2024 3:53 am Post subject: |
|
|
TBH I'm not sure why one would want to use lilo or elilo on an uefi system. Former doesn't support EFI, latter hasn't had patches in almost a decade.
To use lilo on a modern machine, the firmware must have CSM or MBR BIOS compatibility mode. EFI will have nothing of legacy boot sectors.
This is not to say you can't install lilo on a GPT disk, but the firmware of the computer still needs to do legacy boot.
TBH either use grub or refind, or don't use a bootloader at all - the point of lilo is that MBR firmware does not understand filesystems and lilo bridged that gap. EFI however does understand one filesystem (ESP/FAT) and can load boot file images directly. Using EFI is much safer as you won't risk writing sectors in funny places (which is what lilo does in order to be able to boot) so less chance of corruption, not to mention you can't move files around without upsetting lilo.
There's the other problem of EFI firmware on expansion cards knowing that it needs to also do legacy boot, which may not exist...
I ditched lilo a long long time ago as grub brought boot features of OpenFirmware to PCs though without the safety of unmodifible firmware. With UEFI I also question the need of grub, alas having a consistent boot interface among all my PCs is helpful... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Chiitoo Administrator
Joined: 28 Feb 2010 Posts: 2730 Location: Here and Away Again
|
Posted: Tue Nov 05, 2024 8:00 am Post subject: |
|
|
When grub "legacy" was going away, and after having tried grub-2... I tried LILO and I like that it is simple and works.
Some years ago I did try the EFI way too... when I last moved my trusty install to another drive, and didn't get it to work on the first try, so I went back to the way I know works (with GPT included).
So far have not seen an advantage for me with the other methods, though I'm likely to be ignorant to them, but for the time being I'll probably be sticking with LILO at least for some more time to come. _________________ Kindest of regardses. |
|
Back to top |
|
|
ian.au l33t
Joined: 07 Apr 2011 Posts: 606 Location: Australia
|
Posted: Wed Nov 06, 2024 9:30 pm Post subject: |
|
|
I guess the only reason to use a bootloader is if you need dualboot or multiboot capability. I don't need this capability generally, so I don't bother with one at all for EFI.
I use an EFI stub, and manually copy the new bzImage into /boot/EFI/Gentoo/bzImage.efi
This way I don't have to bother with rEFInd each time I build a kernel, set it once to bzImage and it will boot that file once copied into place.
I rename the outgoing kernel as a backup bzImage-X.X.XX.bak before I copy the new one over, just in case I cook a lemon and have to revert. I had to use it just once since 2020 (by neglecting to copy the correct .config over) so best to keep a boot stick handy JIC.
Code: |
/boot
├── amd-uc.img
├── EFI
│ ├── early_ucode.cpio
│ └── Gentoo
│ ├── bzImage-6.6.47.bak
│ └── bzImage.efi
├── intel-uc.img
└── tools
|
|
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Fri Nov 08, 2024 4:01 am Post subject: |
|
|
Also preboot config/recovery. Having grub to tell init to start in single user mode is sometimes helpful, having a static boot environment makes that kind of tough. This sort of is the reason why I went against efistub/direct efi boot. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
ian.au l33t
Joined: 07 Apr 2011 Posts: 606 Location: Australia
|
Posted: Fri Nov 08, 2024 5:34 am Post subject: |
|
|
I'm pretty sure that's possible, but I'm not hosting anything that requires me to boot into single user mode these days, so I haven't bothered.
It requires setting up a separate appropriately configured entry with efibootmgr and you can reach the menu by hitting 'e' during boot IIRC
I should also say that I could and should easily mv bzImage.efi to backup.efi instead of making a backup as above. Then with an additional entry in the boot menu with efibootmgr - that would be fine as a fallback.
It's on my to do list, but with a fair chunk of tasks in front of it... it would have happened by now if I'd had to chroot in a few times over the past few years. When I set this up I was pretty frgile on the whole thing, as my previous PC had a horribly broken uefi implementation - so I made this one as manual and simple as possible so I at least understood it. |
|
Back to top |
|
|
|