Announcement

Collapse
No announcement yet.

Updated AMD Zen CPU Microcode Lands In Linux-Firmware Tree

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Updated AMD Zen CPU Microcode Lands In Linux-Firmware Tree

    Phoronix: Updated AMD Zen CPU Microcode Lands In Linux-Firmware Tree

    Updated AMD Family 17h (Zen / Zen 2) CPU microcode has quietly landed within the linux-firmware Git tree...

    http://www.phoronix.com/scan.php?pag...-CPU-Microcode

  • #2
    Wait, is the AMD microcode only 33 KB in size? Intel's is 2.5 MB.

    Comment


    • #3
      Originally posted by GrayShade View Post
      Wait, is the AMD microcode only 33 KB in size? Intel's is 2.5 MB.
      The microcode for fam17h is 9.5kB in size. But the Intel microcode blob covers way more hardware.

      Comment


      • #4
        Originally posted by PuckPoltergeist View Post

        The microcode for fam17h is 9.5kB in size. But the Intel microcode blob covers way more hardware.
        That's why I added up the size of everything in that directory.

        Comment


        • #5
          ~OT question @ other ASRock X470 Taichi Ultimate owners:
          Has anyone running a recent Linux (or more specifically: Fedora) experienced issues with 1st gen Ryzen 7 and BIOS versions newer than 2.00 (2018/12/19)?
          This warning makes me somewhat nervous:
          **** User will not able to flash previous BIOS once upgrading to this BIOS version.

          Comment


          • #6
            Originally posted by Neuro-Chef View Post
            ~OT question @ other ASRock X470 Taichi Ultimate owners:
            Has anyone running a recent Linux (or more specifically: Fedora) experienced issues with 1st gen Ryzen 7 and BIOS versions newer than 2.00 (2018/12/19)?
            This warning makes me somewhat nervous:
            **** User will not able to flash previous BIOS once upgrading to this BIOS version.
            Someone correct me if I'm wrong, but didn't OS installed firmware replaces BIOS one after you are inside the said OS?

            Comment


            • #7
              Doesn't seem to have changed anything here on my ryZen 2400G:

              Before

              [ 0.915888] microcode: CPU0: patch_level=0x08101016
              [ 0.921706] microcode: CPU1: patch_level=0x08101016
              [ 0.927320] microcode: CPU2: patch_level=0x08101016
              [ 0.934222] microcode: CPU3: patch_level=0x08101016
              [ 0.935556] microcode: CPU4: patch_level=0x08101016
              [ 0.935562] microcode: CPU5: patch_level=0x08101016
              [ 0.935568] microcode: CPU6: patch_level=0x08101016
              [ 0.935577] microcode: CPU7: patch_level=0x08101016

              After:

              [ 0.925365] microcode: CPU0: patch_level=0x08101016
              [ 0.928701] microcode: CPU1: patch_level=0x08101016
              [ 0.934700] microcode: CPU2: patch_level=0x08101016
              [ 0.941859] microcode: CPU3: patch_level=0x08101016
              [ 0.945435] microcode: CPU4: patch_level=0x08101016
              [ 0.949367] microcode: CPU5: patch_level=0x08101016
              [ 0.952026] microcode: CPU6: patch_level=0x08101016
              [ 0.955823] microcode: CPU7: patch_level=0x08101016

              Comment


              • #8
                I don't think this is the same thing as the blob which has an AGESA version and you get updates from your Mobo vendor of... I think.

                Comment


                • #9
                  Originally posted by [email protected] View Post

                  Someone correct me if I'm wrong, but didn't OS installed firmware replaces BIOS one after you are inside the said OS?
                  that's the microcode. He is talking about board firmware (initialization and other low-level functionality of more than just the CPU cores)

                  Comment


                  • #10
                    Originally posted by FireBurn View Post
                    Doesn't seem to have changed anything here on my ryZen 2400G:

                    Before
                    [ 0.915888] microcode: CPU0: patch_level=0x08101016
                    <snip>

                    After:
                    [ 0.925365] microcode: CPU0: patch_level=0x08101016
                    <snip>
                    Yeah, I feel your pain. Been down this road myself yesterday. What worked for me is copying the new firmware (microcode_amd_fam17h.bin) into the relevant directory (/lib/firmware/amd-ucode/) (make sure the permissions are correct and you backup the old file you are replacing!), followed by a version of the instructions here worked for me with my Ryzen 2600 on Lubuntu 18.04.3 with kernel 5.3.x. The key bits for me were:

                    Code:
                    echo 1 > /sys/devices/system/cpu/microcode/reload
                    followed by (as root)

                    Code:
                    update-initramfs -u
                    and rebooting to test.

                    Comment

                    Working...
                    X