How to install amd-debug-tools (needs systemd-devel) on Bazzite for kernel debugging?

Hardware: HP EliteBook X G1a, AMD Ryzen AI 9 HX 375 (Strix Point)

Problem:
The symptom is that the laptop cannot be woken up from suspend.
Debugged and found that the system hangs on suspend entry when amd_pmc driver is loaded.
Current workaround is to add kargs: initcall_blacklist=amd_pmc_driver_init

I then contacted amd_pc maintainer, who requested:
Install amd-debug-tools from PyPI to collect debug logs for upstream bug report.

Now is the real issue:
amd-debug-tools requires compiling systemd Python bindings, which needs systemd-devel package.

What I tried:

â rpm-ostree layer systemd-devel â System won't boot after reboot, had to rollback
â Distrobox with systemd-devel â Can install, but can't access /sys/kernel/debug or dmesg
â Pre-compile wheel in distrobox then install on host â Script hardcoded to compile csystemd dependency itself

Question:
What's the Bazzite-recommended way to:

Install debug tools that need compilation/system headers?
OR collect amd_pmc debug data for upstream kernel bug reports?

Would appreciate any guidance on the "right way" to do kernel-level debugging on Bazzite.

Orignal message received from AMD maintainer:

Hi,

Please use amd-s2idle from https://pypi.org/project/amd-debug-tools/ to
generate a report.  It may root cause it for you. If it doesn't, please
attach it to a bugzilla or drm/freedesktop bug report and CC me.

Hi,

Please use amd-s2idle from https://pypi.org/project/amd-debug-tools/ to
generate a report.  It may root cause it for you. If it doesn't, please
attach it to a bugzilla or drm/freedesktop bug report and CC me.

Hi,

Please use amd-s2idle from https://pypi.org/project/amd-debug-tools/ to
generate a report.  It may root cause it for you. If it doesn't, please
attach it to a bugzilla or drm/freedesktop bug report and CC me.

Hi,

Please use amd-s2idle from https://pypi.org/project/amd-debug-tools/ to
generate a report.  It may root cause it for you. If it doesn't, please
attach it to a bugzilla or drm/freedesktop bug report and CC me.

Solution

OK LMAO, I figured out a way.
turns out this

amd-debug-tool

amd-debug-tool

amd-debug-tool

amd-debug-tool is just a set of damn simple scripts calling journalctl and dmesg to collects logs. I just cloned the repo and directly calls these scripts, it is working perfectly.
https://github.com/superm1/amd-debug-tools/blob/master/src/launcher.py
We are so doomed. What kind of maintainer they have, bundling hard-coded gcc-12 compilation with systemd-headers when these are almost installed on every machine nowadays.:dispair:

GitHub

amd-debug-tools/src/launcher.py at master Â· superm1/amd-debug-tools

mirror of https://git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/ - superm1/amd-debug-tools

Jump to solution

LL1ttleFlyyy Hardware: HP EliteBook X G1a, AMD Ryzen AI 9 HX 375 (Strix Point) Problem: The ...

nagito || Knight of Emilia•12/8/25, 4:42 PM

looked up what that module is
seems to be the very thomg responsible for sleep

L1ttleFlyyyOP•12/8/25, 4:46 PM

Btw this is the original email I sent, and the log I've collected from dmesg:

Hello,

I'm reporting a critical suspend issue on HP EliteBook X G1a with AMD Ryzen
AI 9 HX 375 (Strix Point). The system completely hangs when entering s2idle
with the AMD PMC driver loaded.

Hardware:
- Model: HP EliteBook X G1a 14 inch (Model 8D08)
- CPU: AMD Ryzen AI 9 HX 375 (Strix Point)
- GPU: Radeon 890M (integrated)
- BIOS: X88 Ver. 01.03.11 (2025-09-03)

Kernel: 6.17.7-ba19.fc43.x86_64 (Fedora-based)
Current cmdline: bluetooth.disable_ertm=1 amdgpu.gpu_recovery=1 pcie_aspm=off

Problem:
When executing "systemctl suspend", the system enters s2idle but immediately
hangs. The last kernel message is "PM: suspend entry (s2idle)" with no
further output. System becomes completely unresponsive - keyboard, touchpad,
and power button (short press) have no effect. Only hard power-off works.

BIOS configuration:
- APMF enabled
- Modern Standby (s2idle only, S3 not supported by firmware)
- /sys/power/mem_sleep: [s2idle]

AMD PMC device present: /sys/bus/platform/devices/AMDI000A:00/

Workaround:
Adding "initcall_blacklist=amd_pmc_driver_init" to kernel cmdline prevents
the AMD PMC driver from loading. With this workaround, s2idle works perfectly
and the system resumes normally from suspend.

Logs attached:
1. system-info.txt - detailed system information
2. suspend-fail.log - Journal from failed suspend attempt (hangs after
"PM: suspend entry")
3. suspend-success.log - Journal from successful suspend/resume with
workaround applied

The failure log shows the system stops all output immediately after entering
s2idle, suggesting the AMD PMC driver causes a hard hang during early
platform suspend initialization.

Please let me know if you need any additional debug information or would like
me to test patches.

L1ttleFlyyyOP•12/8/25, 4:47 PM

and orginal logs. Apprently the AMD maintainer wants more log by using their amd-debug-tool python script

suspend-fail.log18.43KB

suspend-success.log34.41KB

system-info.txt1.54KB

LL1ttleFlyyy Btw this is the original email I sent, and the log I've collected from dmesg: >...

nagito || Knight of Emilia•12/8/25, 5:10 PM

you did try rootful distrobox
correct?

L1ttleFlyyyOP•12/8/25, 5:10 PM

yes, created with --privileged, still say no dmesg access

LL1ttleFlyyy yes, created with --privileged, still say no dmesg access

nagito || Knight of Emilia•12/8/25, 5:12 PM

homebrew can't install them either?

L1ttleFlyyyOP•12/8/25, 5:19 PM

I did use homebrew to install pipx. installation fails with pipx install amd-debug-tools because of the compilation issue I mentioned. You can easily reproduce by

brew install pipx
pipx install amd-debug-tools

brew install pipx
pipx install amd-debug-tools

I have to say this is a very terrible installation script from amd.
first thing you hit will be gcc-12gcc-12 not exist, which you can fix by linking /usr/bin/gcc to ~/.local/bin/gcc-12
next failure would be the cysystemd module compilation issue, which requires systemd-devel headers.

LL1ttleFlyyy I did use homebrew to install pipx. installation fails with pipx install amd-deb...

nagito || Knight of Emilia•12/8/25, 5:27 PM

what about doing this in a venv?
venvs are the recommended way nowadays anywoys?

nagito || Knight of Emilia•12/8/25, 5:29 PM

oh
these are just bindings so it'd probably still complain about needing the systemd deps

Solution

L1ttleFlyyy•12/8/25, 5:36 PM

OK LMAO, I figured out a way.
turns out this

amd-debug-tool

amd-debug-tool

is just a set of damn simple scripts calling journalctl and dmesg to collects logs. I just cloned the repo and directly calls these scripts, it is working perfectly.
https://github.com/superm1/amd-debug-tools/blob/master/src/launcher.py
We are so doomed. What kind of maintainer they have, bundling hard-coded gcc-12 compilation with systemd-headers when these are almost installed on every machine nowadays.:dispair:

GitHub

amd-debug-tools/src/launcher.py at master Â· superm1/amd-debug-tools

mirror of https://git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/ - superm1/amd-debug-tools

How to install amd-debug-tools (needs systemd-devel) on Bazzite for kernel debugging?

Similar Threads

Similar Threads

Similar Threads