OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core high occasional DISPUTE

Get the Omarchy 4.0.3 or 4.0.4 ISO past the logo when it hangs at boot

omarchyomarchy-4installerisolaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Re-read #12773 in full (still open). Hardware, the sh: can't access tty; job control turned off line, the different-stick and direct-port workaround and the Raspberry Pi Imager detail all match. The cause is correctly labelled as the reporters' diagnosis. One fabricated specific remains in the fix: 'USB 2.0 is fine'. No reporter used or mentioned a USB 2.0 stick. They said 'a slower usb drive', and one gave write speeds of 22 MB/s (worked) against 40 MB/s (failed). The corrected fix says that instead. The dd and lsblk steps and the danger are sound. The ISO file name is still unverified and left as a placeholder the reader replaces.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

dd overwrites the whole target device without asking. Pointing it at the wrong device, such as an internal disk, destroys that disk's data. Confirm the device with lsblk before running it.

Symptom

Booting the Omarchy 4.0.3 or 4.0.4 installer USB stops on the Omarchy logo and never reaches the installer. Pressing Esc shows:


sh: can't access tty; job control turned off

and the keyboard does nothing else. The same stick works on other machines, and an Ubuntu stick boots fine on the affected one. Reported on a TUXEDO InfinityBook Pro AMD Gen10, a Lenovo ThinkPad X9 (Core Ultra 7 258V) and a Beelink mini PC.

Cause

The early boot environment cannot find the USB device again when it needs to mount the live image, and drops to an emergency shell behind the splash. Reporters traced it to USB timing: fast USB 3 sticks, hubs and some ports fail, while a slower stick plugged directly into the machine succeeds. Upstream has not identified the exact mechanism, so treat the timing explanation as the reporters' diagnosis.

Fix

Write the ISO to a different, slower USB stick, plug it directly into the machine rather than through a hub or dock, and try another port if it still hangs. One reporter's working stick wrote at about 22 MB/s where a 40 MB/s stick failed. Upstream has not established a speed or USB-generation threshold.

Verify the download first, comparing against the checksum published where you downloaded it:


sha256sum omarchy-*.iso

Identify the stick before writing. Run lsblk with the stick unplugged and again plugged in, and use the device that appeared (a whole disk such as /dev/sdb, never a partition such as /dev/sdb1):


lsblk -o NAME,SIZE,MODEL,TRAN
sudo dd if=omarchy-4.0.4.iso of=/dev/sdX bs=4M status=progress oflag=sync

Replace omarchy-4.0.4.iso with the file you downloaded and /dev/sdX with the stick. On macOS, where balenaEtcher errored for one reporter, Raspberry Pi Imager wrote a working stick.

Verify

The ISO boots past the logo into the Omarchy installer's configurator.

Sources

iso-installer-stuck-on-logo-usb-timing