tuxedocomputers/tuxedo-control-center

Tuxedo Control Center no temperatures or fan

Closed this issue · 14 comments

Tccd 2.1.8 no errors in the logs

image

Linux 6.7.12 on Debian Testing

which device?

InfinityBook Pro 14 Gen8 (Intel only/without Nvidia RTX 3050)

What is the output of dkms status?

$ sudo dkms status
tuxedo-drivers/4.4.2, 6.6.15-amd64, x86_64: installed
tuxedo-drivers/4.4.2, 6.7.12-amd64, x86_64: installed

Have you rebooted since the last update?

sure, many times

I have the same issue.
image
Also, I can't find any configurations for battery thresholds anymore.

I have a similar issue (Tuxedo Pulse 14) and have this in the tccd logs:
sudo journalctl -u tccd

Jun 02 19:15:53 host systemd[1]: Started TUXEDO Control Center Service.
Jun 02 19:15:53 host tccd[1162]: Starting daemon v2.1.8 (node: v14.20.0 arch: x64)
Jun 02 19:15:53 host tccd[1162]: No tuxedo-io found on start
...
Jun 02 19:15:54 host tccd[1162]: Daemon started
Jun 02 19:15:55 host tccd[1162]: FanControlWorker: Control unavailable
...
Jun 02 19:15:58 host tccd[1162]: Failed to configure keyboard backlight.

I have tuxed-drivers installed (which afaik has tuxedo-io?)

sudo dpkg -s tuxedo-drivers
Package: tuxedo-drivers
Status: install ok installed

sudo dkms status
tuxedo-drivers/4.4.3, 6.5.0-28-generic, x86_64: installed
tuxedo-drivers/4.4.3, 6.5.0-35-generic, x86_64: installed

I have yet failed to reproduce the issue on a test device, but the not found tuxedo io would explain the missing values in the gui.

What is the output of lsmod | grep tuxedo?

If you don't see tuxedo_io pls try running sudo modprobe tuxedo_io, sudo systemctl restart tccd and restart tcc (right lick on try icon -> exit to fully close it), and for good messure maybe another lsmod | grep tuxedo, and sudo journalctl -u tccd

# modprobe -v tuxedo_io
insmod /lib/modules/6.7.12-amd64/updates/dkms/tuxedo_compatibility_check.ko.xz 
modprobe: ERROR: could not insert 'tuxedo_io': Key was rejected by service

Did you enable secure boot?

Please give the the output of mokutil --sb-state and mokutil --list-enrolled

Hi, yes secure boot was the cause. It works without secure boot. Suggestion: if tccd can't contact tuxedo-io, maybe it could give an hint

Yeah, the current state of secure boot on TUXEDO OS is turn it off or follow this setup guide: https://github.com/tuxedocomputers/Tuxedo-Linux-Kernel-Self-Signed-Certificate. It is on the medium turn todo list to improve the situation.