Re: amdgpu firmware failure (solved?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



lsinitrd <kernel-initrd-filename> | grep amdgpu
and same with the name of the firmware.
If the module is there and the firmware is not then the module would
load and the firmware would not exist so cannot load.
The firmware gets loaded or not when the module loads.

On Thu, Oct 27, 2022 at 1:08 AM Felix Miata <mrmazda@xxxxxxxxxxxxx> wrote:
>
> Felix Miata composed on 2022-10-27 00:56 (UTC-0400):
>
> > # dnf install amd-gpu-firmware
> ...
> > So, amdgpu module loads, but:
> > # grep \(EE /var/log/Xorg.0.log
> > ...
> > [   319.021] (EE) open /dev/dri/card0: No such file or directory
> > ...
> > # dmesg | grep -i amd | grep aile
> > [    4.771180] amdgpu 0000:00:01.0: Direct firmware load for amdgpu/kaveri_pfp.bin failed with error -2
> > [    4.771187] amdgpu: gfx7: Failed to load firmware "amdgpu/kaveri_pfp.bin"
> > [    4.771189] [drm:gfx_v7_0_sw_init.cold [amdgpu]] *ERROR* Failed to load gfx firmware!
> > [    4.771559] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <gfx_v7_0> failed -2
> > [    4.771868] amdgpu 0000:00:01.0: amdgpu: amdgpu_device_ip_init failed
> > [    4.772081] amdgpu: probe of 0000:00:01.0 failed with error -2
> > #
>
> > What to do next? Bugzilla?
>
> # dracut -f
> ...
> # ls -Gg .ini*5.19.17* initramfs-5.19.17-200.fc36.x86_64.img
> -rw------- 1 34233108 Oct 27 01:49 initramfs-5.19.17-200.fc36.x86_64.img
> -rw------- 1 19015128 Oct 25 19:11 .initramfs-5.19.17-200.fc36.x86_64.img1
> -rw------- 1 34233108 Oct 27 01:49 .initramfs-5.19.17-200.fc36.x86_64.img2
>
> With the big fat new initrd all is as expected. Apparently the only way firmware
> will load is if in the initrd, and the last initrd builds didn't include it. Or,
> is it?
> --
> Evolution as taught in public schools is, like religion,
>         based on faith, not based on science.
>
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux