You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Guide: Booting Omarchy on a legacy-BIOS-only laptop (no UEFI) with GRUB
#16713
System details: Sony Vaio SVE15118FNB, Intel i7 (3rd gen, no AVX2), AMD Radeon HD 7650M, legacy BIOS only, Omarchy ISO downloaded 2026-10-23
I installed Omarchy on an older laptop whose firmware has no UEFI mode at all (Sony Vaio SVE15118FNB, InsydeH2O BIOS, 2012). The installer completed fine, but the installed system would not boot. Here's what happened and what got it booting, in case it helps anyone else on legacy-only hardware.
Symptoms
The installer finishes normally ("installed in ~6 min").
With the USB removed, the laptop shows a blinking cursor and then restarts in a loop.
With the USB still in, it keeps booting back into the installer menu (entries labelled (x86_64, BIOS)). "Boot existing OS" just loops back to the same menu.
The firmware has no Boot Mode / UEFI option anywhere, so switching to UEFI isn't possible.
What I tried first
The installer sets up Limine for UEFI. From the live USB I chrooted in and ran limine bios-install /dev/sda, with limine-bios.sys and limine.conf in the root of the boot partition. That got past the blinking cursor, but then I got a blank screen for ~10 seconds followed by a reset. No Limine menu appeared, even with timeout: 10 and textmode: yes.
What worked: GRUB (BIOS) + the stock Arch kernel
I changed two things at once, so I can't say which one was the actual blocker: the bootloader (Limine BIOS → GRUB i386-pc) or the kernel (linux-omarchy → stock linux). The CPU is an older i7 without AVX2, in case that's relevant for the kernel.
Replace sdX with your disk. Mine was sda: sda1 FAT32 boot partition, sda2 LUKS.
Boot the Omarchy USB, choose the install medium, then press Ctrl+C to leave the installer.
Connect to the network (iwctl → station wlan0 scan → station wlan0 connect "SSID").
Unlock and enter the install:
cryptsetup open /dev/sdX2 root
mount -o subvol=@ /dev/mapper/root /mnt
mount /dev/sdX1 /mnt/boot
arch-chroot /mnt
Install GRUB for BIOS and the stock kernel:
pacman -Sy grub linux
grub-install --target=i386-pc /dev/sdX
The kernel lands in /boot/<machine-id>/linux/. Copy it to simple names:
Write /boot/grub/grub.cfg. Get the FS UUID with blkid /dev/sdX1 and the PARTUUID with blkid /dev/sdX2. The kernel options match what's in Omarchy's limine.conf:
exit, reboot, remove the USB. The GRUB menu shows, then the LUKS prompt, then Hyprland.
Keep the copies updated. Kernel updates write to the <machine-id> folder, not to the copies GRUB boots. A pacman hook like this one at /etc/pacman.d/hooks/zz-grub-kernel.hook refreshes them:
[Trigger]
Type = Package
Operation = Install
Operation = Upgrade
Target = linux
Target = mkinitcpio
[Action]
Description = Copying kernel for GRUB
When = PostTransaction
Exec = /bin/sh -c 'cp /boot/*/linux/vmlinuz /boot/vmlinuz-linux && cp /boot/*/linux/initramfs /boot/initramfs-linux.img'
Suggestions for Omarchy
Have the installer detect a BIOS-only boot (no /sys/firmware/efi) and either install a working BIOS bootloader or warn before wiping the disk.
If linux-omarchy targets newer CPUs (x86-64-v3 / AVX2), say so in the requirements. I haven't confirmed that this was the cause here.
Side note
Hyprland ran fine once booted. Later the laptop's Radeon HD 7650M (its only GPU) started failing its ring test on every boot, so the desktop stopped working. That looks like a hardware failure on a 13-year-old GPU and isn't related to the boot issue above.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
System details: Sony Vaio SVE15118FNB, Intel i7 (3rd gen, no AVX2), AMD Radeon HD 7650M, legacy BIOS only, Omarchy ISO downloaded 2026-10-23
I installed Omarchy on an older laptop whose firmware has no UEFI mode at all (Sony Vaio SVE15118FNB, InsydeH2O BIOS, 2012). The installer completed fine, but the installed system would not boot. Here's what happened and what got it booting, in case it helps anyone else on legacy-only hardware.
Symptoms
(x86_64, BIOS)). "Boot existing OS" just loops back to the same menu.What I tried first
The installer sets up Limine for UEFI. From the live USB I chrooted in and ran
limine bios-install /dev/sda, withlimine-bios.sysandlimine.confin the root of the boot partition. That got past the blinking cursor, but then I got a blank screen for ~10 seconds followed by a reset. No Limine menu appeared, even withtimeout: 10andtextmode: yes.What worked: GRUB (BIOS) + the stock Arch kernel
I changed two things at once, so I can't say which one was the actual blocker: the bootloader (Limine BIOS → GRUB i386-pc) or the kernel (
linux-omarchy→ stocklinux). The CPU is an older i7 without AVX2, in case that's relevant for the kernel.Replace
sdXwith your disk. Mine wassda:sda1FAT32 boot partition,sda2LUKS.iwctl→station wlan0 scan→station wlan0 connect "SSID")./boot/<machine-id>/linux/. Copy it to simple names:/boot/grub/grub.cfg. Get the FS UUID withblkid /dev/sdX1and the PARTUUID withblkid /dev/sdX2. The kernel options match what's in Omarchy'slimine.conf:exit,reboot, remove the USB. The GRUB menu shows, then the LUKS prompt, then Hyprland.Keep the copies updated. Kernel updates write to the
<machine-id>folder, not to the copies GRUB boots. A pacman hook like this one at/etc/pacman.d/hooks/zz-grub-kernel.hookrefreshes them:Suggestions for Omarchy
/sys/firmware/efi) and either install a working BIOS bootloader or warn before wiping the disk.linux-omarchytargets newer CPUs (x86-64-v3 / AVX2), say so in the requirements. I haven't confirmed that this was the cause here.Side note
Hyprland ran fine once booted. Later the laptop's Radeon HD 7650M (its only GPU) started failing its ring test on every boot, so the desktop stopped working. That looks like a hardware failure on a 13-year-old GPU and isn't related to the boot issue above.
All reactions