Frozen screen on startup AMD 890M kernel 7.2.x

Ask Fedora
, , ,
1

First, I want to say I’m new to Linux on desktop/laptops, so I don’t have much experience. And sorry for the previous topic sent half written…

I installed Fedora on a Asus Zenbook S16 a few days ago using the official Fedora Media Writer.
The first time I booted on Fedora, it was version 6.19.10-300 of the Linux kernel. Other than the laptop’s speakers not being detected, everything seems to work fine out of the box.

But there was a lot of updates to do (more than 1000), so… I did the updates. Kernet updated to 7.2.5… and I wasn’t able to log in, the screen was completely frozen.
I since made multiple other updates, and the boot screen is listing kernel 6.19.10 7.2.6 and 7.2.7. Only 6.19.10 works, the two other have the same issue as 7.2.5 did.

Since I have an AMD CUP and GPU, and considering the recent bugs I read about here and on reddit, I suspect this is what’s causing it. But I also read fixes had been implemented in the newest kernel versions, so I’m a little lost on why it’s still broken.

Is it a separate issue? Or do I need to do something more to apply the fix?

This is what fastfetch shows for my system:
OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64
Host: Zenbook S16 UM5606GA (1.0)
Kernel: Linux 6.19.10-300.fc44.x86_64
Uptime: 21 mins
Packages: 28 (flatpak), 2677 (rpm), 10 (snap)
Shell: bash 5.3.9
Display (SDC422C): 2880x1800 @ 1.7x in 16", 120 Hz [Built-in]
Desktop Environment: KDE Plasma 6.7.5
Window Manager: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Light) [Qt], Breeze [GTK2/3]
Icons: breeze [Qt], breeze [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (24px)
Terminal: konsole 26.8.1
CPU: AMD Ryzen AI 9 465 (20) @ 2.00 GHz
GPU: AMD Radeon 890M Graphics [Integrated]
Memory: 4.91 GiB / 30.48 GiB (16%)
Swap: 0 B / 8.00 GiB (0%)
Disk (/): 193.91 GiB / 691.94 GiB (28%) - btrfs
Local IP (wlp195s0): 192.168.1.34/24
Battery (ASUS Battery): 100% [AC Connected]
Locale: fr_FR.UTF-8

2

either it’s a regression in the 7.2.x kernels or the recent firmware updates introduced issues with the Radeon 890M IGPU.

you can inspect the journal for hints what went wrong
let’s say the previous boot attempt was with kernel 7.2.x, then you can access the journal with

journalctl -b -1

-1 = previous boot
-2 = the boot before that etc.

option -p 3 filters the output to errors+ only
option -p 4 filters warnings and errors..

screen frozen: was anything shown on the screen or was it black?

have you trried switching to a VT with Ctrl-Alt-F4 ?

3

It’s not a black screen, I can see Fedora’s login screen but it’s frozen. I can’t move the cursor, I can’t see myself type anything to log in, etc. Sometimes the login screen is smaller than it should be and framed by black bars (I guess because it frozes before the animation ends).
At one point I was able to log in but not to see it (I could hear the ‘log in sound’ when typing my password and pressing enter), it probably was with 7.2.5 but I’m not sure.

I hadn’t tried ctrl+alt+f4, so I did now but it didn’t do anything. The screen was still frozen so I couldn’t see if it worked. I don’t think it’s a manipulation error on my part because I tried on 6.19.10 and it worked.

These are the errors logged when I try to boot on 7.2.7:

$ journalctl -b -1 -p 3
sept. 23 20:00:04 Fedora kernel: virt/tdx: TDX not supported by the host platform
sept. 23 20:00:04 Fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._S0W], AE_ALREADY_EXISTS (20260408/dswload2-326)
sept. 23 20:00:04 Fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20260408/psobject-220)
sept. 23 20:00:04 Fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR0], AE_ALREADY_EXISTS (20260408/dswload2-326)
sept. 23 20:00:04 Fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20260408/psobject-220)
sept. 23 20:00:04 Fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR3], AE_ALREADY_EXISTS (20260408/dswload2-326)
sept. 23 20:00:04 Fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20260408/psobject-220)
sept. 23 20:00:04 Fedora kernel: platform MSFT0201:00: AMD-Vi: [Firmware Bug]: No ACPI device matched UID, but 1 device matched HID.
sept. 23 20:00:05 Fedora kernel: hid-multitouch 0018:2808:0219.0002: Returned feature report did not match the request
sept. 23 20:00:05 Fedora kernel: amdtee: failed to load firmware /amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin
sept. 23 20:00:05 Fedora kernel: amdtee: failed to copy TA binary
sept. 23 20:00:05 Fedora kernel: Failed to open TEE session err:0x0, rc:-12
sept. 23 20:00:05 Fedora kernel: amd-pmf AMDI0108:00: Failed to open TA session (-12)
sept. 23 18:00:12 Fedora bluetoothd[1042]: Failed to set mode: Failed (0x03)

There are also errors when booting on 6.1.19 apparently:

$ journalctl -b -p 3
sept. 23 20:01:52 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._S0W], AE_ALREADY_EXISTS (20250807/dswload2-326)
sept. 23 20:01:52 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
sept. 23 20:01:52 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR0], AE_ALREADY_EXISTS (20250807/dswload2-326)
sept. 23 20:01:52 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
sept. 23 20:01:52 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR3], AE_ALREADY_EXISTS (20250807/dswload2-326)
sept. 23 20:01:52 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
sept. 23 20:01:52 fedora kernel: platform MSFT0201:00: AMD-Vi: [Firmware Bug]: No ACPI device matched UID, but 1 device matched HID.
sept. 23 20:01:52 fedora systemd-tmpfiles[436]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:2: Failed to resolve user 'tss': Unknown user
sept. 23 20:01:52 fedora systemd-tmpfiles[436]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:4: Failed to resolve user 'tss': Unknown user
sept. 23 20:01:52 fedora systemd-tmpfiles[436]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:6: Failed to resolve group 'tss': Unknown group
sept. 23 20:01:52 fedora systemd-tmpfiles[436]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:7: Failed to resolve group 'tss': Unknown group
sept. 23 20:01:52 fedora systemd-udevd[517]: /usr/lib/udev/rules.d/60-tpm-udev.rules:3 Failed to resolve user 'tss', ignoring: Unknown user
sept. 23 20:01:52 fedora systemd-udevd[517]: /usr/lib/udev/rules.d/60-tpm-udev.rules:4 Failed to resolve group 'tss', ignoring: Unknown group
sept. 23 20:01:55 fedora kernel: [drm:drm_mode_config_cleanup] *ERROR* connector Unknown-1 leaked!
sept. 23 18:01:58 Fedora kernel: platform acp_asoc_acp70.0: warning: No matching ASoC machine driver found
sept. 23 18:01:59 Fedora bluetoothd[1292]: Failed to set mode: Failed (0x03)
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error(s) opening ddc devices
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-4
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-5
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-6
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-7
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-8
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-9
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-10
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-11
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-12
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-13
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-14
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-15
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-16
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-17
sept. 23 18:02:11 Fedora org_kde_powerdevil[2569]: [  2569] Error EACCES(-13): Permission non accordée opening /dev/i2c-18
sept. 23 18:02:12 Fedora bluetoothd[1292]: Failed to set mode: Failed (0x03)

(“Permission non accordée” means “permission not granted”)

[edit] and thanks for the answer

4

this failed to load some firmware. amdtee is AMD’s version of trusted Execution Env
not sure if it’s related to the issue, maybe.

Do you see something amdtee related in the current boot log for kernel 6.19?
journalctl -b -k -g amdtee

5

There isn’t anything related to amdtee on 6.19.10, journalctl -b -k -g amdtee returns no entries

6

I checked on my F45 system, and this file do exist and is installed by the package amd-ucode-firmware…

$  rpm -qf /lib/firmware/amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin.xz
amd-ucode-firmware-20260916-1.fc45.noarch

check if this file exist on your system, also check with rpm -qa amd-ucode-firmware .
If it’s not installed, then install it please and then run

sudo dracut --kver 7.2.7-200.fc44.x86_64 --force

and try booting kernel 7.2.7 please.

update: what does this command report on kernel 6.19?

modinfo -F firmware amdtee

and compare it with

modinfo -F firmware amdtee -k 7.2.7-200.fc44.x86_64
7

So, amd-ucode-firmware-20260916-1.fc44.noarch is already installed. Booting on 7.2.7 doesn’t result in anything different (which I guess is expected).

$ rpm -qf /lib/firmware/amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin.xz 
amd-ucode-firmware-20260916-1.fc44.noarch 
$ rpm -qa amd-ucode-firmware 
amd-ucode-firmware-20260916-1.fc44.noarch

But the two modinfo commands don’t return anything.

8

I expected that maybe the 6.19 module would print the firmware filename.
That would mean that the firmware is not part of the initramfs…

pls lookup the journal for the last boot attempt with 7.2.7 and instead of -p 3 use option -k

set X to access journal for the last 7.2.7 kernel boot attempt

journalctl -b -X  -k --no-hostname --no-pager  | fpaste

and post the URL link please.

then let’s verify some things

rpm -V amd-ucode-firmware
sudo lsinitrd  -k 7.2.7-200.fc44.x86_64  |grep amdtee 
sudo lsinitrd   |grep amdtee
9

here it is: UNTITLED - Pastebin Service

And this is the output:

$ rpm -V amd-ucode-firmware 
sudo lsinitrd  -k 7.2.7-200.fc44.x86_64  |grep amdtee  
sudo lsinitrd   |grep amdtee
drwxr-xr-x   2 root     root            0 Sep  4 02:00 usr/lib/modules/7.2.7-200.fc44.x86_64/kernel/drivers/tee/**amdtee** 
-rw-r--r--   1 root     root        16180 Sep  4 02:00 usr/lib/modules/7.2.7-200.fc44.x86_64/kernel/drivers/tee/**amdtee**/**amdtee**.ko.xz
10

pls do the same for the kernel 6.19

journalctl -b -k --no-hostname |fpaste

no output for lsinitrd |grep amdtee ?
let’s try

sudo lsinitrd -k 6.19.10-300.fc44.x86_64 | grep    '/amd'
11

Yes, no output…

There is definitely an output now. Very long.

12

dracut adds the amdtee driver to the initramfs but not the firmware.

we could either install the missing firmware or omit the driver from the initramfs.

let’s try

– add firmware to initramfs

sudo dracut  --install '/usr/lib/firmware/amdtee/*' \
   --kver 7.2.7-200.fc44.x86_64 --force

and try booting the kernel. Check journalctl -b [-1] -g amdtee whether the firmware was loaded successfully

– omit the amdtee driver, module will be probed later during boot when the root fs is mounted.

sudo dracut --omit-drivers amdtee  --kver 7.2.7-200.fc44.x86_64  --force

check again with journalctl -b [-1] -g amdtee

try both variants please.

Still I have no idea if this is the source of the issue you’re seeing with the 7.2.x kernels.

14

I tried both options, and each time there is no improvement when booting and afterward on kernel 6.19.10 journalctl -b -1 -g amdtee doesn’t return anything at all. No trace of amdtee in the log. So I guess it’s not the thing causing the freeze?

15

yep, there was a slim chance though :slight_smile:

have you tried setting the display to 60Hz?

16

Yes I did. It doesn’t change anything so I put it back to 120Hz.

It really seems to be ‘just’ the screen freezing, because I tried again to log in 7.2.7 and I heard the login sound again, and I could shutdown it too.

That wouldn’t really be adressing the issue, but is it possible that a fresh install fix it?

17

Could you pls upload the journal for your last attempt with 7.2.x with the option -p 4
journalctl -b -X -p4 --no-hostname | fpaste

A reinstall wouldn’t change anything. It’s either a kernel regression or an issue with the current amdgpu firmware.

Then let’s see if it’s the firmware. You can downgrade the firmware to the version at initial release. Please review the transaction preview, only firmware packages should be altered.

sudo dnf downgrade linux-firmware --repo fedora --allowerasing

then regenerate the initramfs for kernel 7.2.7, this will add the downgraded firmware files to the initramfs

sudo dracut --omit-drivers amdtee  --kver 7.2.7-200.fc44.x86_64  --force

restart.

If it didn’t change anything revert with

run sudo dnf upgrade linux-firmware
18

I guess you need to manually add the file.

Check if the file already exist in your system or not, and if it is installed in your initramfs or not.

19

It’s my last attempt. Booted on kernel 7.2.7, logged in using the keyboard while the screen was frozen, and used the keyboard to open konsole and shutdown the linux while the screen was still frozen.
Another thing I noted is that after logging in, if I close the laptop the screen goes to sleep correctly, and when I reopen it… the screen freezes again on the login screen.

I tried to downgrade like you suggested (it was indeed only altering firmwares), but it didn’t change the outcome when booting on 7.2.7.

I don’t want to drag this more as just I asked the SAV for returning it (for reasons not related to Linux). Anyway, thank you for the help. I have a few things to learn on the subject now.

20

It you still have access to the system, could you please try a 7.3RC kernel from rawhide?
That would give us some info whether there might be a fix ported back to a 7.2.x. kernel.

this will probably need the latest firmware versions.

sudo dnf up linux-firmware
sudo dnf up kernel kernel-modules-extra --releasever 46

to remove the 7.3 kernel, boot another kernel and then

sudo dnf remove 'kernel*7.3.0*'
21

Hi, I also got Asus zenbook S16, processor AMD Ryzen™ AI 7 445 w/ Radeon™ 840M × 12 and I’m experiencing same issue after upgrade to kernel 7.2.7.

Kernel 7.3-rc4 didn’t help.