<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U" href="https://bugs.freedesktop.org/show_bug.cgi?id=109206#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U" href="https://bugs.freedesktop.org/show_bug.cgi?id=109206">bug 109206</a> from <a class="email" href="mailto:tim@timcarr.me" title="Tim Carr <tim@timcarr.me>"> Tim Carr</a> <pre>(In reply to Harry Wentland from <a href="show_bug.cgi?id=109206#c15">comment #15</a>) > Can you see if this patch fixes it: > <a href="https://patchwork.freedesktop.org/patch/277181/">https://patchwork.freedesktop.org/patch/277181/</a> Wasn't able to get that patch to apply cleanly to either 4.20 or 5.0rc2. I did attempt to manually edit the function in the amdgpu_psp.c file according to the patch, but now have in my log: "[drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3" I'm assuming I attempted to apply the patch to the wrong revision. Behavior for me is somewhat changed, before the patch I got about 4 lines of scrambled pixels about 4/5ths of the way down my screen on anything above kernel 4.19, with the patch applied to 5.0rc2 those lines appear for a couple of seconds and then the screen goes and remains totally blank. I can attach the full log if you want, but considering I wasn't able to directly apply the patch and instead manually modified the "psp_cmd_submit_buf" function to warn instead of error and not return -EINVAL as described in the patch, I'd rather not clutter this with potentially bad log data. Should that patch be applied to drm-next instead of what is in the mainline kernel?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>