| View previous topic :: View next topic |
| Author |
Message |
0ven
n00b
Joined: 26 May 2024
Posts: 4
|
 Posted: Sun May 26, 2024 4:42 am Post subject: Stuck with bootctl [SOLVED] |
 |
|
Install was going smoothly until I started trying to setup the boot loader I am using btrfs and systemd-boot with secure boot. bootctl --esp-path=/boot install outputs
| Code: |
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi.signed" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi.signed" to "/boot/EFI/BOOT/BOOTX64.EFI".
Random seed file /boot/loader/random-seed successfully refreshed (32 bytes).
Created EFI boot entry "Linux Boot Manager".
|
but then bootctl list outputs
| Code: |
No boot loader entries found.
|
when I reboot I just get the reboot to bios option which makes sense because when I looked in /boot/loader/entries it has nothing in it. I think this might have something to do with btrfs because I had the same problem on arch like a week ago which got me to finally try Gentoo again. Anyhow currently my thought is that I should manually add an entry to /boot/loader/entries or solve the issue if I have just missed something obvious. Its about midnight now so I am going to go to bed and check this tomorrow.
also probably worth noting I tried a bunch of different esp locations because of other problems I was running into so thats why esp is set to boot
_________________
One must imagine Sisyphus happy.
Last edited by 0ven on Sun May 26, 2024 4:51 pm; edited 1 time in total |
|
| Back to top |
|
 |
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2424
|
| Posted: Sun May 26, 2024 5:01 am Post subject: |
|
|
Did you mount the ESP?
Best Regards,
Georgi |
|
| Back to top |
|
|
Nowa
Developer
Joined: 25 Jun 2014
Posts: 429
Location: Nijmegen
|
| Posted: Sun May 26, 2024 12:40 pm Post subject: |
|
|
Please show us the contents of /boot and your ESP. As well as the output of:
| Code: | | emerge -pv sys-kernel/installkernel |
_________________
OS: Gentoo 6.10.12-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
0ven
n00b
Joined: 26 May 2024
Posts: 4
|
| Posted: Sun May 26, 2024 4:20 pm Post subject: |
|
|
| logrusx wrote: | | Did you mount the ESP? |
Yes If you don't mount the esp bootctl will throw an error
| AndrewAmmerlaan wrote: | Please show us the contents of /boot and your ESP. As well as the output of:
| Code: | | emerge -pv sys-kernel/installkernel |
|
Sure
| Code: |
(chroot) mint / # tree /boot/
/boot/
├── EFI
│ ├── BOOT
│ │ ├── BOOTX64.EFI
│ │ ├── grubx64.efi
│ │ └── mmx64.efi
│ ├── Linux
│ └── systemd
│ └── systemd-bootx64.efi
├── System.map-6.8.10-gentoo-dist
├── System.map-6.8.10-gentoo-dist.old
├── config-6.8.10-gentoo-dist
├── config-6.8.10-gentoo-dist.old
├── initramfs-6.8.10-gentoo-dist.img
├── initramfs-6.8.10-gentoo-dist.img.old
├── loader
│ ├── entries
│ ├── entries.srel
│ ├── loader.conf
│ └── random-seed
├── vmlinuz-6.8.10-gentoo-dist
└── vmlinuz-6.8.10-gentoo-dist.old
|
| Code: |
emerge -pv sys-kernel/installkernel
(chroot) mint / # emerge -pv sys-kernel/installkernel
These are the packages that would be merged, in order:
Calculating dependencies -
!!! Problem resolving dependencies for sys-kernel/installkernel
... done!
Dependency resolution took 0.38 s (backtrack: 0/20).
!!! The ebuild selected to satisfy "sys-kernel/installkernel" has unmet requirements.
- sys-kernel/installkernel-38::gentoo USE="dracut systemd-boot -efistub -grub -refind -systemd -uki -ukify" ABI_X86="(64)"
The following REQUIRED_USE flag constraints are unsatisfied:
systemd-boot? ( systemd )
The above constraints are a subset of the following complete expression:
systemd-boot? ( systemd ) ukify? ( uki ) at-most-one-of ( efistub grub refind systemd-boot )
* IMPORTANT: 22 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
|
noticed this was threw errors so I doubled back and did the installkernel steps in the handbook (I think I forgot about it)
Now tree shows
| Code: |
(chroot) mint / # tree /boot/
/boot/
├── EFI
│ ├── BOOT
│ │ ├── BOOTX64.EFI
│ │ ├── grubx64.efi
│ │ └── mmx64.efi
│ ├── Linux
│ └── systemd
│ └── systemd-bootx64.efi
├── System.map-6.8.10-gentoo-dist
├── System.map-6.8.10-gentoo-dist.old
├── config-6.8.10-gentoo-dist
├── config-6.8.10-gentoo-dist.old
├── initramfs-6.8.10-gentoo-dist.img
├── initramfs-6.8.10-gentoo-dist.img.old
├── loader
│ ├── entries
│ ├── entries.srel
│ ├── loader.conf
│ └── random-seed
├── vmlinuz-6.8.10-gentoo-dist
└── vmlinuz-6.8.10-gentoo-dist.old
|
unfortunately when I run bootctl install I still get no entries with bootctl list and nothing in the entries folder
_________________
One must imagine Sisyphus happy. |
|
| Back to top |
|
|
Nowa
Developer
Joined: 25 Jun 2014
Posts: 429
Location: Nijmegen
|
| Posted: Sun May 26, 2024 4:36 pm Post subject: |
|
|
The kernels are installed in the layout that grub understands, but you are using systemd-boot. The solution is to install sys-kernel/installkernel with the "systemd-boot" flag enabled.
The output of emerge -pv sys-kernel/installkernel shows us that you have enabled this flag, but not enabled the "systemd" flag, which is a requirement for systemd-boot.
To solve your problem:
- enable both the "systemd" and "systemd-boot" flags for sys-kernel/installkernel
- re-install sys-kernel/installkernel with the new configuration
- re-install the kernel: emerge --config sys-kernel/gentoo-kernel or emerge --config sys-kernel/gentoo-kernel-bin
- Optionally cleanup old kernel files in /boot
To improve the handbook, can you tell me exactly which steps you were following that caused you to end up in this state? Clearly some instruction is missing somewhere.
_________________
OS: Gentoo 6.10.12-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
0ven
n00b
Joined: 26 May 2024
Posts: 4
|
| Posted: Sun May 26, 2024 4:50 pm Post subject: |
|
|
| AndrewAmmerlaan wrote: | The kernels are installed in the layout that grub understands, but you are using systemd-boot. The solution is to install sys-kernel/installkernel with the "systemd-boot" flag enabled.
The output of emerge -pv sys-kernel/installkernel shows us that you have enabled this flag, but not enabled the "systemd" flag, which is a requirement for systemd-boot.
To solve your problem:
- enable both the "systemd" and "systemd-boot" flags for sys-kernel/installkernel
- re-install sys-kernel/installkernel with the new configuration
- re-install the kernel: emerge --config sys-kernel/gentoo-kernel or emerge --config sys-kernel/gentoo-kernel-bin
- Optionally cleanup old kernel files in /boot
To improve the handbook, can you tell me exactly which steps you were following that caused you to end up in this state? Clearly some instruction is missing somewhere. |
this worked thanks a bunch. In terms of the handbook I looked through it and it seems to be a mistake on my behalf because I switched to using systemd boot instead of grub after I did the kernel steps and when you get to the section for bootloader the only flag it tells you to give is systemd-boot. Not really sure if thats an issue with the handbook though as the section for the kernel would have worked just fine I just missed it because I was sleepy. Anyhow I will mark this as solved now have a good one 
_________________
One must imagine Sisyphus happy. |
|
| Back to top |
|
|
Nowa
Developer
Joined: 25 Jun 2014
Posts: 429
Location: Nijmegen
|
| Posted: Sun May 26, 2024 6:21 pm Post subject: |
|
|
| 0ven wrote: | | this worked thanks a bunch. In terms of the handbook I looked through it and it seems to be a mistake on my behalf because I switched to using systemd boot instead of grub after I did the kernel steps and when you get to the section for bootloader the only flag it tells you to give is systemd-boot. Not really sure if thats an issue with the handbook though as the section for the kernel would have worked just fine I just missed it because I was sleepy. Anyhow I will mark this as solved now have a good one |
Awesome great to hear that it works now.
I have slightly changed the bootloader page of the handbook to mention that we need the "systemd" as well as the "systemd-boot" flags.
_________________
OS: Gentoo 6.10.12-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
|
Installing Gentoo
