# Tuxedo-Drivers Not Working **URL:** \ **Category:** Bazzite\ **Created:** [August 20, 2024, 4:45am UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614 "2024-08-20T04:45:38Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Dheeraka\_Maddumage](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/dheeraka_maddumage/32/1966_2.png) [@Dheeraka\_Maddumage](https://universal-blue.discourse.group/u/Dheeraka_Maddumage)\ **Post date:** [August 20, 2024, 4:45am UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/1 "2024-08-20T04:45:38Z")
I have a Gigabyte G5 laptop with a clevo-built motherboard, similiar to the tuxedo laptops. So in order to control my keyboard backlight’ [TUXEDO Computers / Development / Packages / tuxedo-drivers · GitLab](https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers)’ this repo should be installed. It seems that since bazzite doesn’t support dkms i may not be able to install this. Hope there is a workaround and sorry to trouble you if i am asking a stupid senseless question. I tried to install with the rpm package but then this happens: ```auto error: Could not depsolve transaction; 1 problem detected: Problem: package dkms-3.0.13-1.fc40.noarch from fedora requires (kernel-devel-matched if kernel-core), but none of the providers can be installed - package kernel-devel-matched-6.10.4-200.fc40.x86_64 from updates requires kernel-core = 6.10.4-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.5-301.fc40.x86_64 from fedora requires kernel-core = 6.8.5-301.fc40, but none of the providers can be installed - package kernel-devel-matched-6.10.3-200.fc40.x86_64 from updates-archive requires kernel-core = 6.10.3-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.10-300.fc40.x86_64 from updates-archive requires kernel-core = 6.8.10-300.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.11-300.fc40.x86_64 from updates-archive requires kernel-core = 6.8.11-300.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.7-300.fc40.x86_64 from updates-archive requires kernel-core = 6.8.7-300.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.8-300.fc40.x86_64 from updates-archive requires kernel-core = 6.8.8-300.fc40, but none of the providers can be installed - package kernel-devel-matched-6.8.9-300.fc40.x86_64 from updates-archive requires kernel-core = 6.8.9-300.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.10-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.10-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.11-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.11-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.12-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.12-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.4-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.4-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.5-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.5-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.6-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.6-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.7-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.7-200.fc40, but none of the providers can be installed - package kernel-devel-matched-6.9.9-200.fc40.x86_64 from updates-archive requires kernel-core = 6.9.9-200.fc40, but none of the providers can be installed - cannot install both kernel-core-6.10.4-200.fc40.x86_64 from updates and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.5-301.fc40.x86_64 from fedora and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.10.3-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.10-300.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.11-300.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.7-300.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.8-300.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.8.9-300.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.10-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.11-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.12-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.4-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.5-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.6-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.7-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - cannot install both kernel-core-6.9.9-200.fc40.x86_64 from updates-archive and kernel-core-6.10.3-202.fsync.fc40.x86_64 from @System - package tuxedo-drivers-4.6.2-1.noarch from @commandline requires dkms >= 2.1, but none of the providers can be installed ``` ---
**Author:** ![andrea-nisti](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/andrea-nisti/32/3445_2.png) [@andrea-nisti](https://universal-blue.discourse.group/u/andrea-nisti)\ **Post date:** [October 27, 2024, 3:02pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/2 "2024-10-27T15:02:28Z")
did you find any solution to this? i bought a tuxedo laptop and I am stuck on the same issue ---
**Author:** ![Dheeraka\_Maddumage](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/dheeraka_maddumage/32/1966_2.png) [@Dheeraka\_Maddumage](https://universal-blue.discourse.group/u/Dheeraka_Maddumage)\ **Post date:** [November 10, 2024, 3:51am UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/3 "2024-11-10T03:51:58Z")
Nope 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 ---
**Author:** ![m2Giles](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/m2giles/32/471_2.png) [@m2Giles](https://universal-blue.discourse.group/u/m2Giles)\ **Post date:** [November 10, 2024, 4:30pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/4 "2024-11-10T16:30:32Z")
Will need the dkms package converted into an akmod package. Then it needs to be built in our akmods repo. ---
**Author:** ![salim](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/salim/32/3536_2.png) [@salim](https://universal-blue.discourse.group/u/salim)\ **Post date:** [December 9, 2024, 1:32pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/5 "2024-12-09T13:32:09Z")
Here are the relevant GitHub issues for supporting the out-of-tree `tuxedo-drivers` in universal blue images: - [ublue-os/akmods#30](https://github.com/ublue-os/akmods/issues/30) - [ublue-os/akmods#129](https://github.com/ublue-os/akmods/issues/129) - [ublue-os/bluefin#898](https://github.com/ublue-os/bluefin/issues/898) [Etienne Schmidt](https://github.com/gladion136) started work to build tuxedo-drivers as kmods [here](https://github.com/gladion136/tuxedo-drivers-kmod), see their post [here](https://github.com/ublue-os/akmods/issues/30#issuecomment-2495687756)! More testing is needed… ---
**Author:** ![BrickMan240](https://avatars.discourse-cdn.com/v4/letter/b/9de0a6/32.png) [@BrickMan240](https://universal-blue.discourse.group/u/BrickMan240)\ **Post date:** [February 14, 2025, 11:40am UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/6 "2025-02-14T11:40:55Z")
Hey everyone! I’m not a member of the Universal Blue project, but I did something with Etienne Schmidt’s efforts and the custom image template by Universal Blue. I have unofficial images you can use right now with Tuxedo drivers preinstalled. You’d be be getting your hardware working before official support, and helping test the drivers for upstream implementation. Here’s my repo: > **[GitHub - BrickMan240/ublue-tuxedo-tcc: Popular Universal Blue images, modified to have...](https://github.com/BrickMan240/ublue-tuxedo-tcc)** > > Popular Universal Blue images, modified to have Tuxedo Control Center by Tuxedo, and the kmod port of their drivers (big thanks to gladion136). Ready for testing until the Ublue project decides to merge the drivers themselves into their images (huge fan of their work btw). ---
**Author:** ![CyberOto](https://avatars.discourse-cdn.com/v4/letter/c/dc4da7/32.png) [@CyberOto](https://universal-blue.discourse.group/u/CyberOto)\ **Post date:** [February 15, 2025, 4:11pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/7 "2025-02-15T16:11:14Z")
Hey, I just switched my Tuxedo Pulse 14 Gen 3 to `tuxedo-bluefin` and I’m happy to report that all TCC functionality works as expected. I was also pleasantly surprised that GNOME Keyboard panel for keyboard light levels is also there. Let me know if you need some specific testing to be performed. ---
**Author:** ![BrickMan240](https://avatars.discourse-cdn.com/v4/letter/b/9de0a6/32.png) [@BrickMan240](https://universal-blue.discourse.group/u/BrickMan240)\ **Post date:** [February 16, 2025, 1:02pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/8 "2025-02-16T13:02:01Z")
Nothing in mind. Just use the drivers, mess with settings, and open an issue if you notice something off. On another note, if the drivers get officially added, don’t forget to switch to the official images instead. This is more of an immediate and temporary solution until that happens, so I might not maintain too well. I’ll probably update the scripts to just pull the official images and not alter them, so that people that are unknowingly still on my images continue getting security updates. At any rate, until then, I hope it’s useful. ---
**Author:** ![blended\_perk](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/blended_perk/32/6094_2.png) [@blended\_perk](https://universal-blue.discourse.group/u/blended_perk)\ **Post date:** [May 1, 2025, 7:41pm UTC](https://universal-blue.discourse.group/t/tuxedo-drivers-not-working/3614/9 "2025-05-01T19:41:48Z")
I found a [Gnome extension](https://github.com/StevenSeifried/tuxedo-fnlock-status) for displaying FN lock status of Tuxedo laptops. You might find it useful.