Description of problem: With the latest kernel from updates testing (4.19.9-300), my computer boots but the screen stays black (no visible gdm). When I ssh in from another machine, gdm says it's running. In the journal I found this error message: Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: Direct firmware load for amdgpu/polaris11_k_mc.bin failed with error -2 Dec 16 11:12:36 zeratul kernel: mc: Failed to load firmware "amdgpu/polaris11_k_mc.bin" Dec 16 11:12:36 zeratul kernel: [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware! Dec 16 11:12:36 zeratul kernel: [drm:amdgpu_device_init.cold.28 [amdgpu]] *ERROR* sw_init of IP block <gmc_v8_0> failed -2 Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: amdgpu_device_ip_init failed Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: Fatal error during GPU init Dec 16 11:12:36 zeratul kernel: [drm] amdgpu: finishing device. Dec 16 11:12:36 zeratul kernel: amdgpu: probe of 0000:01:00.0 failed with error -2 The previous 4.19.8-300 kernel did not have this issue. The hardware is a custom PC with an ASUS H87I-PLUS motherboard and an ASUS Radeon RX 560 graphics card. Version-Release number of selected component (if applicable): kernel-4.19.9-300.fc29.x86_64 How reproducible: always Steps to Reproduce: 1. boot into 4.19.9-300 kernel Actual results: Black screen and aforementioned errors in the journal. Expected results: Normal boot with gdm showing so I can log in and use my computer.
linux-firmware in Fedora is lagging behind upstream. It looks like the gpu firmware in question was added upstream on Dec 3
Indeed. The file in question is https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/polaris11_k_mc.bin. You can drop that in /lib/firmware/amdgpu/ and then regenerate your initramfs with dracut which should work until there's an update for the firmware package.
*** Bug 1660507 has been marked as a duplicate of this bug. ***
*** Bug 1660776 has been marked as a duplicate of this bug. ***
*** Bug 1660674 has been marked as a duplicate of this bug. ***
linux-firmware-20181219-89.git0f22c852.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ba224c644f
linux-firmware-20181219-89.git0f22c852.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7d88c302b7
linux-firmware-20181219-89.git0f22c852.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7d88c302b7
For googlers: dnf upgrade https://kojipkgs.fedoraproject.org//packages/linux-firmware/20181219/89.git0f22c852.fc29/noarch/linux-firmware-20181219-89.git0f22c852.fc29.noarch.rpm dracut -fv /boot/initramfs-4.19.9-300.fc29.x86_64.img 4.19.9-300.fc29.x86_64 reboot
linux-firmware-20181219-89.git0f22c852.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ba224c644f
linux-firmware-20181219-89.git0f22c852.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Thanks for the fix. Just wanted to point out that even though I had the correct linux-firmware package, I still needed to update my initramfs manually ("dracut --regenerate-all --force").
I'm late to the party, but this does fix the issue for me. Thanks!
linux-firmware-20181219-89.git0f22c852.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1660772 has been marked as a duplicate of this bug. ***
*** Bug 1661681 has been marked as a duplicate of this bug. ***