[AMD Public Use]

It looks like the driver is not able to access the firmware for some reason.  
Please make sure it is available in your initrd or compiled into the kernel 
depending on your config.

Alex

________________________________
From: amd-gfx <amd-gfx-boun...@lists.freedesktop.org> on behalf of Mikhail 
Gavrilov <mikhail.v.gavri...@gmail.com>
Sent: Sunday, December 27, 2020 11:58 AM
To: amd-gfx list <amd-...@lists.freedesktop.org>; Linux List Kernel Mailing 
<linux-ker...@vger.kernel.org>; dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [bug] Radeon 3900XT not switch to graphic mode on kernel 5.10

On Sun, 27 Dec 2020 at 21:39, Mikhail Gavrilov
<mikhail.v.gavri...@gmail.com> wrote:
> I suppose the root of cause my problem here:
>
> [    3.961326] amdgpu 0000:0b:00.0: Direct firmware load for
> amdgpu/sienna_cichlid_sos.bin failed with error -2
> [    3.961359] amdgpu 0000:0b:00.0: amdgpu: failed to init sos firmware
> [    3.961433] [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware!
> [    3.961529] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init
> of IP block <psp> failed -2
> [    3.961549] amdgpu 0000:0b:00.0: amdgpu: amdgpu_device_ip_init failed
> [    3.961569] amdgpu 0000:0b:00.0: amdgpu: Fatal error during GPU init
> [    3.961911] amdgpu: probe of 0000:0b:00.0 failed with error -2
>

# dnf provides */sienna_cichlid_sos.bin
Last metadata expiration check: 3:01:27 ago on Sun 27 Dec 2020 06:53:25 PM +05.
linux-firmware-20201218-116.fc34.noarch : Firmware files used by the
Linux kernel
Repo        : @System
Matched from:
Filename    : /usr/lib/firmware/amdgpu/sienna_cichlid_sos.bin

linux-firmware-20201218-116.fc34.noarch : Firmware files used by the
Linux kernel
Repo        : rawhide
Matched from:
Filename    : /usr/lib/firmware/amdgpu/sienna_cichlid_sos.bin

# dnf install linux-firmware-20201218-116.fc34.noarch
Last metadata expiration check: 3:02:11 ago on Sun 27 Dec 2020 06:53:25 PM +05.
Package linux-firmware-20201218-116.fc34.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Looks like firmware is present. So I didn't understand why the kernel
cannot read firmware.

--
Best Regards,
Mike Gavrilov.
_______________________________________________
amd-gfx mailing list
amd-...@lists.freedesktop.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&amp;data=04%7C01%7Calexander.deucher%40amd.com%7Cf76668be26de4be7d0af08d8aa88a8dc%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637446851228684932%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=NOQO9oeX9gOmM7aOThep5kjURTTn14N5nNkhGx7rofQ%3D&amp;reserved=0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Reply via email to