Comme=
nt # 57
on bug 10920=
6
from Joe Coutcher
(In reply to Ondrej Lang from comment #55)
> Hi Joe,
>=20
> I'm quite sure your issue is not related to this ticket. The problem i=
n this
> bug report is quite specific and is related to the raven_dmcu.bin firm=
ware.
> It has a specific symptom where the screen is not initialized during b=
oot
> (stays blank / black) so I think you need to report your problem somew=
here
> else. Also, it would be good if you can check the kernel log after cra=
sh and
> see what error messages you have and then google for that specific mes=
sage
> to find if someone else already created a bug report for it.
>=20
> I have been running kernel 5.2 since yesterday and had no issues whats=
oever.
> I also just run the Basemark Web 3.0 benchmark and had no issues.
>=20
> 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 f=
ix was
> to add "idle=3Dnomwait" to my kernel parameters. That fixed =
the random lockups
> for me. Now I don't know if this issue has already been addressed, las=
t time
> I tried without the parameter was kernel 5.0 I think and still had loc=
kups,
> 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, c=
heck
> 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 firmwa=
re,
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=3Dnomwait.