Package Details: tuxedo-drivers-dkms 4.22.2-1

Git Clone URL: https://aur.archlinux.org/tuxedo-drivers-dkms.git (read-only, click to copy)
Package Base: tuxedo-drivers-dkms
Description: TUXEDO Computers kernel module drivers for keyboard, keyboard backlight & general hardware I/O using the SysFS interface
Upstream URL: https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
Keywords: tuxedo tuxedo-drivers
Licenses: GPL-2.0-or-later
Conflicts: tuxedo-keyboard-dkms, tuxedo-keyboard-ite-dkms
Provides: clevo-acpi, clevo-wmi, ite_8291, ite_8291_lb, ite_8297, ite_829x, tuxedo-io, tuxedo-keyboard, tuxedo-keyboard-ite, uniwill-wmi
Submitter: StevenSeifried
Maintainer: StevenSeifried
Last Packager: StevenSeifried
Votes: 47
Popularity: 1.26
First Submitted: 2023-12-11 18:55 (UTC)
Last Updated: 2026-05-01 21:28 (UTC)

Dependencies (6)

Required by (7)

Sources (2)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

skaman commented on 2026-04-24 13:08 (UTC)

@jonest, i stumbled in the same problem and i got fixed after updating also the Tuxedo Control Center to the version 3.0.3. It look like some incompatibility between the new driver and some previous version of tuxedo control center.

StevenSeifried commented on 2026-04-11 11:34 (UTC)

@jonest I will take a look if I can reproduce it, when I find spare time. It might be an upstream bug, so feel free to report it

jonest commented on 2026-04-11 11:27 (UTC) (edited on 2026-04-11 11:30 (UTC) by jonest)

I had a significant performance regression after the patch to 4.22.1-1. The problem was CPU as utilization was extremely high when viewing in top and common tasks typically took about 50-100 times longer. I have a Infinitybook 14 Pro Gen 10 with the AMD Ryzen 9 HX 370. The fix was to downgrade to version 4.21.3-1. I did not see any errors in any logs related to the install or system use after a reboot. The following are the relevant upgrade logs from pacman.log. 

[2026-04-11T09:29:27+0100] [ALPM] running '71-dkms-remove.hook'...
[2026-04-11T09:29:28+0100] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod tuxedo-drivers/4.21.3 -k 6.19.11-arch1-1
[2026-04-11T09:29:29+0100] [ALPM-SCRIPTLET] ==> depmod 6.19.11-arch1-1
[2026-04-11T09:29:32+0100] [ALPM] transaction started
[2026-04-11T09:29:32+0100] [ALPM] upgraded tuxedo-drivers-dkms (4.21.3-1 -> 4.22.1-1)
[2026-04-11T09:29:32+0100] [ALPM] transaction completed
[2026-04-11T09:29:32+0100] [ALPM] running '25-systemd-hwdb.hook'...
[2026-04-11T09:29:32+0100] [ALPM] running '35-systemd-udev-reload.hook'...
[2026-04-11T09:29:32+0100] [ALPM] running '35-systemd-update.hook'...
[2026-04-11T09:29:32+0100] [ALPM] running '70-dkms-install.hook'...
[2026-04-11T09:29:32+0100] [ALPM-SCRIPTLET] ==> dkms install --no-depmod tuxedo-drivers/4.22.1 -k 6.19.11-arch1-1
[2026-04-11T09:29:40+0100] [ALPM-SCRIPTLET] ==> depmod 6.19.11-arch1-1
[2026-04-11T09:29:43+0100] [ALPM] running '90-kernel-install.hook'...
[2026-04-11T09:29:43+0100] [ALPM-SCRIPTLET] Running kernel-install for 6.19.11-arch1-1
[2026-04-11T09:29:59+0100] [ALPM] running 'rebuild-detector.hook'...
[2026-04-11T09:30:00+0100] [PACMAN] Running 'pacman -D -q --asexplicit --config /etc/pacman.conf -- tuxedo-drivers-dkms'

Dreamkey commented on 2025-10-28 22:17 (UTC) (edited on 2025-10-28 22:18 (UTC) by Dreamkey)

Found the same issue as @sekret.

/usr/lib/modules/$(uname -r)/kernel/drivers/platform/x86/tuxedo/nb04/tuxedo_nb04_wmi_ab.ko.zst is owned by linux but is deleted. Maybe because /usr/lib/modules/$(uname -r)/updates/dkms/tuxedo_nb04_wmi_ab.ko.zst is generated?

hkdb commented on 2025-10-24 14:23 (UTC) (edited on 2025-10-24 14:28 (UTC) by hkdb)

Been having trouble updating this on cachyos due to a bunch of build errors. Just dropping what worked for me here in case it helps someone else.

After failing to update, I changed the package(){} block in PKGBUILD in cache as per below:

package() {

  # Create necessary directories first
  mkdir -p "$pkgdir/usr/src/${pkgname%-dkms}-$pkgver"
  mkdir -p "$pkgdir/usr/lib/modprobe.d"
  mkdir -p "$pkgdir/usr/lib/udev/rules.d"
  mkdir -p "$pkgdir/usr/lib/udev/hwdb.d"

  install -Dm644 "${_pkgname}-v$pkgver"/debian/tuxedo-drivers.dkms "$pkgdir/usr/src/${pkgname%-dkms}-$pkgver/dkms.conf"
  sed -i "s/#MODULE_VERSION#/$pkgver/g" "$pkgdir/usr/src/${pkgname%-dkms}-$pkgver/dkms.conf"

  # Use cp instead of install -t
  cp -p "${_pkgname}-v$pkgver"/usr/lib/modprobe.d/*.conf "$pkgdir/usr/lib/modprobe.d/"
  cp -p "${_pkgname}-v$pkgver"/usr/lib/udev/rules.d/*.rules "$pkgdir/usr/lib/udev/rules.d/"
  cp -p "${_pkgname}-v$pkgver"/usr/lib/udev/hwdb.d/*.hwdb "$pkgdir/usr/lib/udev/hwdb.d/"

  cp -r "${_pkgname}-v$pkgver"/src/* "$pkgdir/usr/src/${pkgname%-dkms}-$pkgver/"

}

It's basically removing some trailing %s and using mkdir/cp instead of install -t.

Then, just run:

makepkg -si

seebi commented on 2025-09-04 15:12 (UTC)

I just installed this package on a Tuxedo InfinityBook Pro with CachyOS to have sound but there is still no device available. Any ideas how to fix that?

Karrde commented on 2025-08-18 07:03 (UTC)

Today with the update to Kernel 6.16.1-arch1-1 I got a warning about the same module as sekret on my TUXEDO Gemini Gen2 but it said "Warning: could not get file information ..." (roughly translated from German).

Maybe I missed that warning when i got tuxedo-drivers-dkms 4.15.0-2 itself a few days ago.

sekret commented on 2025-08-16 10:11 (UTC) (edited on 2025-08-16 10:11 (UTC) by sekret)

When I run pacman -Qkk, I get this message

warning: linux: /usr/lib/modules/6.16.0-arch2-1/kernel/drivers/platform/x86/tuxedo/nb04/tuxedo_nb04_wmi_ab.ko.zst (No such file or directory)

I think this started with the current linux package version seen in the file path.

londeril commented on 2025-07-31 14:57 (UTC)

Yes! Thanks, Steven! Works again!

MrMike commented on 2025-07-31 13:38 (UTC)

4.14.4 installed perfectly this morning. Thank you so much for that lightning-quick fix, Steven!

1 2 3 4 5 6 .. 9 Next › Last »