Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-320GitHub issuePublicDecided· Out of scope

Lenovo IdeaPad 1 ELAN061A touchpad requires i2c_hid_acpi

Reported by Padanerd · filed Sep 19, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Lenovo IdeaPad 1 ELAN061A touchpad requires i2c_hid_acpirevision 1 · captured 2026-09-28 21:23 UTC via poll

Lenovo IdeaPad 1 11IGL05 ELAN061A touchpad fails with elan_i2c

System

  • Hardware: Lenovo IdeaPad 1 11IGL05 (DMI product 81VT)
  • BIOS: DWCN17WW
  • Omarchy: 4.0.4-1
  • Kernels tested: 7.2.5-3-omarchy and 6.18.49-3-lts
  • Touchpad: Elan Touchpad, ACPI device ELAN061A, 04f3:006b

Problem

The touchpad is detected, but it does not produce usable pointer input in Omarchy. Both the Omarchy kernel and the LTS kernel bind the device to elan_i2c and repeatedly log:

elan_i2c i2c-ELAN061A:00: invalid report id data (0)

The Hyprland input configuration does not disable the touchpad.

The same laptop touchpad worked in Linux Mint 22.3, confirming that the hardware is functional.

Reproduction

  1. Boot Omarchy on the Lenovo IdeaPad 1 11IGL05.
  2. The device is bound to elan_i2c.
  3. The touchpad is unresponsive and the kernel logs invalid report ID errors.

Workaround

Unbind the device from elan_i2c and bind it to i2c_hid_acpi:

d=/sys/bus/i2c/drivers
n=i2c-ELAN061A:00
printf '%s\n' "$n" | sudo tee "$d/elan_i2c/unbind"
sleep 1
printf '%s\n' "$n" | sudo tee "$d/i2c_hid_acpi/bind"

The touchpad works immediately with i2c_hid_acpi. Making the following modprobe rule persistent also makes it work after reboot:

blacklist elan_i2c

Expected behavior

The ELAN061A touchpad should automatically bind to a working driver, or Omarchy should provide a model-specific compatibility rule. The generic blacklist should not be required for this laptop.

View raw text
## Lenovo IdeaPad 1 11IGL05 ELAN061A touchpad fails with `elan_i2c`

### System

- Hardware: Lenovo IdeaPad 1 11IGL05 (DMI product `81VT`)
- BIOS: `DWCN17WW`
- Omarchy: `4.0.4-1`
- Kernels tested: `7.2.5-3-omarchy` and `6.18.49-3-lts`
- Touchpad: `Elan Touchpad`, ACPI device `ELAN061A`, `04f3:006b`

### Problem

The touchpad is detected, but it does not produce usable pointer input in Omarchy. Both the Omarchy kernel and the LTS kernel bind the device to `elan_i2c` and repeatedly log:

```text
elan_i2c i2c-ELAN061A:00: invalid report id data (0)
```

The Hyprland input configuration does not disable the touchpad.

The same laptop touchpad worked in Linux Mint 22.3, confirming that the hardware is functional.

### Reproduction

1. Boot Omarchy on the Lenovo IdeaPad 1 11IGL05.
2. The device is bound to `elan_i2c`.
3. The touchpad is unresponsive and the kernel logs invalid report ID errors.

### Workaround

Unbind the device from `elan_i2c` and bind it to `i2c_hid_acpi`:

```bash
d=/sys/bus/i2c/drivers
n=i2c-ELAN061A:00
printf '%s\n' "$n" | sudo tee "$d/elan_i2c/unbind"
sleep 1
printf '%s\n' "$n" | sudo tee "$d/i2c_hid_acpi/bind"
```

The touchpad works immediately with `i2c_hid_acpi`. Making the following modprobe rule persistent also makes it work after reboot:

```text
blacklist elan_i2c
```

### Expected behavior

The ELAN061A touchpad should automatically bind to a working driver, or Omarchy should provide a model-specific compatibility rule. The generic blacklist should not be required for this laptop.

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 15:56 UTC