Proof Portal

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-5057GitHub issuePublicReceived

MSI Titan GT77HX: RGB keyboard control not supported by msi-perkeyrgb

Reported by andyholst · filed Sep 12, 2026Closed upstream on 2026-09-15 by its own reporter andyholst. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

MSI Titan GT77HX: RGB keyboard control not supported by msi-perkeyrgbrevision 1 · captured 2026-10-04 12:10 UTC via poll

Summary

The MSI Titan GT77HX 13VI uses a Cherry MX Ultra Low Profile mechanical keyboard that msi-perkeyrgb does not support. The tool executes without error but has no effect on the hardware.

Background

PR #11549 initially included RGB config creation (/etc/msi-perkeyrgb.conf) and udev rules for hidraw permissions. After testing, it was discovered that:

  • msi-perkeyrgb exits with code 0 (success)
  • The config file is created correctly (all steady 00ff00)
  • The hidraw device exists (/dev/hidraw0, 1038:113a, SteelSeries KLC)
  • udev rules set correct permissions (MODE="0666")
  • But the keyboard does not respond to any RGB commands

Root Cause

msi-perkeyrgb is designed for older SteelSeries membrane keyboards (GE63, GS75, etc.). The Titan GT77HX 13VI uses a Cherry MX mechanical keyboard with a different HID protocol that the tool does not implement.

$ msi-perkeyrgb --list-models
Available laptop models are:
GE63, GE73, GE75, GS63, GS73, GS75, GX63, GT63, GL63, GS65

No Titan or GT77 models are listed.

Hardware

ComponentDevice
KeyboardCherry MX Ultra Low Profile Mechanical per-key RGB (SteelSeries)
USB ID1038:113a (SteelSeries KLC)
USB ID1038:1146 (SteelSeries ALC)
EC firmware17Q2IMS1.107

What Was Removed

PR #11549 was updated to remove:
- msi-perkeyrgb package installation from msi.sh
- /etc/msi-perkeyrgb.conf creation
- /etc/udev/rules.d/99-msi-rgb.rules creation
- All RGB-related tests from hw-msi-test.sh

Future Direction

This issue is to track adding RGB support for the Titan GT77HX when a compatible tool or kernel driver becomes available. Possible approaches:
- Add GT77HX support to msi-perkeyrgb (upstream contribution)
- Use SteelSeries GG via Wine/Proton
- Use OpenRGB when they add Titan support
- Reverse-engineer the HID protocol for Cherry MX keyboards

Related

  • PR #11549 — MSI laptop driver optimizations (RGB removed from scope)
  • Issue #11532 — Original MSI driver optimizations issue
  • https://github.com/Askannz/msi-perkeyrgb — upstream tool (last updated 2022)
View raw text
## Summary

The MSI Titan GT77HX 13VI uses a **Cherry MX Ultra Low Profile mechanical keyboard** that `msi-perkeyrgb` does not support. The tool executes without error but has no effect on the hardware.

## Background

PR #11549 initially included RGB config creation (`/etc/msi-perkeyrgb.conf`) and udev rules for hidraw permissions. After testing, it was discovered that:

- `msi-perkeyrgb` exits with code 0 (success)
- The config file is created correctly (`all steady 00ff00`)
- The hidraw device exists (`/dev/hidraw0`, `1038:113a`, SteelSeries KLC)
- udev rules set correct permissions (MODE="0666")
- **But the keyboard does not respond to any RGB commands**

## Root Cause

`msi-perkeyrgb` is designed for older SteelSeries membrane keyboards (GE63, GS75, etc.). The Titan GT77HX 13VI uses a Cherry MX mechanical keyboard with a different HID protocol that the tool does not implement.

```
$ msi-perkeyrgb --list-models
Available laptop models are:
GE63, GE73, GE75, GS63, GS73, GS75, GX63, GT63, GL63, GS65
```

No Titan or GT77 models are listed.

## Hardware

| Component | Device |
|-----------|--------|
| Keyboard | Cherry MX Ultra Low Profile Mechanical per-key RGB (SteelSeries) |
| USB ID | 1038:113a (SteelSeries KLC) |
| USB ID | 1038:1146 (SteelSeries ALC) |
| EC firmware | 17Q2IMS1.107 |

## What Was Removed

PR #11549 was updated to remove:
- `msi-perkeyrgb` package installation from `msi.sh`
- `/etc/msi-perkeyrgb.conf` creation
- `/etc/udev/rules.d/99-msi-rgb.rules` creation
- All RGB-related tests from `hw-msi-test.sh`

## Future Direction

This issue is to track adding RGB support for the Titan GT77HX when a compatible tool or kernel driver becomes available. Possible approaches:
- Add GT77HX support to `msi-perkeyrgb` (upstream contribution)
- Use SteelSeries GG via Wine/Proton
- Use OpenRGB when they add Titan support
- Reverse-engineer the HID protocol for Cherry MX keyboards

## Related

- PR #11549 — MSI laptop driver optimizations (RGB removed from scope)
- Issue #11532 — Original MSI driver optimizations issue
- https://github.com/Askannz/msi-perkeyrgb — upstream tool (last updated 2022)

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.

No decision has been recorded yet.