You are not logged in.
I want to make systemd-boot loader.conf use img from /boot, not those from /boot/efi, which are copied from /boot by myself. If I don't do this, I won't boot the system.
I thought this would be easy, but I didn't find any infomation from google and chatgpt, I know nothing about loader.conf or UEFI boot.
Last edited by lionclaw (2024-12-07 11:19:26)
Offline
didn't find any infomation from google and chatgpt
https://wiki.archlinux.org/title/Systemd-boot
tl;dr just mount the esp into /boot ?
plz use /boot img, this will be helpful.
Most certainly not.
Please remove the oversized images, the board has a 250x250 px max rule and while you'd typically be asked to replace them w/ links: don't post pictures of text, post the text.
https://wiki.archlinux.org/title/Genera … s_and_code
Online
The simplest way to use systemd-boot is to have the EFI system partition mounted under /boot/.
To change your system to that configuration follow these steps:
mv /boot/{,efi/}amd-ucode.img
umount /boot/efi
rm -r /boot/*
mount /dev/nvme0n1p1 /boot
sed -i 's|/boot/efi|/boot|' /etc/fstabEDIT: and you should also configure systemd-boot to load the µcode: https://wiki.archlinux.org/title/Microcode#systemd-boot
Last edited by Head_on_a_Stick (2024-12-07 10:05:54)
Jin, Jîyan, Azadî
Offline
sorry for that, I will read the rule and edit the post.
Offline
I do as you say, mount boot as esp. But I wonder if I can make esp not include any initrd.img or vmlinuz files. This will make system more sustainable, or smaller esp partition? Since esp is mounted after root, this should be able.
Offline
if I can make esp not include any initrd.img or vmlinuz files
Jin, Jîyan, Azadî
Offline
Oh, I should read the wiki more carefully. And I can tolerate this situation, since managing another partition will be a problem for me. Thanks.
Offline