You are not logged in.
Hello
Arch Linux x86_64
Host: B650 Pro RS
Kernel: Linux 6.18.3-arch1-1
CPU: AMD Ryzen 7 7700 (16) @ 5.39 GHz
GPU 1: AMD Radeon RX 6600 XT
I have an MB Asrock B650 pro RS, running their BIOS 3.5 all is perfect
If I update to the latest version 4.03, Arch shows a message at boot "EFI stub: Warning: unable to unprotect memory range"
But it boots and runs as normal
For info, secure boot is disabled, and I cleared Secure Boot keys as I saw a similar post, but that again didn't change anything
Any ideas if this is due to the kernel or the BIOS ?
I suppose it's the BIOS and not Arch, or rather the kernel, but often I always get good answers or pointers to fixing problems
For the moment, I've reflashed back to their 3.50 BIOS
I've posted the same question on the Asrock forums
Last edited by Trevor_B (2026-01-07 15:36:12)
Offline
the correct error message is "unable to unprotect memory" - please update the topic
searching with the correct error message I found this: https://github.com/torvalds/linux/blob/ … x86-stub.c - so this is an error specific to efi-stub
it's a very wild guess but from what's in that file it maybe has something to do with the general kernel address space randomization
plugging "linux efi stub unable to unprotect memory range" into google comes up with: SecureBoot, TPM, firmware bug
wild guess: asrock changed something in the newer update which doesn't play nice with boot linux via efi-stub - and linux complains about it
this is nothin arch specific but rather about how you boot and a likely faulty uefi
reporting this to asrock is general the right way (please link the topic on the asrock forums - and add a link to this topic there) - but it's unlikely asrock devs will see any importance in fixing it
my recommend: update and ignore the warning - as there'S not much you can do - as the agesa update is quite an important security update you should apply no matter if using secureboot or the (f)tpm
Offline
the correct error message is "unable to unprotect memory" - please update the topic
reporting this to asrock is general the right way (please link the topic on the asrock forums - and add a link to this topic there) - but it's unlikely asrock devs will see any importance in fixing it
my recommend: update and ignore the warning - as there'S not much you can do - as the agesa update is quite an important security update you should apply no matter if using secureboot or the (f)tpm
Hello
Typo corrected
Asrock forums done, but like you, I don't think they will do anything. I'll wait until the next BIOS update to see what happens
Thanks
Offline
It's defenetly a problem with the latest BIOS Version (4.03).
Same Problem here on an Asrock Taichi Lite X870E.
Offline
It's defenetly a problem with the latest BIOS Version (4.03).
Same Problem here on an Asrock Taichi Lite X870E.
I sent an email to Asrock Asrock_TSD@asrock.com.tw and actually received a reply
"Thank you for your email.
Our BIOS team is checking on this case, and we will contact you again if we have any new information.
All the best,
ASRock TSD"
Fingers crossed that they'll actually look into it
Offline
well - at least you didn't got the usual "we don't support linux"
Offline
It's defenetly a problem with the latest BIOS Version (4.03).
Same Problem here on an Asrock Taichi Lite X870E.
I received a version to test from Asrock this morning by mail, and it works
@Boogleix, if you want a copy, PM me
Bravo Asrock, that's dammed good customer service
Offline
sharing a rom with a different board and bios won't work (and likely declined by the flash utility)
but yea - one of the few times a board oem responded in such way to some regular linux customer
often beta version are only send to known people like LTT
Offline