<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#c57">Comment # 57</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:joseph.coutcher@gmail.com" title="Joe Coutcher <joseph.coutcher@gmail.com>"> Joe Coutcher</a> <pre>(In reply to Ondrej Lang from <a href="show_bug.cgi?id=109206#c55">comment #55</a>) > Hi Joe, > > I'm quite sure your issue is not related to this ticket. The problem in this > bug report is quite specific and is related to the raven_dmcu.bin firmware. > It has a specific symptom where the screen is not initialized during boot > (stays blank / black) so I think you need to report your problem somewhere > else. Also, it would be good if you can check the kernel log after crash and > see what error messages you have and then google for that specific message > to find if someone else already created a bug report for it. > > I have been running kernel 5.2 since yesterday and had no issues whatsoever. > I also just run the Basemark Web 3.0 benchmark and had no issues. > > As for your lockups, I know that the AMD APU had problems with random > lockups in earlier kernels (if I remember correctly it was related to the > C-state changes of the CPU), I myself had the problem and for me the fix was > to add "idle=nomwait" to my kernel parameters. That fixed the random lockups > for me. Now I don't know if this issue has already been addressed, last time > I tried without the parameter was kernel 5.0 I think and still had lockups, > so this might not be related to your specific problem, but as I said, best > course of action for you is to inspect the kernel log after a crash, check > the error message and then search for a bug report with that error and > report your findings there. Sorry...I was using the Lynx browser to type out the reply last night and didn't include all the details. :-) My report was related to this issue. On every distro I've tried (Ubuntu 19.04, Fedora 30, OpenSuSE Tumbleweed), whenever it tries to initialize the firmware, the system goes to a black screen. The only way for me to get around it is to boot with nomodeset, remove raven_dmcu.bin, update my initrd, and reboot. My tests were to provide a baseline: fresh install, no workarounds applied, with kernel 5.2rc7 and latest linux-firmware package (AFAIK.) Under those conditions, raven_dmcu.bin loads, I can get to the GUI, but seeing garbage on the screen. When I have some time this weekend, I'll do some more testing/sift through the logs/try building 5.2 final and see if anything jumps out at me. I'll also retry my tests with idle=nomwait.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>