dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init
Date: Sat, 05 Jan 2019 13:28:47 +0000	[thread overview]
Message-ID: <bug-108781-502-lus8otdiu0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108781-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2420 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108781

--- Comment #38 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 firmware!
> > [drm:amdgpu_device_init.cold.31 [amdgpu]] *ERROR* sw_init of IP block
> > <gmc_v7_0> failed -2
> > [drm] amdgpu: finishing device.
> 
> The driver is not able to find the firmware when it loads.  Please make sure
> the initrd contains the firmware if you are using one.  Please note that
> 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=x completely from linux commandline and updated grub. '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 to 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"  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-initramfs,
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3544 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-01-05 13:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17 21:25 [Bug 108781] 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:26 ` bugzilla-daemon
2018-11-17 21:34 ` bugzilla-daemon
2018-11-19 15:01 ` bugzilla-daemon
2018-11-19 17:25 ` bugzilla-daemon
2018-11-20  2:26 ` bugzilla-daemon
2018-11-20 12:50 ` bugzilla-daemon
2018-11-20 14:35 ` bugzilla-daemon
2018-11-20 20:20 ` bugzilla-daemon
2018-11-21  0:06 ` bugzilla-daemon
2018-11-21  7:52 ` bugzilla-daemon
2018-11-21  9:48 ` bugzilla-daemon
2018-11-22  0:13 ` bugzilla-daemon
2018-11-22  0:15 ` bugzilla-daemon
2018-11-22  0:15 ` bugzilla-daemon
2018-11-22  0:48 ` bugzilla-daemon
2018-11-22  1:38 ` bugzilla-daemon
2018-11-22 17:01 ` bugzilla-daemon
2018-11-22 18:56 ` bugzilla-daemon
2018-11-23  9:42 ` bugzilla-daemon
2018-11-23 14:42 ` bugzilla-daemon
2018-11-23 21:46 ` bugzilla-daemon
2018-11-23 22:42 ` bugzilla-daemon
2018-11-23 22:43 ` bugzilla-daemon
2018-11-25 19:08 ` bugzilla-daemon
2018-11-27 17:11 ` bugzilla-daemon
2018-11-28 11:28 ` bugzilla-daemon
2018-11-28 11:45 ` bugzilla-daemon
2018-11-28 14:46 ` bugzilla-daemon
2018-12-02  6:34 ` bugzilla-daemon
2018-12-02  6:44 ` bugzilla-daemon
2018-12-02 15:53 ` bugzilla-daemon
2018-12-03  3:07 ` bugzilla-daemon
2018-12-03 13:16 ` bugzilla-daemon
2018-12-03 13:26 ` bugzilla-daemon
2018-12-30 22:55 ` bugzilla-daemon
2018-12-31 15:08 ` bugzilla-daemon
2019-01-05 13:28 ` bugzilla-daemon [this message]
2019-01-11  0:04 ` bugzilla-daemon
2019-11-19  9:04 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108781-502-lus8otdiu0@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox