<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#c29">Comment # 29</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:freedesktop@clouddrop.de" title="pascalp <freedesktop@clouddrop.de>"> pascalp</a> <pre>For me it is the other way round: With my 290x I used to boot fine under 4.18 without amdgpu.dpm set at all. After updating to 4.19 and being unable to boot I read that amdgpu.dpm defaults to "enabled" so I explicitly had to add amdgpu.dpm=0 to be able to boot again. amdgpu.dc does not matter in this context - both 0 and 1 work as long as dpm is disabled. This is on an unpatched kernel (4.19.4 currently).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>