Video Issue After Hibernation in Bazzite Linux (llvmpipe identified instead of GPU)

Hello guys! I'm having a persistent video rendering issue with my system after it went into hibernation. Before hibernation, everything was working perfectly. My GPU is a AMD Radeon RX 5700 XT The Problem: Since the system resumed from hibernation, I'm experiencing visual corruption/artifacts on the screen. I've noticed two main things: The boot logs and dmesg show an error message related to the GPU during startup.
[ 6.896273] [drm] amdgpu kernel modesetting enabled.
[ 6.896497] amdgpu: Virtual CRAT table created for CPU
[ 6.896509] amdgpu: Topology: Add CPU node
[ 6.896820] [drm] initializing kernel modesetting (NAVI10 0x1002:0x731F 0x1002:0x0000 0xC1).
[ 6.896838] [drm] register mmio base: 0xFBB00000
[ 6.896841] [drm] register mmio size: 524288
[ 6.900171] amdgpu 0000:05:00.0: amdgpu: invalid ip discovery binary checksum
[ 6.900176] amdgpu 0000:05:00.0: amdgpu: [drm] *ERROR* discovery failed: -22
[ 6.900178] amdgpu 0000:05:00.0: amdgpu: Fatal error during GPU init
[ 6.900179] amdgpu 0000:05:00.0: amdgpu: amdgpu: finishing device.
[ 6.900229] amdgpu 0000:05:00.0: probe with driver amdgpu failed with error -22
[ 6.896273] [drm] amdgpu kernel modesetting enabled.
[ 6.896497] amdgpu: Virtual CRAT table created for CPU
[ 6.896509] amdgpu: Topology: Add CPU node
[ 6.896820] [drm] initializing kernel modesetting (NAVI10 0x1002:0x731F 0x1002:0x0000 0xC1).
[ 6.896838] [drm] register mmio base: 0xFBB00000
[ 6.896841] [drm] register mmio size: 524288
[ 6.900171] amdgpu 0000:05:00.0: amdgpu: invalid ip discovery binary checksum
[ 6.900176] amdgpu 0000:05:00.0: amdgpu: [drm] *ERROR* discovery failed: -22
[ 6.900178] amdgpu 0000:05:00.0: amdgpu: Fatal error during GPU init
[ 6.900179] amdgpu 0000:05:00.0: amdgpu: amdgpu: finishing device.
[ 6.900229] amdgpu 0000:05:00.0: probe with driver amdgpu failed with error -22
I suspect the hibernation/suspend process may have somehow corrupted the driver state or configuration. I've attached both the dmesg output and the logs from the last boot to this post. Has anyone encountered this specific issue on Bazzite or with an AMD GPU after hibernation? Any guidance on how to force the system to recognize and use the correct vulkan-mesa driver, or what the error message in the logs might indicate, would be greatly appreciated! Thanks in advance for your help!
3 Replies
santoscigor
santoscigorOP2mo ago
I have updates, today I just rebooted the PC, and the video display was OK, without artifacts/corruption. I did not change anything at all, but this time at startup the dmesg and startup logs shows no problems and when I check the "About" in the system it shows my graphic card instead of llvmpipe, like this:
Operating System: Bazzite 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-108.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Xeon® CPU E5-2680 v4 @ 2.40GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: INTEL
Operating System: Bazzite 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-108.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Xeon® CPU E5-2680 v4 @ 2.40GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: INTEL
Here are the logs of this new boot to compare
Peteydog
Peteydog2mo ago
hi, i haven't grabbed logs of this issue just yet, but it seems i'm encountering a similar, if not the same issue Operating System: Bazzite 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.4-115.bazzite.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900 12-Core Processor Memory: 32 GiB of RAM (30.9 GiB usable) Graphics Processor: Intel® Arc Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E26 System Version: 1.0
santoscigor
santoscigorOP3w ago
I found where the problem was. It was a GPU Card issue. The 5700XT vram were with a problem that caused the issue. The problem was resolved by switching the GPU Card

Did you find this page helpful?