<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init" href="https://bugs.freedesktop.org/show_bug.cgi?id=108781#c32">Comment # 32</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 4.19 Regression - Hawaii (R9 390) boot failure - Invalid PCC GPIO / invalid powerlevel state / Fatal error during GPU init" href="https://bugs.freedesktop.org/show_bug.cgi?id=108781">bug 108781</a> from <a class="email" href="mailto:shecks@gmail.com" title="Shecks <shecks@gmail.com>"> Shecks</a> <pre>(In reply to freedesktop from <a href="show_bug.cgi?id=108781#c27">comment #27</a>) > OK there seems to be something screwy going on with the amdgpu.dpm option - > if that's set to 0, it still results in a blank screen. It has to be removed > entirely from the kernel command line for boot to work for me on 4.19. > > I'm not sure if that's a different bug or not, but can anyone who had > success with removing the option, also test with amdgpu.dpm=0 to see if it > still results in a blank screen? > > Also, are FD BZ email notifications broken for anyone else? I can confirm that attempting to boot with either amdgpu.dpm=0 or amdgpu.dpm=1 results in the same black screen issue on my PC I am now running Fedora 29 with kernel 4.19.5 (MSI R9 390 8GB Gaming GPU) and the only way to boot is by completely removing the amdgpu.dpm kernel parameter.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>