# Shutdown and Reboot issues on FW 13 (Ryzen AI 300) \[openSUSE Leap 16.0\]

**URL:** <https://community.frame.work/t/shutdown-and-reboot-issues-on-fw-13-ryzen-ai-300-opensuse-leap-16-0/84541>\
**Category:** Linux\
**Tags:** opensuse\
**Created:** [September 1, 2026, 2:54pm UTC](https://community.frame.work/t/shutdown-and-reboot-issues-on-fw-13-ryzen-ai-300-opensuse-leap-16-0/84541 "2026-09-01T14:54:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuele\_Batocchi](https://avatars.discourse-cdn.com/v4/letter/s/ce73a5/32.png) [@Samuele\_Batocchi](https://community.frame.work/u/Samuele_Batocchi)\
**Post date:** [September 1, 2026, 2:54pm UTC](https://community.frame.work/t/shutdown-and-reboot-issues-on-fw-13-ryzen-ai-300-opensuse-leap-16-0/84541/1 "2026-09-01T14:54:13Z")

</div>

**Hardware & OS Environment:**

- **Machine:** Framework Laptop 13 AMD Ryzen AI 5 340

- **OS:** openSUSE Leap 16.0 (KDE Plasma with Wayland)

- **Configuration:** Secureboot disabled

**Issue:**

When I perform a clean installation of openSUSE Leap 16.0, the laptop shuts down and reboots perfectly. Immediately after applying the initial system updates (via `zypper up` or “Update all” in the Discover GUI), the machine has issues with reboot and power off.

When initiating a shutdown or reboot, the screen goes black, but the keyboard remains backlit and the machine continues drawing power. It requires a hard reset via the physical power button every time.

**Troubleshooting already performed (failed):**  
I removed the `quiet` and `splash` kernel parameters to monitor the raw shutdown output. The logs confirm that this is not a hung application or a stalled `systemd` service. User-space termination is completely clean:

1. `systemd` successfully stops all services.

2. All filesystems, loop devices, and block devices are successfully unmounted and detached.

3. The absolute final message printed to the screen is: `systemd-shutdown[1]: Powering off.`

The deadlock occurs precisely at the `reboot(RB_POWER_OFF)` system call, where the updated kernel fails to execute the ACPI handoff to the motherboard to cut power.

- **Initramfs:** Rebuilt the initial RAM filesystem using `dracut -f --regenerate-all`.

- **ACPI Parameters:** Appended `acpi=force` to the GRUB boot line.

- **SELinux:** Placed SELinux into permissive mode (`enforcing=0`) to bypass a minor Plymouth AVC search denial observed in the shutdown logs.

- **Plymouth:** Completely disabled the splash daemon at the kernel level using `plymouth.enable=0`.

Are any other Ryzen AI 300 series users experiencing this regression on recent kernels, and are there any specific AMD scatter-gather or MediaTek driver workarounds recommended for this current build?

Thank you

---

<div class="post-metadata">

**Author:** ![Ahmed\_Al-Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@Ahmed\_Al-Ahmed](https://community.frame.work/u/Ahmed_Al-Ahmed)\
**Post date:** [September 3, 2026, 10:01pm UTC](https://community.frame.work/t/shutdown-and-reboot-issues-on-fw-13-ryzen-ai-300-opensuse-leap-16-0/84541/2 "2026-09-03T22:01:17Z")

</div>

I had exactly the same issue. I installed Kubuntu (Ubuntu + KDE Plasma + Wayland) lts 26.04 and 70% of the time my pc would not should down cleanly. What I found out is that some specific changes to amd drivers were introduced in kernel 6.19 and onwards and are now being rolled back or fixed in 7.x. 7.x is not mature enough yet, even worse on ubuntu which lags behind with the kernel version.

It just so happens that 6.18 is a kernel that is lts and still receives fixes from ubuntu, so I manually installed the 6.18.48 from the ubuntu mainline, which is very stable and works very well with the newest linux-firmware.

I don’t think a kernel parameter is enough to fix it. I tried everything.