I’ve been using my system and suddenly it froze (might be because I’ve inserted a usb stick). After 2-3 minutes I did forced shut down and after that Fedora never booted again no matter what kernel version I use. If I change rghb quiet to nomodeset it works. I’ve been “debugging” the problem with LLM, but it’s just a crappy way and it didn’t solve anything.
dmesg | grep -Ei “amdgpu|gpu|drm|fw” showed “probe with driver amdgpu failed with error -22”.
I’ve tried restoring an older snapshot, upgrading my system, force restoring dracut, reinstalling all the mesa and linux-firmware packages and it just doesn’t work.
My specs are: Ryzen 5 3600, RX570, DDR4 2400Mhz 8x2, ASrock A320.
I would really appreciate any help, as a beginner I have no clue how to debug and fix it.
I hope those inputs may lead into something:
dmesg | grep -i "failed to"
0.424226] amd_pstate: Failed to initialize CPU 0: -22
[ 0.426225] amd_pstate: Failed to initialize CPU 1: -22
[ 0.428223] amd_pstate: Failed to initialize CPU 2: -22
[ 0.430229] amd_pstate: Failed to initialize CPU 3: -22
[ 0.432224] amd_pstate: Failed to initialize CPU 4: -22
[ 0.434229] amd_pstate: Failed to initialize CPU 5: -22
[ 0.436224] amd_pstate: Failed to initialize CPU 6: -22
[ 0.438228] amd_pstate: Failed to initialize CPU 7: -22
[ 0.440224] amd_pstate: Failed to initialize CPU 8: -22
[ 0.442230] amd_pstate: Failed to initialize CPU 9: -22
[ 0.444224] amd_pstate: Failed to initialize CPU 10: -22
[ 0.446230] amd_pstate: Failed to initialize CPU 11: -22
[ 0.446241] amd_pstate: failed to register with return -19
[ 7.588119] asus_wmi: failed to register LPS0 sleep handler in asus-wmi
sudo dmesg | grep -i firmware
[ 0.000232] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 0.191790] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.237516] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf8000000-0xfbffffff] for domain 0000 [bus 00-3f] only partially covers this bridge
[ 6.087693] SELinux: Permission firmware_load in class system not defined in policy.
[ 6.968131] systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[ 6.968491] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
OK - so you have a system which boots ok if you specify nomodeset on the kernel parameter, but fails if you just allow it to try to boot normally.
- Restart your machine, but within grub remove
rhgbandquietso that you get all the boot messages on screen. Let it sit there for 10 minutes (this is just to let things run to the point where if they were ever going to complete, they will probably have done so.) - Press Ctrl+Alt+F5 - if you get a TTY, login in and issue the
shutdowncommand. - This time boot the machine by adding in your
nomodesetparameter. Hopefully this fires you up to a graphical desktop, just to make things easier for you. - Open a terminal, and issue the command
journalctl --no-hostname --no-pager -b -1 | fpaste. the-b -1part indicates we want to look at the log from the previous boot - the one you just made demonstrating the issue. - Post the URL it gives you here - ideally you’d upload the entire journal here, but it will be too large so sticking it into a pastebin is the next best option and I can cut and paste the relevant bits in here for posterity when we work out what the issue is.
- Post the output from
inxi -Fzxxhere too. Shows us your hardware, verisions, which driver is loaded and so on.
- It resulted into another error, if I boot without rghb quiet it displays: “amd_pstate: failed to register with return -19” at the start of booting. All the other services are with green OK.
- Nothing happened after those first 10 seconds of error and services booting, I waited around 10 minutes and turned it off through button, because no combination of ctrl+alt+F1-12 gave any result.
- This gets me into the system, yes.
4-5. UNTITLED - Pastebin Service (that’s what I got from terminal. The issue persist on any version of kernel, Fedora or Cachyos, older or newer. The newest one doesn’t work anymore because I’ve restored an old snapshot, but it’s not what is causing the boot issue I believe.
Couldrtc_cmos 00:02: RTC can wake from S4mean that the issue is coming from this freeze resulting into the system thinking it’s should hibernate itself? inxi -Fzxx System: Kernel: 6.18.4-cachyos1.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop Edition) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <superuser required> part-nu: SKU Firmware: UEFI vendor: American Megatrends v: 5603 date: 10/14/2020 CPU: Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB Speed (MHz): avg: 3600 min/max: 2200/4208 boost: enabled cores: 1: 3600 2: 3600 3: 3600 4: 3600 5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600 bogomips: 86244 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: N/A arch: GCN-4 pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.0 chip-ID: 1002:67df Device-2: Razer USA Kiyo X driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 1532:0e06 Display: wayland server: Xwayland v: 24.1.9 compositor: kwin_wayland driver: N/A display-ID: 0 Monitor-1: Unknown-1 res: 1024x768 hz: 60 dpi: 96 diag: 338mm (13.3") API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast wayland: drv: swrast x11: drv: swrast inactive: gbm API: OpenGL v: 4.5 vendor: mesa v: 25.2.7 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 21.1.5 256 bits) device-ID: ffffffff:ffffffff display-ID: :0.0 API: Vulkan v: 1.4.328 surfaces: N/A device: 0 type: cpu driver: mesa llvmpipe device-ID: 10005:0000 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: lact wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr Audio: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: XFX Pine driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 1002:aaf0 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487 Device-3: Razer USA Kiyo X driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 1532:0e06 Device-4: JMTek LLC. USB PnP Audio Device driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 3-4.4:5 chip-ID: 0c76:161e API: ALSA v: k6.18.4-cachyos1.fc43.x86_64 status: kernel-api Server-1: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-6:2 chip-ID: 2550:8761 Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10 Drives: Local Storage: total: 1.13 TiB used: 775.25 GiB (67.1%) ID-1: /dev/sda vendor: Geil model: ZENITH 240G R3 size: 223.57 GiB speed: 6.0 Gb/s serial: <filter> ID-2: /dev/sdb vendor: Toshiba model: HDWD110 size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> Partition: ID-1: / size: 219.64 GiB used: 210.14 GiB (95.7%) fs: btrfs dev: /dev/sda6 ID-2: /boot size: 1.9 GiB used: 909.9 MiB (46.8%) fs: ext4 dev: /dev/sda5 ID-3: /boot/efi size: 96 MiB used: 50.1 MiB (52.2%) fs: vfat dev: /dev/sda1 ID-4: /home size: 219.64 GiB used: 210.14 GiB (95.7%) fs: btrfs dev: /dev/sda6 Swap: ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 42.9 C mobo: N/A Fan Speeds (rpm): N/A Info: Memory: total: 16 GiB available: 15.54 GiB used: 3.97 GiB (25.5%) Processes: 409 Power: uptime: 6m wakeups: 0 Init: systemd v: 258 default: graphical Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 53 Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0 running-in: konsole inxi: 3.3.40
Triple backticks for preformatted text. When I read this, it appears like this, which is not easy to read:
`inxi -Fzxx System: Kernel: 6.18.4-cachyos1.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop Edition) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <superuser required> part-nu: SKU Firmware: UEFI vendor: American Megatrends v: 5603 date: 10/14/2020 CPU: Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB Speed (MHz):
[snip]
I see you are running a non-standard kernel, recompiled with unknown parameters. Do you also get this issue when you use a standard Fedora kernel?
Your BIOS is almost 6 years old now - might want to check for a newer version just to rule out the obvious. I say this because when this kernel is trying to set up power states on the CPU, the firmware report that either (or maybe all) of the values for this CPU are zero, which is invalid. At the end of trying all to set up each CPU on the die, they are all reported incorrectly by the BIOS and the entire thing gives up.
This is not the cause of your issue though - it’s a BIOS issue but its not fatal.
It’s the same story with your amdgpu -22 error message you refer to in the title; -22 is “invalid value”.
The next thing that SHOULD happen is the creation of a framebuffer to display the screen. When you use the nomodeset parameter, you’re telling the kernel - “don’t try to get the GPU to set up the screen - just keep using this low-res screen you already have”. Everything proceeds normally.
If you leave off that nomodeset parameter, the GPU is asked to create a framebuffer and in your case, it fails. You get a black screen forever as evidently something isn’t happy.
Try the following, in order of least hassle to most.
- Ensure the firmware is up-to-date;
sudo dnf reinstall linux-firmware - Try booting with
amdgpu.dc=0as a kernel parameter. Apparently, according to A Dummy's Guide to AMD GPU Issues on Linux - Understanding RDNA3, TLB Fences, and Kernel Parameters · GitHub, older amd GPU often had issues with display core. Turning it off can help, but I suspect you’ll lose some functionality if you need to do this, so if it makes no improvement, don’t continue to use it! - Test to see if this is a CachyOS introduced issue with your GPU model, which is a Polaris or Ellesmere device; install a standard kernel and not a tweaked and tuned CachyOS recompiled version - I have no idea what they do to this kernel and thus all bets are off if you use it.
Thanks, didn’t know it about triple backticks.
I’m pretty embarrassed to say that, but the Cachyos and Fedora kernels are both working (except of this 6.18.4)…
I sticked to the older one for the compatibility, and maybe this when I (or Fedora itself) fixed something…
I’m also pretty sure they have not worked, since I’ve tried each of them after my system couldn’t boot.
So yeah, I’m really grateful for the help, now I hope it doesn’t break again.
This is my journalctl from successful boot: UNTITLED - Pastebin Service
I’ve tried turning off/on FSS support in the bios, I’ve unplugged my PCU for some time, I’ve reinstalled all the mesa and linux-firmware packages in the nomodeset.
I have no idea what worked exactly. Is that Fedora just fixed itself or me…
1 Like