| 1 |
On Wednesday, 26 May 2021 14:49:01 BST Michael wrote: |
| 2 |
> On Tuesday, 25 May 2021 16:23:01 BST Peter Humphrey wrote: |
| 3 |
> > Thanks for the offer, Michael, but let me clear a few things up first. |
| 4 |
> > |
| 5 |
> > 1. I don't use symlinks in /boot. |
| 6 |
> |
| 7 |
> This allows a simpler single boot partition (ESP) & filesystem set up |
| 8 |
> (VFAT). |
| 9 |
|
| 10 |
How do symlinks work on a FAT32 partition? |
| 11 |
|
| 12 |
--->8 |
| 13 |
|
| 14 |
> I notice you have /dev/nvme1n1p1 named as "boot". Is this a secondary boot |
| 15 |
> partition? What is its mountpoint? What does it contain? |
| 16 |
|
| 17 |
It's a hangover from my attempts earlier. I'll remove it soon. |
| 18 |
|
| 19 |
--->8 |
| 20 |
|
| 21 |
> > I followed the installation handbook, boot-loader section, to create a |
| 22 |
> > UEFI |
| 23 |
> > boot entry. I followed the syntax precisely, with several variations at |
| 24 |
> > various attempts. In every case, the UEFI BIOS listed the new entry but |
| 25 |
> > couldn't execute it. |
| 26 |
> |
| 27 |
> This should work to launch your systemd-boot: |
| 28 |
> |
| 29 |
> efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "systemd-boot" -- |
| 30 |
> loader "\EFI\Boot\bootx64.efi" |
| 31 |
|
| 32 |
It didn't, but ... |
| 33 |
|
| 34 |
> This would also work, if vmlinuz-5.10.27-gentoo, config-5.10.27-gentoo, and |
| 35 |
> System.map-5.10.27-gentoo are stored on the ESP under the EFI/ directory, |
| 36 |
> e.g. in EFI/Linux/, to launch your current kernel directly: |
| 37 |
|
| 38 |
That's the point I was missing - where those three files live. I had them at |
| 39 |
the root of the FS, as implied by the installation wiki. |
| 40 |
|
| 41 |
> efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Gentoo-5.10.27" -- |
| 42 |
> loader "\EFI\Linux\vmlinuz-5.10.27-gentoo" |
| 43 |
|
| 44 |
--->8 |
| 45 |
|
| 46 |
> 2. Use some other better suited 3rd party boot manager (not systemd-boot). |
| 47 |
> The principle is broadly the same as your present setup. Each boot manager |
| 48 |
> has its own idiosyncrasies and commands of choice. GRUB is quite automated, |
| 49 |
> although you can overwrite its grub.conf menu and decline using |
| 50 |
> update-grub, or grub-mkconfig to generate it. Then again, why would you |
| 51 |
> select such a heavily automated and complicated piece of software, only to |
| 52 |
> bypass the very functionality its devs wanted to offer? Contrastingly, |
| 53 |
> syslinux is very simple and lightweight, but you have to manually configure |
| 54 |
> its also very simple boot menu. |
| 55 |
|
| 56 |
I don't want to start on about grub. I washed my hands of it a few years ago, |
| 57 |
after struggling to set it up to offer a choice including a kernel with three |
| 58 |
run-level options: default, no X and no network. |
| 59 |
|
| 60 |
> PS. The UEFI firmware will scan more than a single VFAT partition marked as |
| 61 |
> ESP type, but as far as I know this will only work if the ESP is on the |
| 62 |
> first disk - I haven't tried it. |
| 63 |
|
| 64 |
That may be Wol's answer. |
| 65 |
|
| 66 |
Thanks again for all the work you've put into this, Michael. |
| 67 |
|
| 68 |
-- |
| 69 |
Regards, |
| 70 |
Peter. |
Archives