Announcement

Collapse
No announcement yet.

ASRock BIOS breaks Linux

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

  • lu_tze
    replied
    4.18.10 fixes it, the CCP driver has timeout for SEV to return.

    Finally it works, amd_kvm and all.

    Leave a comment:


  • dc740
    replied
    If you have a backup for your GA-AX370-Gaming K7 I recommend the BIOS "F23f" (which is the beta previous to the F23).
    This beta BIOS was better than the final release because:
    * It didn't have the PSP bug (or didn't expose it to Linux): it didn't have the timeouts seen in this post
    * There was an option to DISABLE PSP: the option was removed in F23.
    * "Typical Current" option appeared for the first time: This was the first BIOS that exposed the option that made Ryzen systems usable for many people. More info here: https://www.phoronix.com/forums/foru...pu-gcn-1-1-bug

    So... if you have F23f, or a backup, stick to that BIOS.

    Here is the download link


    Get it while you can. It's not shown in the Gigabyte download page, but if you try to download the F23 version and add the extra F manually, you get the working download link like I posted above, and the download works fine. They are probably going to remove it at some point, so make sure you make a backup. That BIOS version is gold for this motherboard (specially for the ability to disable PSP, which is no longer available)

    Good luck
    Last edited by dc740; 17 September 2018, 07:51 AM.

    Leave a comment:


  • dfyt
    replied
    Well mine was 100% the bios update "Update AGESA 1.0.0.4" F23. Check the manjaro link I provided. With the bios update upto 10 mins to shutdown only when ZFS is installed. Rolled back the bios to F22 "Update AGESA 1.0.0.1a" no more issues.

    https://www.gigabyte.com/us/Motherbo...upport-dl-bios

    Leave a comment:


  • chithanh
    replied
    There are now reports that 4.19_rc kernels will work fine with PinnaclePI-1.0.0.4

    Originally posted by SwooshyCueb View Post
    I wonder why they updated to AGESA 1.0.0.2 when 1.0.0.6 was released over a year ago https://www.anandtech.com/show/11447...sa-1006-update
    Originally posted by lu_tze View Post
    Because version numbers for TR AGESA and Ryzen/AM4 AGESA are different. The article linked is about Ryzen AGESA.
    Actually, Threadripper is also Ryzen...
    But the AGESA version numbers are actually different for different chips (Summt, Raven, Pinnacle).

    Originally posted by dfyt View Post
    So I suspect I am having the same issue https://forum.manjaro.org/t/4-17-9-k...s-zfs/57439/21
    I think this issue is unrelated to ZFS.

    Leave a comment:


  • dfyt
    replied
    So I suspect I am having the same issue https://forum.manjaro.org/t/4-17-9-k...s-zfs/57439/21

    Anyone had any luck with this? I also did a bios update and I can't lose amd_kvm. My board is a Gigabyte X370 K7. Note that booting a LTS kernel fixes the issue.

    Leave a comment:


  • lu_tze
    replied
    Originally posted by SwooshyCueb View Post
    I wonder why they updated to AGESA 1.0.0.2 when 1.0.0.6 was released over a year ago https://www.anandtech.com/show/11447...sa-1006-update
    Because version numbers for TR AGESA and Ryzen/AM4 AGESA are different. The article linked is about Ryzen AGESA.

    Leave a comment:


  • lu_tze
    replied
    Originally posted by djselbeck View Post

    You can add module_blacklist=ccp to your kernel commandline
    While blacklisting ccp allows at least to boot, it breaks kvm_amd.

    Back to 2.30 for me.

    Leave a comment:


  • djselbeck
    replied
    Originally posted by brent View Post
    Or maybe the PSP driver is simply buggy? It's a rather new driver. I wonder if you can disable it without recompiling the kernel.
    You can add module_blacklist=ccp to your kernel commandline

    Leave a comment:


  • SwooshyCueb
    replied
    I wonder why they updated to AGESA 1.0.0.2 when 1.0.0.6 was released over a year ago https://www.anandtech.com/show/11447...sa-1006-update

    Leave a comment:


  • brent
    replied
    FWIW it doesn't look like this is an ASRock specific issue. It's a bug either in the PSP firmware of the Linux PSP driver:

    Leave a comment:

Working...
X