You are not logged in.
Fixing Unbootable GRUB on UEFI Systems – Arch Linux
Tutorial: Ensuring Arch Linux Boots on Problematic UEFI Firmware (Samsung)
This guide is for UEFI systems with buggy firmware (such as certain Samsung laptops) that do not properly detect custom boot entries created by Arch Linux.
? Symptom
Even with GRUB correctly installed (and entries visible with efibootmgr), the system either doesn’t list Arch Linux as a boot option or fails to start it.
✅ Solution
Use the UEFI fallback path, which all UEFI firmwares are required to recognize:
EFI/BOOT/BOOTX64.EFI
? Final Installation Steps (After Installing GRUB)
Install GRUB as usual:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch
Generate the GRUB config:
grub-mkconfig -o /boot/grub/grub.cfg
Create the fallback folder and copy the GRUB EFI binary:
mkdir -p /boot/efi/EFI/BOOT
cp /boot/efi/EFI/arch/grubx64.efi /boot/efi/EFI/BOOT/BOOTX64.EFI
Check with efibootmgr:
efibootmgr -v
? Result
Your laptop should now boot Arch Linux normally via UEFI, even if the firmware ignores custom boot entries.
? Optional: Automate with a Script
Create a script named fixuefiboot.sh:
#!/bin/bash
set -e
mkdir -p /boot/efi/EFI/BOOT
cp /boot/efi/EFI/arch/grubx64.efi /boot/efi/EFI/BOOT/BOOTX64.EFI
echo "EFI fallback successfully configured."
Make it executable:
chmod +x fixuefiboot.sh
Run it after installing GRUB.
Offline
first: please use code tags
second: https://man.archlinux.org/man/grub-inst … #removable -> installs grub in the "fallback" path
third: read uefi spec -> it's not a "fallback" at all but designated path explicitly for removable media so uefi boot media can start without require a proper boot entry
fourth: this is an issue with many mobile latforms in general and by no means specific to any specific vendor
fith: please use search function as this "solution" can be found all over the bbs
Last edited by cryptearth (Yesterday 21:53:40)
Offline