Comme=
nt # 38
on bug 10878=
1
from DanglingPointerException@gmail.com
(In reply to Alex Deucher from comment #37)
> (In reply to DanglingPointerException from comment #36)
> > [drm:gmc_v7_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmwar=
e!
> > [drm:amdgpu_device_init.cold.31 [amdgpu]] *ERROR* sw_init of IP b=
lock
> > <gmc_v7_0> failed -2
> > [drm] amdgpu: finishing device.
>=20
> The driver is not able to find the firmware when it loads. Please mak=
e sure
> the initrd contains the firmware if you are using one. Please note th=
at
> when using amdgpu, the firmware must be in /lib/firmware/amdgpu rather=
than
> /lib/firmware/radeon.
Thanks for the tip/hint on how to go about starting to sort it out. I have
SOLVED the problem and the R9-290X now fully works with Mesa 18.3 and Linux
Kernel 4.20.0
[SOLVED]
My Solution for those wishing to migrate to 4.20.0 with R9-290/X
1) Removed amdgpu.dpm=3Dx completely from linux commandline and updated gru=
b. '0'
or '1' will NOT work and will not boot, NOT even tty
2) copied /lib/firmware/radeon/* to /lib/firmware/amdgpu/
3) backed-up all contents of /lib/firmware/radeon/*
4) deleted /lib/firmware/radeon/
5) ensured initrd for 4.20.0 was in the /boot location
6) sudo update-initramfs -u
7) confirm contents of functioning/working kernel via "~$ lsinitramfs
/boot/initrd.img-<YOUR-KERNEL>-generic | grep hawaii" It needs t=
o still point
to the /lib/firmware/radeon even though we have deleted it.
8) confirm contents of new kernel that isn't functioning. For me the kernel=
was
"~$ lsinitramfs /boot/initrd.img-4.20.0-042000-generic | grep hawaii&q=
uot; It
should only contain /lib/firmware/amdgpu/*
9) Restore /lib/firmware/radeon/* from backup. This is so you can recover to
the previous kernel version if necessary.
10) Restart/Reboot
11)[OPTIONAL-IMPORTANT] If all working well (it is for me) then for no
conflicts for future kernels, delete /lib/firmware/radeon THEN delete all
previous kernels prior to the new kernel that is now functioning. If you do
NOT do this AND install a new Kernel AND then run the command update-initra=
mfs,
then you will have duplicate paths in the initrd for the future kernel. Not
sure what happens when that happens, I'm not testing to find out as haven't=
got
time for it.