Linux 4.20 To Receive Fix That Prevented Some AMD Raven Ridge Systems From Booting

[phoronix]

Phoronix: Linux 4.20 To Receive Fix That Prevented Some AMD Raven Ridge Systems From Booting

It looks like the mainline Linux 4.20 kernel within a few days will be playing nicely on more AMD hardware. In particular, the Raven Ridge Zen+Vega APUs that have been rather troublesome depending upon the BIOS/motherboard since their launch almost one year ago...

http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.20-AMD-MCE-Fix

[Azpegath]

There's another huge firmware-related bug for 290/380 cards that prevents 4.19.x from booting. I don't have the link right now, but I'm unable to use the 4.19-series because of it.

[dungeon]

Of bug reports related to this issue, the Ryzen 2500U / Raven Ridge hardware seems to be a common trait.

Not that situation was much better on Windows with Ryzen laptop APUs too OEMs get just one driver and that is it, but seems AMD will improve that to semi-annually

https://www.guru3d.com/news-story/am...en-mobile.html

[Zajec]

Michael: the bug report you linked https://bugzilla.kernel.org/show_bug.cgi?id=201213 is only about a WARNING, that wasn't critical.

The real & more serious bug that is being fixed by a linked commit is https://bugzilla.kernel.org/show_bug.cgi?id=201291

In any case, I'm really happy (proud?) I managed to debug this & provide required info for a fix.

[Zajec]

Ah, I've just noticed you linked *both* bug reports. Sorry for the noise, links are next to each other and seem like a single one.

[41zu]

I have a different problem with my ryzen laptop. I have to set the kernel parameter ivrs_ioapic[32]=00:14.0 in GRUB

[LazarusIV]

As a side note, anyone using the HP Envy x360 with the Ryzen 2500U? I'm trying to figure out a way to apply a firmware update and I really don't want to have to install Win10 just to update the firmware...

Also, what distros are people using with this laptop? I've been quite happy with mine.

[treba]

Michael: the bug report you linked https://bugzilla.kernel.org/show_bug.cgi?id=201213 is only about a WARNING, that wasn't critical.

The real & more serious bug that is being fixed by a linked commit is https://bugzilla.kernel.org/show_bug.cgi?id=201291

In any case, I'm really happy (proud?) I managed to debug this & provide required info for a fix.

Kudos for that!

[darkbasic]

I got this issue on my Raven Ridge system and it was a nightmare, fortunately with latest AGESA from November they fixed it in firmware. As always the problem is the fuck1ng closed source damn blob. Can't wait for my Raptor system.

[agd5f]

I have a different problem with my ryzen laptop. I have to set the kernel parameter ivrs_ioapic[32]=00:14.0 in GRUB

Windows doesn't enable interrupt remapping so the OEM probably never validated their IVRS tables.