| 1 |
On Fri, Jan 12, 2018 at 1:42 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> On Friday, 12 January 2018 17:47:46 GMT Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> The other odd thing is that a firmware update was released for my |
| 5 |
>> motherboard (ASRock AB350 Pro4) on the 10th, and if I flash it grub |
| 6 |
>> will no longer boot the linux kernel, and it is pretty slow overall, |
| 7 |
>> but it will still boot memtestx86 just fine. I figured I'd wait a few |
| 8 |
>> days and see if there is any further info on it. |
| 9 |
> |
| 10 |
> No Asus MoBo firmware updates here ... but would they be even required/ |
| 11 |
> necessary for the CPU bugs? |
| 12 |
|
| 13 |
It shouldn't be. I'm not sure if Ryzen has anything equivalent to the |
| 14 |
Intel Management Engine. Intel has been scrambling to patching the |
| 15 |
firmware for that (which basically gives a hardware-level rootkit to |
| 16 |
anybody who exploits it). |
| 17 |
|
| 18 |
The official docs just mentioned adding support for additional |
| 19 |
processors with an AGESA update. I wouldn't be surprised if at some |
| 20 |
point the motherboard vendors slip in the microcode updates there as |
| 21 |
well. When I was having issues getting linux to update the microcode |
| 22 |
I figured I'd check the firmware for updates. When it failed to boot |
| 23 |
I just rolled it back. They actually did 2 firmware releases, with |
| 24 |
one being used as a bridge to the other. That also makes me wonder if |
| 25 |
there is a microcode update of some kind in there. |
| 26 |
|
| 27 |
-- |
| 28 |
Rich |
Archives