Created attachment 1865565 [details] Kernel logs with amdgpu.dpm=0 (showing the bug) 1. Please describe the problem: I have a system with a Ryzen 5600G APU and a Vega 64 GPU. When the kernel parameter amdgpu.dpm=0 is used, the APU isn't initialized successfully, with a "smu firmware loading failed" error. The Vega 64 is initialized correctly. See "dmesg-bad.txt". The same system works fine without "admgpu.dpm=0". I will attempt to add a second attachment after filing with logs on a successful boot (Bugzilla doesn't seem to support more than one attachment at filing time?) 2. What is the Version-Release number of the kernel: Linux fedora 5.16.12-200.fc35.x86_64 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 : Unsure, just bought this APU. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes. I believe having a Ryzen 5600G APU is sufficient, but I haven't been able to test without the Vega 64. But anyway: try to boot with a 5600G + Vega 64, then "lspci -k" notice that the APU device has no "driver in use": 30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c9) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 1636 Kernel modules: amdgpu Alternatively, connect a display on the APU and attempt to use it. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I am running Silverblue and I'm not sure how to do this. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Done!
Created attachment 1865566 [details] Kernel logs WITHOUT amdgpu.dpm=0 (everything works fine, for comparison) Adding logs from a boot without "amdgpu.dpm=0": everything works fine in this case. (Side note: I am running with amdgpu.dpm=0 because I experience occasional hangs on my Vega 64 in graphically intensive games without it. It is hard to reliably reproduce, but if you want I can try to file that bug too. This thread by me has more details: https://ask.fedoraproject.org/t/gpu-hang-how-could-i-investigate-fix-this/20124/10?u=danutsu)
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 '35'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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.