1 line
1.7 KiB
Plaintext
1 line
1.7 KiB
Plaintext
<!-- SC_OFF --><div class="md"><p>On my new UEFI only laptop, I used archinstall to get plasma installed using grub. It was my first bare metal UEFI only install. It worked the first time, and I'm happy with it. </p> <p>After doing a practice install "from existing Arch", to a USB, and rebooted, I found my internal Plasma install came up with a UEFI boot screen saying No Boot Device. </p> <p>I fixed it by doing this: <code>grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=GRUB</code> but this seems wrong. </p> <p>Instead of using grub-install, wouldn't the better solution be efibootmgr? What was the efibootmgr code that grub-install ran inside archinstall? Or, how would I fix this without access to Arch media? </p> <p>I've looked over <a href="https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#efibootmgr">https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#efibootmgr</a> but could not get efibootmgr to set up a new boot device: <code>efibootmgr -create --disk /dev/nvme0n1 --part 1 --loader /boot/EFI --label "new arch" --verbose</code> Error was something like "invalid or bad number eta" or similar. Sorry. </p> <p>My system:</p> <p>/dev/nvme0n1p1 - esp F32 format. /dev/nvme01np2 - root filesystem. ext4 format</p> <p>I mount esp to /boot</p> <p>Any ideas appreciated.</p> <p>Tks</p> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/archover"> /u/archover </a> <br/> <span><a href="https://www.reddit.com/r/archlinux/comments/qyhyhc/problem_booting_grub_on_uefi_system/">[link]</a></span>   <span><a href="https://www.reddit.com/r/archlinux/comments/qyhyhc/problem_booting_grub_on_uefi_system/">[comments]</a></span> |