Announcement

Collapse
No announcement yet.

Updated AMD Zen 1 Through Zen 3 CPU Microcode Published

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

  • csutcliff
    replied
    Code:
    Microcode patches in /lib/firmware/amd-ucode/microcode_amd_fam17h.bin:
    Family=0x17 Model=0x08 Stepping=0x02: Patch=0x0800820d Length=3200 bytes
    Family=0x17 Model=0x01 Stepping=0x02: Patch=0x0800126e Length=3200 bytes
    Family=0x17 Model=0x31 Stepping=0x00: Patch=0x08301055 Length=3200 bytes
    Family=0x17 Model=0x08 Stepping=0x02 Ryzen/Threadripper Zen+
    2XXX (and the 1600AF)
    No change from previous patch level
    Family=0x17 Model=0x01 Stepping=0x02 Zen1 EPYC
    (inc EPYC embedded)
    updated patch level from previous version
    Family=0x17 Model=0x31 Stepping=0x00 Zen2 EPYC newly added patch
    Last edited by csutcliff; 21 April 2022, 07:31 AM.

    Leave a comment:


  • zerothruster
    replied
    The fam17 microcode may be bigger, but it only contains items for three specific model and stepping variants. To see what it (and fam19) contain, use
    https://github.com/AMDESE/amd_ucode_info

    Leave a comment:


  • Soul_keeper
    replied
    Ok, thanks. I guess there is nothing I can do to make the loader work.
    I'll just have to wait for a bios update to test the new microcode.

    Leave a comment:


  • clouddrop
    replied
    Originally posted by Soul_keeper View Post
    I guess you are thinking of updating the bios. Using the amd released firmware with the kernel on boot don't permanently modify anything as far as I know.
    For me the issue was with the Bluetooth firmware for the Intel AX200 chip. It would not load the latest driver from linux-firmware. Only after doing a cold boot + draining all power would the new version be loaded. I stumbled across this solution after several reports in this thread. Maybe this is specific to the Bluetooth firmware? But whenever I see a linux-firmware update I follow this procedure ever since just to make sure (and will do for the next release as well as there is updated bluetooth firmware).

    Leave a comment:


  • Developer12
    replied
    Originally posted by Soul_keeper View Post
    I guess you are thinking of updating the bios. Using the amd released firmware with the kernel on boot don't permanently modify anything as far as I know.

    Anyways, i'm unable to actually use the microcode released by AMD, and i'm pretty sure i've never been able to and i've spent a few years trying.
    It just never loads, and searching the internet till my eyes hurt never gives an answer.
    It's usually due to an incorrect table in the container header not listing your specific CPU, even if it's compatible. The whole microcode loading facility in linux if full of horrible jank.

    Leave a comment:


  • Soul_keeper
    replied
    I guess you are thinking of updating the bios. Using the amd released firmware with the kernel on boot don't permanently modify anything as far as I know.

    Anyways, i'm unable to actually use the microcode released by AMD, and i'm pretty sure i've never been able to and i've spent a few years trying.
    It just never loads, and searching the internet till my eyes hurt never gives an answer.

    Leave a comment:


  • clouddrop
    replied
    Originally posted by Soul_keeper View Post
    I can't get the kernel to use the updated microcode.
    ...
    It always shows the same patch_level.
    Any ideas ?
    For me I have to shutdown my machine, pull the PSU Plug and hold the power button for about 10 seconds to get new firmware to load. Afterwards the new version is shown during boot. I had been running with old firmware for quite some time before discovering this a couple of months ago.

    Leave a comment:


  • Soul_keeper
    replied
    I guess dmesg just won't show the updated version. It only shows what you booted with.

    If enable pr_debug messages, then do echo 1 > /sys/devices/system/cpu/microcode/reload

    [Mon Apr 11 15:09:08 2022] microcode: verify_and_add_patch: Added patch_id: 0x0a001058, proc_id: 0xa010
    [Mon Apr 11 15:09:08 2022] microcode: verify_and_add_patch: Added patch_id: 0x0a001173, proc_id: 0xa011
    [Mon Apr 11 15:09:08 2022] microcode: verify_and_add_patch: Added patch_id: 0x0a001229, proc_id: 0xa012

    No idea if it is working.
    cat /sys/devices/system/cpu/cpu0/microcode/version
    0xa201204
    The older version is still being shown.

    Anyone else try this ?

    Leave a comment:


  • Soul_keeper
    replied
    I can't get the kernel to use the updated microcode.

    kernel .config options:

    #
    # Generic Driver Options
    #
    # CONFIG_UEVENT_HELPER is not set
    CONFIG_DEVTMPFS=y
    CONFIG_DEVTMPFS_MOUNT=y
    # CONFIG_DEVTMPFS_SAFE is not set
    CONFIG_STANDALONE=y
    CONFIG_PREVENT_FIRMWARE_BUILD=y

    #
    # Firmware loader
    #
    CONFIG_FW_LOADER=y
    CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd_fam19h.bin"
    CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
    # CONFIG_FW_LOADER_USER_HELPER is not set
    # CONFIG_FW_LOADER_COMPRESS is not set
    # end of Firmware loader

    kernel-firmware-20220124_eb8ea1b-noarch-1
    dmesg
    [ 1.158007] microcode: CPU0: patch_level=0x0a201204
    md5sum
    482491f4d4f94f480ff94362e5ff91bc /lib/firmware/amd-ucode/microcode_amd_fam19h.bin
    -rw-r--r-- 1 root root 16804 Jan 24 22:03 /lib/firmware/amd-ucode/microcode_amd_fam19h.bin

    kernel-firmware-20220318_681281e-noarch-1
    dmesg
    [ 1.158688] microcode: CPU0: patch_level=0x0a201204
    md5sum
    b7ace9dda9a1319dae2e75b8768870b9 /lib/firmware/amd-ucode/microcode_amd_fam19h.bin
    -rw-r--r-- 1 root root 16804 Apr 9 19:40 /lib/firmware/amd-ucode/microcode_amd_fam19h.bin

    kernel-firmware-20220411_f219d61-noarch-1
    dmesg
    [ 1.157711] microcode: CPU0: patch_level=0x0a201204
    md5sum
    ac0884e187cfa302e1c90b3e79e5ff1e /lib/firmware/amd-ucode/microcode_amd_fam19h.bin
    -rw-r--r-- 1 root root 16804 Apr 11 10:48 /lib/firmware/amd-ucode/microcode_amd_fam19h.bin


    It always shows the same patch_level.
    Any ideas ?

    Leave a comment:


  • mangeek
    replied
    Originally posted by phoronix View Post
    we are left to only speculate
    I see what you did there. ;-)

    Leave a comment:

Working...
X