Issues with motherboard BIOS issues appearing on Ubuntu

Hi. bought a new desktop with a ASRock B760M Pro RS/D4 and a 12th Gen Intel® Core™ i9-12900KF × 24 CPU, however after transferring my hard drive to my new desktop,nearly all hardware security checks which I have listed at the end of this topic. It seems that I contacted ASRock over this and they recommended reinstalling the operating system which I did, but the results are the same. Seems that ASRock recommended that I contact Ubuntu directly which brings me here. Most troubling of the settings seems that the motherboard is in manufacturing mode which really creeps me out. Is there a conflict between the motherboard and Ubuntu? Let me know if you have any ideas or need more details. I’ll provide what I canwith the latter.

Below is the Device Security Report.
Device Security Report

Report details
Date generated: 2025-08-29 15:29:04
fwupd version: 2.0.7

System details
Hardware model: ASRock B760M Pro RS/D4
Processor: 12th Gen Intel(R) Core™ i9-12900KF
OS: Ubuntu 25.04
Security level: HSI:0! (v2.0.7)

HSI-1 Tests
UEFI Platform Key: Pass (Valid)
Firmware BIOS Region: ! Fail (Not Locked)
UEFI Bootservice Variables: Pass (Locked)
TPM v2.0: Pass (Found)
Intel Management Engine Version: Pass (Valid)
Firmware Write Protection Lock: ! Fail (Not Enabled)
Platform Debugging: Pass (Not Enabled)
Intel Management Engine Manufacturing Mode: ! Fail (Not Locked)
UEFI Secure Boot: Pass (Enabled)
BIOS Firmware Updates: Pass (Enabled)
Firmware Write Protection: Pass (Not Enabled)
Intel Management Engine Override: Pass (Locked)
TPM Platform Configuration: Pass (Valid)

HSI-2 Tests
Intel BootGuard Fuse: ! Fail (Not Valid)
Intel BootGuard Verified Boot: ! Fail (Not Valid)
Intel BootGuard ACM Protected: ! Fail (Not Valid)
Intel BootGuard: Pass (Enabled)
TPM Reconstruction: Pass (Valid)
IOMMU Protection: Pass (Enabled)
Platform Debugging: Pass (Locked)

HSI-3 Tests
Intel BootGuard Error Policy: ! Fail (Not Valid)
Pre-boot DMA Protection: Pass (Enabled)
Suspend To RAM: ! Fail (Enabled)
Control-flow Enforcement Technology: Pass (Supported)
Suspend To Idle: ! Fail (Not Enabled)

HSI-4 Tests
Encrypted RAM: ! Fail (Not Supported)
Supervisor Mode Access Prevention: Pass (Enabled)

Runtime Tests
Linux Swap: ! Fail (Not Encrypted)
Firmware Updater Verification: Pass (Not Tainted)
Control-flow Enforcement Technology: Pass (Supported)
Linux Kernel Verification: ! Fail (Tainted)
Linux Kernel Lockdown: Pass (Enabled)

Host security events

For information on the contents of this report, see Redirecting to https://fwupd.github.io/libfwupdplugin/hsi.html

1 Like

maybe check if there are linux drivers on your brand pc, but it seems that maybe uefi needs its windows settings be turned on(this report then should be new on kernel update)… amid some HSI Tests failing as they are not Ubuntu Ready for First Install, and also Network Administrator needs maybe some admission for your approval and maybe some licensing if required for compatibility with Android and similars.

Hmmm. The “UEFI windows settings?” Where can I find that?

That’s a curiously-phrased question.
From a software (Ubuntu) standpoint, a hardware “conflict” would typically mean that the software simply could not load or run.

That’s curious advice, as changing the operating system rarely has any effect on hardware.

Your link leads to…

ME not in manufacturing mode

There have been some unfortunate cases of the ME being distributed in manufacturing mode.

In manufacturing mode many features from the ME can be interacted with that decrease the platform’s security.

Impact:

If the ME is in manufacturing mode then any user with root access can provision the ME engine with new keys.

This gives them full access to the system even when the system is powered off.

Resolution: Contact your OEM, who may be able to issue a firmware update.

It seems like you might be asking two questions:

  1. How to mitigate these hardware vulnerabilities in daily use?

  2. How Ubuntu can help mitigate these hardware vulnrabilities?

Is that accurate? Or are you asking something else?

Well, as I said being stuck in manufacturing is the main concern I have here, though I contacted ASRock, the company that made the motherboard and they said it could be the OS being at fault here. From what hifron said earlier it could be that the UEFI needs the Windows settings turned and mentioned something about a kernel update. This is certainly new territory for me.

Edit Update:
I just updated the Kernel to the latest version. Still no change. I guess updating the kernel is at least something.

Second Edit Update:
Seems that I restarted the system and for what ever reason my desxktop doesn’t like the new Kernel. It says:
Quote
Loading Linux 6.16.4-061604-generic …
error: bad shim signature.
Loading initial ramdisk …
error: you need to load the kernel first.
Unquote

It seems you turn UEFI Secure boot on, but have installed Ubuntu with it off. You may be able to update, but if new install, easier to just reinstall with Secure Boot on.

Fwupdate is a tool to update UEFI firmware. It now also can run a check on settings. But most motherboard manufacturers do not provide firmware for updates, many laptop mfgs do.

Devices using LVFS for firmware updates
https://fwupd.org/lvfs/devicelist

Often updating UEFI, reverts settings to vendor defaults. If you change settings, you have to redo them. My old motherboard required 6 or 7 settings changed with every updates. My newer Dell laptop automatically udpates with Dell, and does not need any settings changed, if I want Secure Boot on.

I think manufacturer mode, just means you can update UEFI settings.

1 Like

Just tried a clean install followed by an update on the Kernel. Same issue.

Have you updated firmware for both UEFI & SSDs?

Have you tried with both UEFI Secure boot on & with it off. It should work with it on, but some just have issues.

Some typical settings you may want to review.
UEFI settings tea-for-one

I tried the firmware update, but nothing says it’s updatable.

Only some vendors & even then only some models are supported with fwupdate. You can use Windows if dual booting, or most vendors have instructions on downloading the update file into a FAT32 partition and updating from there or a DOS type bootable flash drive with update files.

Some systems have added locks on UEFI updates/changes. Check UEFI settings. Often better to download manual for more explanation that what little is inside UEFI itself.

1 Like

Seems the operating system finally noticed a firmware update, but it seems to not be installing.

There is a current server problem. See https://askubuntu.com/questions/1555546/why-am-i-unable-to-update-ubuntu-right-now-september-5-2025-incident

1 Like

Good news. I finally was able to disable secure boot and the updates installed properly with most of the security risks gone. All that’s left is the Linux Kernal Verification.

don’t know why - there is gnome firmware and sign option… fwupdmgr --help as cmd when something does not show up in snap version of gnome firmware to snap package change.

Note that this is not an Ubuntu kernel (the version looks like it is one of the debug kernels from the mainline PPA which should not be used in production (there are tons of security patches missing, the config is wrong and installing such a kernel disables kernel updates for good) these kernels are solely for the case where a kernel team member asks you in a bug to temporarily install them to verify if a bug is fixed in a mainline release (and then remove them again immediately))…

Also see the bold warning in the first paragraph from the Ubuntu kernel team at:

https://wiki.ubuntu.com/Kernel/MainlineBuilds

2 Likes

Can you fill me in more. I tried updating again with fwupdmgr, but no new version exists.
Screenshot From 2025-09-07 13-34-07

Update:I also ran some commands to update again to the latest stable verson. Figured i’d give it a second chance. I’m rebooting now.
https://askubuntu.com/questions/1388115/how-do-i-update-my-kernel-to-the-latest-one

Second update:No good. Results are the same.

Behind this link is extremely ill advice, please do not link it here …

1 Like

Sorry man. What would you recommend command line wise to fix this?

I do not have any recommendation here and it is up to you to decide to drop all security from your system at the very core by installing a mainline kernel that does not have the security options set or patches applied a normal supported Ubuntu kernel provides, your system, your choice …

I’m just asking that you do not spread links to instructions that might lead others to installing a mainline kernel without knowing what they get themselves into. If you put a link like the above in one of your posts here, please add a big disclaimer so people reading along do understand the massive security hole they open on their system when following it.

2 Likes

Sorry. Didn’t intend to post a link with risk info. Any idea where I can download the mainline kernel. Seems like this issue is coming to a close.

Update:I may get some heat over this, but I came across a video on installing mainline kernels. Based on what the video advises i’m supposed to install and uses the latest “long term” kernel rather than the flat out newest one.
https://www.youtube.com/watch?v=AV6sk_8IBME

I tried the latest mainnline(6.12.45 I currently only can use 6.14.29-0) version marked as “longterm.” Still no luck. Same message as the latest version

1 Like