Boot the Omarchy install USB with nomodeset when an NVIDIA machine goes to a black screen
Re-read issue omacom/omarchy#7045 in full today with all eleven comments, plus issue #7061, plus every cited omarchy-iso file on the quattro branch. The issues do support the symptom and the workaround: the opening report is an RTX 5060 Ti whose author states that adding nomodeset to the installer's GRUB parameters lets the installer boot, joaomcarlos confirmed the same on an RTX 4090 after patching the stick with dd, fbal98 confirmed it on an RTX 5060 from the grub> prompt using the exact four commands the record quotes, and Ycaro-Oleg reports the same live-ISO failure and workaround on an RTX 3060 in #7061. Confirmed from source on 2026-09-11: configs/grub/grub.cfg:49-50 still sets timeout=0 and timeout_style=hidden with no nomodeset entry, configs/grub/loopback.cfg matches it, configs/syslinux/archiso_sys.cfg:4 sets TIMEOUT 150, configs/syslinux/archiso_sys-linux.cfg:6 carries the exact menu label the fix tells the user to highlight, configs/airootfs/etc/mkinitcpio.conf.d/archiso.conf:2 puts kms in HOOKS with no autodetect, builder/build-iso.sh:121 adds no NVIDIA driver to the live environment, and configs/profiledef.sh sets install_dir="arch" and arch="x86_64", which is what makes the /arch/boot/x86_64/vmlinuz-linux-t2 paths in the grub> recipe correct. Two things were wrong. The canonical repository name is omacom/omarchy-iso and every source URL in the record used the old omacom-io/omarchy-iso name, which redirects on github.com but is not the current name. And the release enumeration is stale: PR #110 is still open at head c7cbcb4 with base quattro, last updated 2026-09-08 and never merged, while omarchy v4.0.3 was published on 2026-09-08, so the affected-image list has to include it rather than stopping at 4.0.2. I also added a labelled note on omacom/omarchy-iso#160, raised on #7045 on 2026-09-07, which puts modprobe.blacklist=nouveau on both GRUB boot paths and deliberately not on the syslinux one, is still open, and has never been tested by anyone with an affected card. On this machine I confirmed only that an installed Omarchy 4.0.2 NVIDIA system has no nomodeset in /proc/cmdline, which supports the verify step. Nothing about the live ISO boot was exercised: this workstation runs nvidia-open-dkms 610.57.04 on a card none of the reports cover, and booting an install medium is outside what a read-only audit can do.
Symptom
Booting the Omarchy 4 (Quattro) install medium on a machine with an NVIDIA card shows a black screen and never reaches the installer. Reported on an RTX 5060 Ti, an RTX 5060 and an RTX 4090 in this thread, and on an RTX 3060 in #7061. One reporter saw the screen stay black for about 20 seconds, the keyboard backlight go out, and the monitor start its sleep countdown. On UEFI no boot menu is shown at all, so there is nowhere obvious to type a kernel parameter.
Cause
The workaround is confirmed by three reporters on three cards in #7045, an RTX 5060 Ti, an RTX 4090 and an RTX 5060, and by a fourth reporter on an RTX 3060 in #7061. The mechanism is the collaborator's reading of the omarchy-iso sources, not a reproduction, since nobody triaging had an NVIDIA card. configs/airootfs/etc/mkinitcpio.conf.d/archiso.conf puts kms in HOOKS with no autodetect, so every in-tree DRM driver is built into the live initramfs and modesets during the live boot. builder/build-iso.sh adds no NVIDIA driver to the live environment, so nouveau is the NVIDIA display driver in play. The default boot entry carries quiet splash, so when that takeover fails nothing is left on screen. Exactly what nouveau gets wrong on these cards is not established. The missing UEFI menu is configuration, not a symptom: configs/grub/grub.cfg in omacom/omarchy-iso sets timeout=0 and timeout_style=hidden at lines 49 and 50, and configs/grub/loopback.cfg does the same for the Ventoy and loopback path, so GRUB boots the default entry on every UEFI machine without drawing anything (re-read on quattro on 2026-09-11). Legacy BIOS boots show a syslinux menu for 15 seconds (TIMEOUT 150 in configs/syslinux/archiso_sys.cfg). nomodeset is needed on the live medium only. The installed system boots normally without it afterwards, confirmed on the 4090.
Fix
Add nomodeset to the live medium's kernel command line for that one boot.
**Legacy BIOS boot.** The syslinux menu is visible for 15 seconds. Highlight Omarchy install medium (x86_64, BIOS), press Tab, append nomodeset to the end of the line, press Enter.
**UEFI boot, if you can raise the hidden GRUB menu.** Hold Shift from the moment the firmware hands off. This is a GRUB side effect that depends on the firmware reporting modifier state, so it may do nothing. If a menu appears, highlight Omarchy, press e, find the line beginning linux, append nomodeset, and press Ctrl-X.
**UEFI boot, no menu at all.** Get to the grub> prompt (one reporter reached it with Shift+Esc during boot, on one machine) and boot the live kernel by hand. The paths and arguments are the shipped default entry with archisosearchuuid= swapped for archisosearchfilename=, because the UUID is not known at a bare prompt:
search --file --set=root /arch/boot/x86_64/vmlinuz-linux-t2
linux /arch/boot/x86_64/vmlinuz-linux-t2 archisobasedir=arch archisosearchfilename=/arch/boot/x86_64/vmlinuz-linux-t2 quiet splash xe.enable_panel_replay=0 initramfs_async=0 nomodeset
initrd /arch/boot/x86_64/initramfs-linux-t2.img
boot
If the screen still goes black, drop quiet splash from that linux line so the last kernel message stays visible.
The installer then runs as normal, and the installed system does not need nomodeset.
**Status of the real fix, re-checked on 2026-09-11.** The proposed fix is an Omarchy with safe graphics menu entry carrying nomodeset plus a three second visible menu, omacom/omarchy-iso#110. It is still open and has never merged, head c7cbcb4, base quattro, last updated 2026-09-08. quattro still sets timeout=0 and timeout_style=hidden at configs/grub/grub.cfg:49-50 and carries no nomodeset entry anywhere, and both the nightly and the released image build from quattro, so every image published up to and including the omarchy v4.0.3 release of 2026-09-08 still black-screens with no safe entry and no visible UEFI menu.
A second and different proposal, omacom/omarchy-iso#160, puts modprobe.blacklist=nouveau on both GRUB boot paths (configs/grub/grub.cfg and configs/grub/loopback.cfg, deliberately not on the syslinux BIOS path). That would rescue the boot with nothing for the user to select and without stopping Intel or AMD modesetting. It is also open and unmerged, it was raised for an unrelated reason, and nobody with an affected card has tested it, so treat it as an idea rather than a workaround.
Verify
The Omarchy logo and the installer's configurator appear instead of a black screen. After the install, reboot without the USB stick: the installed system starts its graphical session with no nomodeset anywhere (cat /proc/cmdline shows the Omarchy defaults only).
Sources
- https://github.com/omacom/omarchy/issues/7045
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/grub/grub.cfg
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/syslinux/archiso_sys-linux.cfg
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/syslinux/archiso_sys.cfg
- https://github.com/omacom/omarchy-iso/pull/110
- https://github.com/omacom/omarchy/issues/7061
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/grub/loopback.cfg
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/airootfs/etc/mkinitcpio.conf.d/archiso.conf
- https://github.com/omacom/omarchy-iso/blob/quattro/builder/build-iso.sh
- https://github.com/omacom/omarchy-iso/blob/quattro/configs/profiledef.sh
- https://github.com/omacom/omarchy-iso/pull/160
- https://github.com/omacom/omarchy/releases/tag/v4.0.3