-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Notes from making the Corsair iCUE NEXUS work on Linux — a 640×48 touchscreen that clips to a keyboard, sold to be driven by Windows-only software.
This wiki is the how and why: what the hardware actually does, how each fact
was established, and which assumptions turned out to be wrong. The reference
tables live in the repository under docs/;
the pages here are the reasoning behind them.
Not affiliated with or endorsed by Corsair.
| Page | What it covers |
|---|---|
| The Panel | What the hardware is, measured rather than quoted |
| Reverse Engineering the NEXUS | The protocol, and how each part of it was pinned down |
| Device Access on Linux | udev, uaccess, and the rule-ordering trap that silently grants nothing |
| Rendering | Drawing for a 13.3:1 strip with 18-bit colour |
| Music Visualizers | Audio capture, the analysis chain, and 32 modes |
| How We Measured It | The method: instruments, and controls in both directions |
| Traps | The mistakes, kept because each one cost real time |
The first thing worth writing down, because it is the first thing anyone tries.
CorsairOfficial/cue-sdk is a client of the iCUE daemon, not a hardware
protocol SDK. iCUE runs on Windows and macOS only, so every binding — Python,
Node, .NET — inherits that limitation. There is no configuration of it that
talks to the panel on Linux.
The panel itself, though, is an ordinary USB HID device. Everything here is
built on hidraw.