Looks like I’m not the only one but I having a issue with the “latest” kernel.
Since kernel 7.2 got available, I’m having the same problem. After an update and reboot I only got black screen. I can use different TTY-s to rollback the update, but nothing else. I tried 7.2.4 -.5 -.6 -.7 with the same result.
Is 7.2.x is doomed and I should wait till 7.3?
Any body has an idea what could be the problem?
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.1.10-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 6800
Manufacturer: ASUS
Is this “drm” errors from the start up logs (journalctl -k -b)? Because I don’t have any of the errors on start up like others.
I lokked up the logs with the other way.
sudo dmesg -t -H | grep amd > 727dr.txt
And everyting seems okay.
amd_uncore: 4 amd_df counters detected
amd_uncore: 6 amd_l3 counters detected
perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
x86/amd: Previous system reset reason [0x00080800]: software wrote 0x6 to reset control register 0xCF9
amdgpu: Virtual CRAT table created for CPU
amdgpu: Topology: Add CPU node
amdgpu 0000:0d:00.0: enabling device (0006 → 0007)
amdgpu 0000:0d:00.0: initializing kernel modesetting (SIENNA_CICHLID 0x1002:0x73BF 0x1EAE:0x6705 0xC3).
amdgpu 0000:0d:00.0: register mmio base: 0xFCC00000
amdgpu 0000:0d:00.0: register mmio size: 1048576
amdgpu 0000:0d:00.0: detected ip block number 0 <common_v1_0_0> (nv_common)
amdgpu 0000:0d:00.0: detected ip block number 1 <gmc_v10_0_0> (gmc_v10_0)
amdgpu 0000:0d:00.0: detected ip block number 2 <ih_v5_0_0> (navi10_ih)
amdgpu 0000:0d:00.0: detected ip block number 3 <psp_v11_0_0> (psp)
amdgpu 0000:0d:00.0: detected ip block number 4 <smu_v11_0_0> (smu)
amdgpu 0000:0d:00.0: detected ip block number 5 <dce_v1_0_0> (dm)
amdgpu 0000:0d:00.0: detected ip block number 6 <gfx_v10_0_0> (gfx_v10_0)
amdgpu 0000:0d:00.0: detected ip block number 7 <sdma_v5_2_0> (sdma_v5_2)
amdgpu 0000:0d:00.0: detected ip block number 8 <vcn_v3_0_0> (vcn_v3_0)
amdgpu 0000:0d:00.0: detected ip block number 9 <jpeg_v3_0_0> (jpeg_v3_0)
amdgpu 0000:0d:00.0: Fetched VBIOS from VFCT
amdgpu 0000:0d:00.0: [drm] ATOM BIOS: 113-1MS21XL203W_210810, build: 596865 , ver: 020.001.000.071.000000, 2021/12/17
amdgpu 0000:0d:00.0: vgaarb: deactivate vga console
amdgpu 0000:0d:00.0: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
amdgpu 0000:0d:00.0: MEM ECC is not presented.
amdgpu 0000:0d:00.0: SRAM ECC is not presented.
amdgpu 0000:0d:00.0: vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
amdgpu 0000:0d:00.0: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
amdgpu 0000:0d:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
amdgpu 0000:0d:00.0: [drm] Detected VRAM RAM=16368M, BAR=16384M
amdgpu 0000:0d:00.0: [drm] RAM width 256bits GDDR6
amdgpu 0000:0d:00.0: 16368M of VRAM memory ready
amdgpu 0000:0d:00.0: 15994M of GTT memory ready.
amdgpu 0000:0d:00.0: [drm] GART: num cpu pages 131072, num gpu pages 131072
amdgpu 0000:0d:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000083FEB00000).
amdgpu 0000:0d:00.0: STB initialized to 2048 entries
amdgpu 0000:0d:00.0: [drm] Loading DMUB firmware via PSP: version=0x02020022
amdgpu 0000:0d:00.0: [drm] use_doorbell being set to: [true]
amdgpu 0000:0d:00.0: [drm] use_doorbell being set to: [true]
amdgpu 0000:0d:00.0: [drm] use_doorbell being set to: [true]
amdgpu 0000:0d:00.0: [drm] use_doorbell being set to: [true]
amdgpu 0000:0d:00.0: [VCN instance 0] Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 14
amdgpu 0000:0d:00.0: [VCN instance 1] Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 14
amdgpu 0000:0d:00.0: reserve 0xa00000 from 0x83fd000000 for PSP TMR
amdgpu 0000:0d:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
amdgpu 0000:0d:00.0: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, smu fw version = 0x003a5b00 (58.91.0)
amdgpu 0000:0d:00.0: use vbios provided pptable
amdgpu 0000:0d:00.0: SMU is initialized successfully!
amdgpu 0000:0d:00.0: [drm] Display Core v3.2.384 initialized on DCN 3.0
amdgpu 0000:0d:00.0: [drm] DP-HDMI FRL PCON supported
amdgpu 0000:0d:00.0: [drm] DMUB hardware initialized: version=0x02020022
amdgpu 0000:0d:00.0: kiq ring mec 2 pipe 1 q 0
amdgpu: Virtual CRAT table created for GPU
amdgpu: Topology: Add GPU node [0x1002:0x73bf]
amdgpu 0000:0d:00.0: SE 4, SH per SE 2, CU per SH 10, active_cu_number 60
amdgpu 0000:0d:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
amdgpu 0000:0d:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.1.0 uses VM inv eng 5 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
amdgpu 0000:0d:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
amdgpu 0000:0d:00.0: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
amdgpu 0000:0d:00.0: ring sdma0 uses VM inv eng 13 on hub 0
amdgpu 0000:0d:00.0: ring sdma1 uses VM inv eng 14 on hub 0
amdgpu 0000:0d:00.0: ring sdma2 uses VM inv eng 15 on hub 0
amdgpu 0000:0d:00.0: ring sdma3 uses VM inv eng 16 on hub 0
amdgpu 0000:0d:00.0: ring vcn_dec_0 uses VM inv eng 0 on hub 8
amdgpu 0000:0d:00.0: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
amdgpu 0000:0d:00.0: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
amdgpu 0000:0d:00.0: ring vcn_dec_1 uses VM inv eng 5 on hub 8
amdgpu 0000:0d:00.0: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
amdgpu 0000:0d:00.0: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
amdgpu 0000:0d:00.0: ring jpeg_dec uses VM inv eng 8 on hub 8
amdgpu: HMM registered 16368MB device memory
amdgpu 0000:0d:00.0: Using BACO for runtime pm
amdgpu 0000:0d:00.0: [drm] Registered 6 planes with drm panic
[drm] Initialized amdgpu 3.64.0 for 0000:0d:00.0 on minor 1
fbcon: amdgpudrmfb (fb0) is primary device
amdgpu 0000:0d:00.0: [drm] fb0: amdgpudrmfb frame buffer device
kvm_amd: TSC scaling supported
kvm_amd: Nested Virtualization enabled
kvm_amd: Nested Paging enabled
kvm_amd: LBR virtualization supported
kvm_amd: Virtual VMLOAD VMSAVE supported
kvm_amd: Virtual GIF supported
snd_hda_intel 0000:0d:00.1: bound 0000:0d:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
amd_atl: AMD Address Translation Library initialized
I been trough some of the topic to try to find some solution.
I found that topic:
I beleve so Chris had some solution but it didn’t worked for me.
PS: I’m sorry if I wrote something bad or stupid. I’m still new in “linux”. I only swiched 1 and a half year ago.
it’s really sad, I reported this bug already early June ( Warning: new kernel 7.2.* breaks certain AMD GPU support ) - but they only laugthed at me that “rawhide” bugs will never make it into a release, now here we are, I knew it would happen, pitty that testers are ignored
I saw your topic as well. Basically your post give me some “hope”, because it’s easier to skip the current 7.2.* kernel.
What’s your experience with the 7.3? Do you have to tweak something besides the different kernel?
Otherwise, if you believe it is a kernel 7.2 problem and you are brave enough to test the 7.3.0.rc4, you could try to install it for science… sudo dnf upgrade kernel --releasever=46
If you end up testing it, you can leave your feedback on the build here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7e4f109c7d
Yes I tried that firmware reinstall/refresh on 7.2.4 and .5 without successes.
Somebody mentioned the firmware downgrade, but it’s looks a bigger hassle to do and maintain it. dnf upgrade --exclude=kernel* or dnf history rollback much easier and faster to keep up with the rest of the updates.
In the other hand 7.3 looks more appealing. I will try out and comeback with the result.
I tried the 7.3 ass well. Look good to me. I have to roll back to 7.1 and skip 7.2 till 7.3 get stable. Seems like my controller not work at the current stage of the new kernel.
