Tracking X370 UEFI issues
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=9853
Printed Date: 12 Sep 2025 at 3:54pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Tracking X370 UEFI issues
Posted By: shmerl
Subject: Tracking X370 UEFI issues
Date Posted: 09 Oct 2018 at 10:08am
|
Just to open a definitive thread about it, since others seem to focus on issues with specific release versions. I'm so far waiting for the fix that's affecting both 4.80 and 4.81. When enabling virtualization in UEFI, it doesn't have any effect in the host OS (Debian testing Linux for me) and Qemu/KVM can't detect virtualization availability. With 4.64 there is no such issue.
|
Replies:
Posted By: xhue
Date Posted: 10 Oct 2018 at 2:16am
|
I stopped caring anymore. Since I'm way beyond RMA I ordered a new X470 from ASUS. As soon as it arrives I'm dumping this PoS on fleabay. ASRock stopped caring about their customers the second they took your money form the purchase. I say give them NO more money. We can talk again in 5-10 years.
|
Posted By: basedmeezus
Date Posted: 13 Oct 2018 at 2:35am
|
For anyone else, this is due to agesa pinnacle_pi 1.0.0.4. Bios/uefi advertises that it supports secured encrypted virtualization but does not answer kernel calls requesting if the hardware supports it. As for op, if you update your kernel to latest stable build, it should fix ur kvm issue. Also update kvm and qemu. EDIT: there's some incorrect info here for anyone else reading this, I'll fix up all my mistakes once i get home. but overall, updating to kernel 4.18.13 + should resolve any issue
|
Posted By: shmerl
Date Posted: 13 Oct 2018 at 3:17am
" rel="nofollow -
Interesting, thanks for the info! So newest kernel works around this problem? I'm now on 4.19.0-rc7, due to 4.18 having a ton of problems with AMD Vega and DisplayPort. Debian testing is shipping Qemu 2.12. Newer one (3.0) wasn't packaged yet. Should 2.12 work with it?
|
basedmeezus wrote:Posted By: basedmeezus
Date Posted: 13 Oct 2018 at 4:14am
|
" rel="nofollow - I'm on mobile at the moment and can't really check. What version of Debian are you running? EDIT: QEMU 3.0.0 can be built from source from here: https://www.qemu.org/download/#source EDIT2: Not sure if your UEFI will have this option, but try disabling PSP. I'm currently at work, but once I get home, I can tell you where it resides in my B450 Fatal1ty gaming k4
|
Posted By: shmerl
Date Posted: 13 Oct 2018 at 4:28am
|
Debian testing. I haven't tried the UEFI update recently, but I'll give it a try with the recent 4.19 kernel. |
Posted By: shmerl
Date Posted: 13 Oct 2018 at 4:29am
" rel="nofollow -
Does it mean it's still a bug in UEFI?
|
Posted By: basedmeezus
Date Posted: 13 Oct 2018 at 4:49am
|
Yes, I'm already in touch with Asrock support to hopefully upgrade Bios to fix this, but it seem's like the person replying back to me is a bot :/ (pablo medina). I've asked them to escalate the issue to the dev team if possible. I haven't used debian in a while, but I'm gonna take a wild guess and say the reason why you weren't able use kvm was maybe possibly debian recompiled the kernel with the following line of code: CONFIG_CRYPTO_DEV_SP_PSP=N which completely disables virtualization, but at the same time fixes shutdown hang time/feeze. If hopefully that was the case, kernels 4.18.13+ added a timeout call which gets rid of hang time and re-enables kvm.
|
Posted By: shmerl
Date Posted: 13 Oct 2018 at 5:11am
|
From my current config:
So I suppose it can work now. I'll give it another try.
|
Posted By: shmerl
Date Posted: 13 Oct 2018 at 5:25am
|
@basedmeezus: Just updated to UEFI 4.81, enabled SVM and all is working now! So newer kernel fixed it as you mentioned, even with older qemu. Thanks again for the hint! |
Posted By: basedmeezus
Date Posted: 13 Oct 2018 at 5:44am
" rel="nofollow -
Awesome, that's great to hear! For anyone else having this issue, I'd recommend updating your kernel to 4.18.13 + and also email asrock to fix this issue. The more people that contact Asrock with this issue, the sooner we'll be able to fix this. Usually support will reply saying they don't have support for Linux OS, but reiterate that this is not a Linux issue, it is an issue with Agesa PinnaclePI-AM4_1.0.0.4 and Asrock Bios/UEFI saying supports Secure Encrypted Virtualization(SEV) when the hardware does not. To my knowledge Only AMD EPYC processors support SEV, SME, TSME, and Ryzen Pro Processors supporting only TSME. Bios/UEFI need to stop advertising SEV when the hardware does not even support it. For anyone who wants to get into the nitty gritty of this issue, I'd recommend checking out this Redhat Bug tracker related to this issue: http://bugzilla.redhat.com/show_bug.cgi%3Fid=1608242" rel="nofollow - https://bugzilla.redhat.com/show_bug.cgi?id=1608242
|