I have a SER9 AI HX 370, there is a known vulnerability in its CPU instruction set that has prompted newer Linux kernels to disable some CPU functionality. Here is some detail from AMD: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html So when I boot into Linux I see “RDSEED32 is broken, disabling the corresponding cpuid bit” This needs patching in a bios update, such is my understanding after reading around how other manufacturers have dealt with it. I have tried the most recent FW, SER9T407, which did arrive after this problem was widely known. Nonetheless it persists - has anyone else come across this or hit upon a solution? Thank you all, Adrian

adrianhand Hello there, Sorry for the trouble. Could you please send us a picture of SN code(two lines) at the bottom of machine ? Please repeatedly press delete key as soon as you turn on the PC, go to BIOS. Please send us a picture of the Main page, then we will send you the corresponding BIOS file to solve the problem. Have a nice day~

adrianhand Hello there, Please flash the T405 BIOS file to solve the problem. I have sent you the BIOS file, please check your PM. Have a nice day~

Beelink CS-June What about all other Beelink models affected? Currently the GTR9 Pro with the latest BIOS/UEFI P110 has the same AMD vulnerabilities issue and old/unpatched AGESA/microcode (uCode) versions. As discussed on a different thread here . We need updated BIOS/UEFI versions to fix it, please.

jotapesse The EOM file has been sent to your private message.

Beelink CS-Rose Hi! Thank you. That AMD EOM seems to be a Windows only tool. I’m a Linux user and currently do not hold any Windows system install on GTR9 Pro. Could you please provide me with a Linux capable alternative tool, if possible? Anyway, AFAIK, the CPU microcode/AGESA updates should be delivered via BIOS updates, right? Will there be a BIOS update for the GTR9 Pro with those AMD microcode/AGESA updates in the near future?

jotapesse Hello there, We are sorry that at present we do not have the EOM file version available for the Linux version. Regarding the BIOS update issue of GTR9 that you inquired about, we are currently consulting with the R&D team. We will inform you as soon as we receive a reply from the R&D team. Have a nice day~

@jotapesse don’t bother with the EoM tool, I have jumped through these suggested hoops (including installing Windows for it) despite suspecting that they would do nothing, and indeed they didn’t - hopefully you won’t have to waste as much time on this as I have. The EoM tool just flips a “fuse” relating to Firmware Anti Rollback, it doesn’t have anything to do with microcode. I have had it confirmed via DM that there is no fix available, as you have said all along the only way this can get fixed is with a bios update and that isn’t coming. It makes it really easy to recommend against anyone buying a beelink machine, I’ll update this thread if a patch ever comes out but the official line at the moment is “we are currently unable to provide the CPU microcode update you require”.

Any news with this? Same problem here with GTR9 Pro. Where can I download that EOM file?

Also being discussed on this thread … But no reply from Beelink up until now… concerning it is.

RDSEED32 is broken, disabling the corresponding cpuid bit

jotapesse

Beelink CS-June Hi! Several months have passed already since these were reported - AMD vulnerabilities and the lack of BIOS proper CPU microcode (uCode) updates with the latest patched AGESA™ (AMD Generic Encapsulated System Architecture) versions to resolve them on Beelink Mini PCs (such as my GTR9 Pro):

AMD-SB-7033 - AMD CPU Microcode Signature Verification Vulnerability – affects AMD CPUs with Zen 1 up to Zen 5
AMD-SB-7055 - RDSEED Failure on AMD “Zen 5” Processors – affects AMD CPUs with Zen 5 only

What is the status of this with the R&D teams? Any ETA or update? When can we expect it, please?

Beelink CS-Rose

jotapesse

We apologize for the inconvenience. Please contact us at support-pc@bee-link.com for after-sales support.

You can refer to this link: https://buildin.ai/lizong/share/a687a7ed-a7a2-4760-a0b9-fd05c19cd9d7#038ca976-ccfe-4776-bed1-c1134e0ac3e2

adrianhand

@Beelink CS-Rose that is an unrelated issue. We are all asking about security vulnerabilities not about NIC performance. Please advise regards the security vulnerability.

Beelink CS-June

adrianhand and @jotapesse

Hello there,

I inquired of our technical staff that the BIOS solution file for the AGESA issue will not be released until at least mid-May.

Thank you for your understanding and patience.

Have a nice day~

« Previous Page