Created attachment 1914955 [details] Xorg.0.log + journal Original Summary: [DRI] radeon 0000:04:00.0: Direct firmware load for radeon/RV610_pfp.bin failed with error -2 Actual behavior: 1-$SUMMARY 2-KMS fails for RV610 [Radeon HD 2400 PRO] chip-ID: 1002:94c3 2-KMS fails for RV620 PRO [Radeon HD 3470] chip-ID: 1002:95c0 3-(EE) open /dev/dri/card0: No such file or directory 4-vttys black screen 5-Xorg runs on VESA display driver in 1400x1050 resolution 6-r600_cp: Failed to load firmware "radeon/RV610_pfp.bin" [drm:r600_init [radeon]] *ERROR* Failed to load firmware! Expected behavior: 1-radeon firmware loads 2-KMS loads for RV610 [Radeon HD 2400 PRO] chip-ID: 1002:94c3 2-KMS loads for RV620 PRO [Radeon HD 3470] chip-ID: 1002:95c0 3-/dev/dri/card0 exists 4-vttys run normally 5-Xorg runs on modesetting display driver in display's native 1920x1200 resolution 2. What is the Version-Release number of the kernel: 5.17.14-300.fc36 with HD2400 PC/F36 5.18.19-200.fc36 with HD2400 PC/F36 5.19.11-200.fc36 with HD2400 PC/F36 5.19.11-300.fc37 with HD3470 PC/F37 6.0.0-0.rc7.20220927gita1375562c0a8.48.fc38 with HD2400 PC/F36 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 5.17.14 kernel worked after last upgrading 28 June on F36 on the HD2400 PC before today's upgrade, when I installed 5.18.19 and 5.19.11. Now same failure with 5.17.14, 5.18.19 & 5.19.11. On the HD3470 PC the F36 upgrade was last a month ago with 5.18.19 and now works as expected with 5.19.11. However the F37 upgrade from a month ago working with 5.19.0 on same HD3470 fails in same manner as the HD2400 with 5.19.0 and 5.19.11. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: They're test installations, so I didn't back up before the upgrades. I did try removing the freshly installed 5.19.11 on the HD2400 and reinstalled after rebooting, but same errant behavior persisted. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No From HD2400/F36 PC: # rpm -qa | grep mesa-dri mesa-dri-drivers-22.1.7-1.fc36.x86_64 Note-if the vttys weren't black, I would have thought this a Mesa problem. Using nomodeset makes the vttys work, but Xorg is unhappy without KMS: (EE) Unable to find a valid framebuffer device (EE) Screen 1 deleted because of no matching config section. (EE) modeset(0): glamor initialization failed modeset(0): Refusing to try glamor on llvmpipe vesa: Refusing to run, Framebuffer or dri device present (II) modeset(0): Output None-1 using initial mode 1024x768 +0+0
Seems like almost same problem now on a much newer and different PC, but also amd/ati graphics: [ 0.053171] Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume audit=0 ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1440x900@60 5 [ 0.342715] amd_uncore: 4 amd_nb counters detected [ 0.343366] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). [ 4.716984] [drm] amdgpu kernel modesetting enabled. [ 4.723866] amdgpu: Topology: Add APU node [0x0:0x0] [ 4.730960] amdgpu 0000:00:01.0: vgaarb: deactivate vga console [ 4.731247] amdgpu 0000:00:01.0: amdgpu: Fetched VBIOS from VFCT [ 4.731251] amdgpu: ATOM BIOS: 113-SPEC-102 [ 4.731266] amdgpu 0000:00:01.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 4.731478] amdgpu 0000:00:01.0: amdgpu: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used) [ 4.731481] amdgpu 0000:00:01.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 4.731528] [drm] amdgpu: 1024M of VRAM memory ready [ 4.731529] [drm] amdgpu: 3436M of GTT memory ready. [ 4.731821] amdgpu 0000:00:01.0: Direct firmware load for amdgpu/kaveri_pfp.bin failed with error -2 [ 4.731825] amdgpu: gfx7: Failed to load firmware "amdgpu/kaveri_pfp.bin" [ 4.731826] [drm:gfx_v7_0_sw_init.cold [amdgpu]] *ERROR* Failed to load gfx firmware! [ 4.732154] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <gfx_v7_0> failed -2 [ 4.732412] amdgpu 0000:00:01.0: amdgpu: amdgpu_device_ip_init failed [ 4.732414] amdgpu 0000:00:01.0: amdgpu: Fatal error during GPU init [ 4.732417] amdgpu 0000:00:01.0: amdgpu: amdgpu: finishing device. [ 4.732565] amdgpu: probe of 0000:00:01.0 failed with error -2 [ 4.732608] [drm] amdgpu: ttm finalized # rpm -qa | egrep 'mwar|nel-cor' kernel-core-5.18.19-200.fc36.x86_64 kernel-core-5.19.17-200.fc36.x86_64 kernel-core-5.19.16-200.fc36.x86_64 amd-gpu-firmware-20221012-141.fc36.noarch linux-firmware-20221012-141.fc36.noarch linux-firmware-whence-20221012-141.fc36.noarch # inxi -Gxx Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: N/A arch: GCN-2 bus-ID: 00:01.0 chip-ID: 1002:130f With the two newer kernels, only remote login is possible, as on host directly there is only black screen with no keyboard response.
Recent updates on all 3 PCs on F36 & F37 have eliminated this failure.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.