Slimbook and TUXEDO on Omarchy Linux

Verdict

Silver. Omarchy has shipped vendor-specific enablement for Slimbook and TUXEDO since 3.4.0, Slimbook now sells machines with Omarchy preinstalled, and the issue tracker is almost empty for both brands. But “almost empty” cuts both ways. Three issues across two vendors is not enough to call any subsystem confirmed working, so most of the subsystem table on this page says unknown on purpose.

Treat these as Clevo chassis with a Linux-first vendor in front of them. That buys you two things Omarchy uses: a working keyboard backlight driver and a Motorcomm ethernet driver. It does not buy you a tested fingerprint reader or a tested webcam.

If you want the shortest path, buy a Slimbook SKU that the vendor ships with Omarchy on the disk. You get the factory provisioning flow described below instead of an install.

What works

The keyboard backlight works once tuxedo-drivers-nocompatcheck-dkms is installed, which Omarchy does for you. DHH added this in v3.5.0 under the line “Fix keyboard backlighting for Tuxedo/Slimbook laptops”.

Wired ethernet on the Slimbook Executive works. The machine uses a Motorcomm YT6801 NIC that the mainline kernel does not drive, so v3.4.0 added yt6801-dkms behind an lspci check.

Suspend works on 4.x on the one TUXEDO that reported a problem. In issue #6380 hirschnase reported that suspend broke going from 3.8.2 to 3.8.4 on an InfinityBook Pro 15 Gen10 AMD, and later commented that after updating to Quattro the problem was gone and sleep worked again on that machine.

The TUXEDO InfiniteBook Pro 14 sits on DHH’s hardware list, described there as a matte 3K screen, an 80 Wh battery, dual NVMe, built-in ethernet and HDMI, five USB ports, at 1.45 kg. That is a recommendation, not a test report, and it is not an endorsement by Omarchy of every TUXEDO SKU.

What breaks

Suspend on 3.8.4. Issue #6380 is the clearest data point on this page. The screen went black, the power LED changed colour, and the machine needed a hard reset. It is closed and the reporter says 4.x fixed it, so if you are still on 3.8.4 the fix is to update rather than to chase power profile rules.

Graphics teardown crashes on 4.0.3. In issue #11376 jaredpohl posted the only detailed Slimbook report on the tracker: a SLIMBOOK Executive-14-UC2 with an Intel Core Ultra 7 255H and Arc Pro 130T/140T graphics, hitting a SIGSEGV inside Aquamarine::CDRMBackend::flushAsyncCommitEvents() when both the SDDM greeter compositor and the user session exit. The desktop still starts, so this is noise in coredumpctl rather than a broken machine, and it is not Slimbook-specific: the same issue collects NVIDIA and AMD reports. Read it with one caveat the reporter flags: that machine had Slimbook’s own vendor repository enabled next to the Omarchy mirror, so it is not a stock package set.

Black screen after login on 3.x. Issue #4278 came from a Tuxedo 14 inch with a Ryzen AI 9 HX 370 in January 2026. The reporter recovered by switching to a TTY, removing the Hyprland config, rebooting into the default config and running omarchy-reinstall. That predates Quattro and the Lua config format, so the recovery steps no longer apply verbatim.

Nothing else is reported. There is no Slimbook or TUXEDO Wi-Fi issue, no audio issue, no fingerprint issue in the data. That is an absence of evidence, not a clean bill of health.

What Omarchy does for this model

Two scripts sit in install/hardware/all.sh. That file is sourced by omarchy-apply-hardware, which omarchy-apply-system calls while the installer finalises the machine. It is not part of omarchy-update, which runs omarchy-migrate instead, so an in-place update does not re-run hardware detection.

install/hardware/fix-tuxedo-backlight.sh reads /sys/class/dmi/id/sys_vendor and matches TUXEDO or Slimbook, case-insensitively. When it matches it installs tuxedo-drivers-nocompatcheck-dkms, writes blacklist clevo_xsm_wmi to /etc/modprobe.d/blacklist-clevo-xsm-wmi.conf, and deletes any leftover clevo-xsm-wmi.ko in /lib/modules/*/extra/. The comment in the file explains why: if clevo_xsm_wmi loads first it grabs the Clevo WMI GUIDs and tuxedo-drivers cannot bring up the backlight.

install/hardware/fix-yt6801-ethernet-adapter.sh greps lspci for YT6801 or a Motorcomm ethernet controller and installs yt6801-dkms.

Note what these do not do. Neither script calls omarchy-hw-match, which is the helper other vendors use to match on product_name or product_family. The match here is vendor-wide, so every Slimbook and every TUXEDO gets the same treatment regardless of model. There is also no speaker tuning: default/audio/tunings/ in v4.0.4 contains only dell-xps-2026.

Version differences matter here. On 3.5.0 through 3.8.4 the backlight script ended with [ -f "$f" ] && sudo rm "$f" inside a loop, which returns non-zero when the glob matches nothing and could take the rest of hardware setup down with it. v4.0.0 rewrote that as a plain if block, listed in the Quattro notes as “Stop the Tuxedo/Slimbook backlight fix from aborting hardware setup”. In 4.0.4 both scripts also stopped asking for linux-headers by name. The 4.0.4 notes lead with “Install our bespoke kernel and set linux-omarchy as the default boot option”, and the package list swapped linux-headers for linux-omarchy-headers to match. Because the hardware scripts do not re-run on update, 4.0.4 also ships a migration that installs the matching headers package for linux-omarchy or linux-t2 on machines that were missing it. If your DKMS modules are the reason you care about this page, 4.0.4 is the release you want.

Variants

Prefer a Slimbook SKU sold with Omarchy preinstalled if you do not want to flash a USB stick at all. Confirm the model and the shipped Omarchy version with Slimbook directly before ordering.

The Slimbook Executive is the best-covered model in Omarchy’s own code, since both quirk scripts name it. The Executive-14-UC2, with Arrow Lake-P era Arc Pro 130T/140T graphics on i915, is the one machine with a public 4.0.3 report.

The TUXEDO InfinityBook Pro line is the best-covered on the issue tracker, such as it is: a Gen10 AMD 15 inch and a 14 inch Ryzen AI 9 HX 370. The InfiniteBook Pro 14 is the one DHH lists, with a small right Shift key on the US ANSI layout as the noted annoyance.

Older Clevo rebadges from either vendor are unrated. The clevo_xsm_wmi blacklist exists precisely because those machines may have an out-of-tree module installed from elsewhere.

TUXEDO OS is not Omarchy. Buying TUXEDO hardware does not mean the vendor supports Omarchy on it.

Before you install

• Run cat /sys/class/dmi/id/sys_vendor from the live ISO. If it does not contain TUXEDO or Slimbook, neither quirk script will fire and your backlight is on its own.
• Run lspci | grep -i ethernet and look for Motorcomm or YT6801. That tells you whether you depend on yt6801-dkms, and therefore on working kernel headers.
• Install 4.0.4 or later, or update to it first. Older releases carried the backlight script bug and asked for the wrong headers package. On an updated machine the 4.0.4 migration is what repairs the headers, since the hardware scripts themselves only run at install time.
• Test suspend from the System menu before you rely on the machine. Do it on battery and on AC, since the power profile switches between them.
• If you bought the machine preinstalled, run omarchy version and omarchy update on day one. A factory image can be months behind the current release.
• If you are reselling or handing the machine on, Setup > Reset Computer returns a Quattro-installed machine to its first-boot state. It only works on machines installed from the Quattro ISO, not on ones upgraded from 3.x.

Related

• /hardware/suspend-sleep/ and /fix/suspend-wont-resume-s2idle/ for the failure in #6380
• /hardware/intel-gpu/ for the Arc Pro 130T/140T graphics on the Executive-14-UC2
• /fix/quickshell-crashes-or-bar-missing/ and /fix/black-screen-after-login/
• /upgrade/3-to-4-quattro/ if you are still on 3.8.4 with broken suspend
• /hardware/submit/ if you own one of these and can fill in the unknowns
• Omarchy manual: system sleep, updates, troubleshooting