<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c36">Comment # 36</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 <span class="vcard"><a class="email" href="mailto:evo8800@gmail.com" title="Talha Khan <evo8800@gmail.com>"> <span class="fn">Talha Khan</span></a>
</span></b>
<pre>(In reply to JerryD from <a href="show_bug.cgi?id=109206#c35">comment #35</a>)
<span class="quote">> Well, I just ran Fedora updates which brought kernel to 5.0.7-200.fc29 and
> there was also an update to mesa-dri-drivers.x86_64 18.3.6-1.fc29. My laptop
> failed to boot with or without the raven_dmcu.bin file after this update.
>
> I then also noted that the 5.06 kernel will boot with or without the
> raven_dmcu.bin file. I am leaving that firmware file in place and using
> 5.06 kernel at the moment.
>
> I suspect we have a "whack-a-mole" bug, also affectionately known as a
> Heisenbug. Or at least more than one problem overlapping another. Hard to
> say whether the problem is in the kernel or somewhere else. For sure, I can
> not boot the 5.07.</span >
I also updated my system to kernel 5.0.7-200.fc29 and mesa-dri-drivers.x86_64
version 18.3.6-1.fc29, and here are the results for me:
original initramfs image with raven_dmcu.bin file: Unable to boot, same issue
as before.
updated initramfs image without raven_dmcu.bin file: able to boot fine.
It's unfortunate that the issue is so hard to reproduce.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>