Skip to content

Linux Troubleshooting

oxGorou edited this page May 29, 2026 · 8 revisions

Linux Troubleshooting


Daemon not running

Symptom: The app shows "Daemon is not running" on launch.

sudo systemctl status uxtu4linux.service
sudo systemctl start uxtu4linux.service

If it keeps failing, check the logs:

journalctl -u uxtu4linux.service -n 50

From inside the app, go to Settings -> Daemon Service -> Install & enable to reinstall the service.


Secure Boot blocking ryzenadj

Symptom: The daemon logs show ryzen_smu module not loaded and Secure Boot is on.

Option 1: Disable Secure Boot in your UEFI firmware settings.

Option 2: Install and sign the module with your MOK key:

# Install build dependencies (Fedora example)
sudo dnf install cmake gcc gcc-c++ dkms openssl

# Clone and install ryzen_smu via DKMS
git clone https://github.com/amkillam/ryzen_smu
cd ryzen_smu
sudo make dkms-install

# Enroll the DKMS signing key
sudo mokutil --import /var/lib/dkms/mok.pub

Reboot. The system will enter MOK Manager, choose Enroll MOK, enter the password you set, and reboot again.

Verify the module loaded:

lsmod | grep ryzen_smu

dmidecode not found

sudo apt install dmidecode      # Debian / Ubuntu
sudo dnf install dmidecode      # Fedora / RHEL
sudo pacman -S dmidecode        # Arch
sudo zypper install dmidecode   # openSUSE

ryzenadj not found or not executable

chmod +x /opt/uxtu4linux/src/Assets/Linux/ryzenadj

If the binary is missing entirely, trigger a fresh download from About -> Force update.


PermissionError on config or preset files

This usually happens if the installer was run as root instead of a normal user, leaving files owned by root.

sudo chown -R $USER:$USER /opt/uxtu4linux

CPU not detected / wrong preset loading

Hardware detection reads your CPU via dmidecode. If it returned an unrecognised or empty string, set it manually in config.ini:

[Info]
cpu = AMD Ryzen 5 7535HS with Radeon Graphics

Use a known model string matching your actual hardware family. See the full [Info] key reference in Configuration.


Custom preset shows "not found" in daemon logs

This happens when a custom preset name is referenced in config.ini but the corresponding entry no longer exists in custom.json, for example after a manual edit or a file corruption.

Fix: Open Power Management -> Select Preset and choose a valid preset. This updates config.ini and the daemon picks it up automatically.

Alternatively, edit config.ini directly:

[User]
mode = Balance

Python version too old

UXTU4Linux requires Python 3.10 or later. Check your version:

python3 --version

Install a newer version:

# Ubuntu 20.04 (via deadsnakes PPA)
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt install python3.11 python3.11-venv

# Fedora / RHEL
sudo dnf install python3.11

# Arch (always ships latest)
sudo pacman -S python

Then re-run the installer.


pyzmq not installed / ZMQ errors

The daemon communicates with the app via ZMQ. If pyzmq is missing:

/opt/uxtu4linux/venv/bin/pip install pyzmq

Then restart the daemon:

sudo systemctl restart uxtu4linux.service

App shows duplicate banners or garbled output

This can happen if the terminal emulator does not support ANSI escape sequences properly, or if the terminal window is very narrow.

  • Make sure your terminal is at least 80 columns wide.
  • Try a different terminal emulator (e.g. GNOME Terminal, Kitty, Alacritty).