Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Synaptics touchpad not working after upgrade - requires `synaptics_intertouch` parameter
Reported by c3d · filed May 28, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Problem
After upgrading Omarchy to kernel 7.0.9-arch2-1, the Synaptics touchpad (model TM3114-001) stopped working. The touchpad was detected but not functional. A second installation on the same machine that had not been upgraded (still running kernel 7.0.3-arch1-2) continued to work correctly with the same hardware.
Hardware Details
- Touchpad: Synaptics TM3114-001 (PNP: SYN3228 SYN1e00 SYN0002 PNP0f13)
- Firmware: 8.1, id: 0x1e2b1
- Board id: 3114, fw id: 1805562
Root Cause
The touchpad supports both PS/2 and I2C/RMI4 interfaces. The newer kernel defaults to using the legacy PS/2 interface (via psmouse driver), which does not work properly. The kernel even logs a suggestion:
psmouse serio1: synaptics: Your touchpad says it can support a different bus.
If i2c-hid and hid-rmi are not used, you might want to try setting
psmouse.synaptics_intertouch to 1Solution
Enable the synaptics_intertouch parameter to use the I2C/RMI4 driver instead:
- Create
/etc/modprobe.d/psmouse.conf:
options psmouse synaptics_intertouch=1- Reload the module:
sudo modprobe -r psmouse
sudo modprobe psmouseAfter this change, the touchpad appears as "Synaptics TM3114-001" using the rmi4 driver instead of "SynPS/2 Synaptics TouchPad" and works correctly.
Recommendation
Consider adding this configuration to the default Omarchy installation for better hardware compatibility with Synaptics touchpads that support I2C/RMI4.
View raw text
## Problem After upgrading Omarchy to kernel 7.0.9-arch2-1, the Synaptics touchpad (model TM3114-001) stopped working. The touchpad was detected but not functional. A second installation on the same machine that had not been upgraded (still running kernel 7.0.3-arch1-2) continued to work correctly with the same hardware. ## Hardware Details - Touchpad: Synaptics TM3114-001 (PNP: SYN3228 SYN1e00 SYN0002 PNP0f13) - Firmware: 8.1, id: 0x1e2b1 - Board id: 3114, fw id: 1805562 ## Root Cause The touchpad supports both PS/2 and I2C/RMI4 interfaces. The newer kernel defaults to using the legacy PS/2 interface (via psmouse driver), which does not work properly. The kernel even logs a suggestion: ``` psmouse serio1: synaptics: Your touchpad says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 ``` ## Solution Enable the synaptics_intertouch parameter to use the I2C/RMI4 driver instead: 1. Create `/etc/modprobe.d/psmouse.conf`: ``` options psmouse synaptics_intertouch=1 ``` 2. Reload the module: ```bash sudo modprobe -r psmouse sudo modprobe psmouse ``` After this change, the touchpad appears as "Synaptics TM3114-001" using the rmi4 driver instead of "SynPS/2 Synaptics TouchPad" and works correctly. ## Recommendation Consider adding this configuration to the default Omarchy installation for better hardware compatibility with Synaptics touchpads that support I2C/RMI4.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 03:50 UTC