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

Finish an Omarchy 4.0 install that stops at `Module psmouse not found`

omarchylaptoplenovothinkpadintel
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Checked the mechanism, the merge and the shipped script, and reproduced the failure with a stub modprobe. Confirmed from the GitHub API that #7236 is merged into quattro with merged_at 2026-08-24T13:33:04Z, and that the script at tag v4.0.1 (published 2026-08-25) carries the modprobe -qn psmouse guard. Confirmed on this machine that /usr/share/omarchy/install/hardware/fix-synaptic-touchpad.sh on omarchy 4.0.2-1 has that guard at line 22, and that /usr/bin/omarchy-apply-system exists. Confirmed on this machine that install/hardware/all.sh runs fix-synaptic-touchpad.sh at line 9, nvidia.sh at 11, vulkan.sh at 12 and the intel/ scripts from 14, so the offline-mirror errors cannot occur in an untouched run, which is the evidence for the record's own statement that they are a consequence of resuming by hand. Fetched the v4.0.0 script and ran it under bash -euo pipefail against a stub modprobe that fails: exit 1, and the patched and the upstream-corrected versions both exit 0, so the cause and the workaround both hold. Two things were wrong. The sed command in the fix does not work: with | as the s delimiter the literal || was written \||, so the unescaped pipe ends the replacement and sed exits 1 with unknown option to 's' and leaves the file unpatched. I reproduced that verbatim against the v4.0.0 script and replaced it with a #-delimited command I tested, which produces modprobe psmouse synaptics_intertouch=1 2>/dev/null || true and passes bash -n. The second was provenance: issue 6985 has one further explicit full-disk report (kridaydave) and one user who installed 3.6 instead (rez1-dev) rather than two full-disk reports, and nobody in the thread reported installing from the v4.0.1 ISO. gtech-pedrol only pointed at the release page and kridaydave acknowledged it, so I replaced the "two reporters confirmed" claim with the tag reading I did myself. Issue 6985 otherwise supports the record: the maintainer triage states the chroot kernel mismatch, that the gate is evaluated in the ISO environment so the install mode cannot matter, and that the unmounted bind mount explains the Could not open file errors. Not exercised: no install was run from any ISO, and the bind-mount resume step was not tested. The v4.0.1 release carries no release assets and omacom/omarchy-iso has no tags or releases, so the ISO image itself could not be inspected and the version claim rests on the tagged script content.

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

Resuming a half-finished install by hand skips whatever the installer had not yet reached. If anything after the hardware phase also fails, reinstall from the v4.0.1 ISO rather than patching further, or the target may not boot cleanly.

Symptom

A clean Omarchy 4.0.0 (Quattro) install halts during the Configuring system phase with:


modprobe: FATAL: Module psmouse not found in directory /lib/modules/7.1.8-arch1-Watanare-T2-2-t2
[Failed]: /usr/share/omarchy/install/hardware/fix-synaptic-touchpad.sh (exit code: 1)

It does not matter whether you picked full-disk or free-space install. Reported on a ThinkPad (free-space dual boot), a Lenovo IdeaPad L340 (full disk) and a Lenovo IdeaPad 330-15IKB, plus one further full-disk report and one user who gave up and installed Omarchy 3.6 first. If you patch around it and resume by hand, the next hardware scripts fail with error: failed retrieving file '...' from disk : Could not open file /var/cache/omarchy/mirror/offline/... even with working internet.

Cause

Established by the maintainers' triage and fixed in #7236. install/hardware/fix-synaptic-touchpad.sh fires on any machine with an input device merely named synaptics and runs modprobe psmouse synaptics_intertouch=1. During an install it runs inside arch-chroot, where uname -r still names the live ISO's linux-t2 kernel while /lib/modules holds the target's stock linux, so modprobe cannot find the module, and because the hardware phase runs under set -euo pipefail the whole install stops. The follow-on Could not open file /var/cache/omarchy/mirror/offline/... errors are a consequence of resuming by hand: the installer bind-mounts the ISO's offline mirror into the target and unmounts it when it exits, leaving an empty directory that the target's pacman.conf still names as its only repository. That part is the triage's reading of the source, not something a reporter measured.

Fix

Install from the v4.0.1 ISO or later, and prefer the newest: v4.0.3 was published on 2026-09-08. #7236 merged into quattro on 2026-08-24 and the v4.0.1 tag (2026-08-25) carries the corrected script, which asks modprobe -qn psmouse before loading and warns instead of failing. That was checked by reading the script at both tags and at the installed 4.0.2-1 copy, not by running an install from the ISO. Installing Omarchy 3.6 and upgrading also avoids it, because the script only runs from the ISO, and one reporter did exactly that.

If you are stuck mid-install with the 4.0.0 ISO, patch the script in the target from the live environment. Two reporters confirmed that appending 2>/dev/null || true to the modprobe line gets past the touchpad step:


sed -i 's#^\(\s*modprobe psmouse synaptics_intertouch=1\).*#\1 2>/dev/null || true#' \
  /mnt/usr/share/omarchy/install/hardware/fix-synaptic-touchpad.sh
grep -n modprobe /mnt/usr/share/omarchy/install/hardware/fix-synaptic-touchpad.sh

The # delimiter is not cosmetic. With s|...|...| the literal || has to be written \|\|, and one escape short of that makes sed exit 1 with sed: -e expression #1, char 72: unknown option to 's' and leave the file untouched, which looks like the patch worked until the install fails again. The grep must print exactly:


  modprobe psmouse synaptics_intertouch=1 2>/dev/null || true

Before resuming, put the offline mirror back so the remaining hardware scripts can find their packages. This step is the triage's proposed resume and was not confirmed by a reporter, but the reporters who skipped it hit the Could not open file errors on every following script:


mount --bind /var/cache/omarchy/mirror/offline /mnt/var/cache/omarchy/mirror/offline
findmnt /mnt/var/cache/omarchy/mirror/offline
ls /mnt/var/cache/omarchy/mirror/offline | head

Then resume the way the original reporter did, with your install username:


arch-chroot /mnt /usr/bin/omarchy-apply-system --install-user <user> --first-install

Verify

On a v4.0.1 or later ISO the corrected script is in place:


grep -n 'modprobe -qn psmouse' /usr/share/omarchy/install/hardware/fix-synaptic-touchpad.sh

After a resumed 4.0.0 install, the [Failed] line does not recur and the hardware scripts complete. One reporter confirmed the rest of the install finished after patching the touchpad script and restoring package access.

Sources

omarchy-install-fails-psmouse-module-not-found