tuxedocomputers/tuxedo-control-center

No "Battery charging options" on TCC 2.1.7 on Pulse 15 gen1

Closed this issue ยท 7 comments

As by title, the "Battery charging options" section is not showing up.

Installed packages

ii  tuxedo-archive-keyring         2022.04.01~tux all          GnuPG archive keys of the tuxedo archive
ii  tuxedo-control-center          2.1.7          amd64
ii  tuxedo-drivers                 4.3.1          all          Kernel modules for TUXEDO devices
ii  tuxedo-keyboard                4.3.1          all          Keyboard back-light driver for ITE devices (dummy transitional package)
ii  tuxedo-keyboard-dkms           4.3.1          all          Keyboard back-light driver for ITE devices (dummy transitional package)

Kernel 6.7.7-amd64

I have the same problem. No more "Battery charging options" after update. Linux Mint 21.3 Cinnamon, 6.5.0-25-generic.
Nach Update auf tuxedo-drivers 4.3.2 am 12.03.2024 ist der Fehler behoben, kudos an das tuxedo team fรผr das schnelle update!

Same problem here
Fedora 39
Kernel: 6.7.7-200.fc39.x86_64
Model: Infinity Book Pro (Gen 7)

rpm -qa | grep tuxedo
tuxedo-touchpad-switch-1.0.7-1.fc39.x86_64
tuxedo-drivers-4.0.2-1.fc39.noarch
tuxedo-control-center-2.1.2-1.fc39.x86_64

sudo dkms status
tuxedo-drivers/4.0.2, 6.7.7-200.fc39.x86_64, x86_64: installed

(I am using the kallepm COPR repositories. It was working till some days ago)

I just realized Tuxedo provides a compiled version of drivers and the Tuxedo Control Center for Fedora. I gave them a try, but I am still getting the same problem. The touchpad LED isn't working, and there are no battery options or keyboard backlight options in the TCC.

Screenshot of the error:
Screenshot from 2024-03-12 18-06-27

Output of dkms command:

sudo dkms status
tuxedo-drivers/4.3.2, 6.7.7-200.fc39.x86_64, x86_64: installed (original_module exists)

Package versions:

tuxedo-drivers-4.3.2-1.noarch
tuxedo-control-center-2.1.7-1.x86_64

Some additional information from TCC journalctl:

Mar 13 10:26:15 fedora systemd[1]: Started tccd.service - TUXEDO Control Center Service.
Mar 13 10:26:15 fedora tccd[649639]: Starting daemon v2.1.7 (node: v14.20.0 arch: x64)
Mar 13 10:26:15 fedora tccd[649639]: No tuxedo-io found on start
Mar 13 10:26:15 fedora tccd[649639]: Filled missing settings with default: /etc/tcc/settings
Mar 13 10:26:17 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:17 fedora tccd[649639]: Could not find keyboard backlight. Retrying...
Mar 13 10:26:17 fedora tccd[649639]: Daemon started
Mar 13 10:26:18 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:18 fedora tccd[649639]: Could not find keyboard backlight. Retrying...
Mar 13 10:26:18 fedora tccd[649639]: FanControlWorker: Control unavailable
Mar 13 10:26:19 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:19 fedora tccd[649639]: Could not find keyboard backlight. Retrying...
Mar 13 10:26:20 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:20 fedora tccd[649639]: Could not find keyboard backlight. Retrying...
Mar 13 10:26:21 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:21 fedora tccd[649639]: Could not find keyboard backlight. Retrying...
Mar 13 10:26:22 fedora tccd[649639]: Detected no keyboard backlight
Mar 13 10:26:22 fedora tccd[649639]: Failed to configure keyboard backlight.

Hello everyone,

I did a test installation and for us the battery charging options do show up.

As by title, the "Battery charging options" section is not showing up.

Installed packages

ii  tuxedo-archive-keyring         2022.04.01~tux all          GnuPG archive keys of the tuxedo archive
ii  tuxedo-control-center          2.1.7          amd64
ii  tuxedo-drivers                 4.3.1          all          Kernel modules for TUXEDO devices
ii  tuxedo-keyboard                4.3.1          all          Keyboard back-light driver for ITE devices (dummy transitional package)
ii  tuxedo-keyboard-dkms           4.3.1          all          Keyboard back-light driver for ITE devices (dummy transitional package)

Kernel 6.7.7-amd64

What I am wondering looking at your installed packages: we recently renamed tuxedo-keyboard to tuxedo-drivers, I don't think it's nessesary to have them both installed and might be the root cause.

as for @izacarias I see a similar possible problem here, a quick google search alledged that (original_module exists) means dkms is throwing an error, also your whole problem looks like the classic "tuxedo-drivers not working".

I think the updating of the packages did not go smoothly and messed them up somehow.

I kindly ask you both to cleanly (purge old versions) reinstall tuxedo-drivers and see if the bug still persists.

best regards, Crissi

@crissi-tuxedo

I just removed everything from Tuxedo (with rpm -e <package_name>) and reinstalled only the Tuxedo Drivers package.
You are right. The problem seems to be with Tuxedo Drivers because the Touchpad on/off key doesn't work (the small white dot at the top-right of the touchpad). The Aeroplane mode key doesn't work as well.

I still need to figure out what is wrong.
At least the DKMS command now looks right:

sudo dkms status 
tuxedo-drivers/4.3.2, 6.7.9-200.fc39.x86_64, x86_64: installed

Package versions:

sudo rpm -qa | grep tuxedo
tuxedo-drivers-4.3.2-1.noarch

best regards,
Iuli

@izacarias

as this is an issue with tuxedo-drivers, would you be so kind to open an issue over there? :)

https://github.com/tuxedocomputers/tuxedo-drivers

best regards, Crissi

Hi Crissi!
Just a small update:
You were totally right. My problem was related to the tuxedo-drivers package (therefore, it had nothing to do with the Tuxedo Control Center).

I temporarily solved the problem by disabling the secure boot option in my BIOS. I will open an issue on the tuxedo-drivers Gitlab repository and ask them to add this information to the README file (or try to fix the problem of key enrollment).

Thank you very much for the feedback, and sorry for "spamming" the Tuxedo Control Centre issues thread :)

Best regards,
Iuli

Oh no, you are not spamming! :)

thank you for your detailed report, I will keep this in mind as a possible solution for future similar problems.

I will close this issue, as it's not a TCC issue

best regards,
Crissi