This component is marked as blacklisted for Debian and Ubuntu variants.
This component is marked as blacklisted for Debian and Ubuntu variants.
I mentioned this earlier about a month ago and have since uploaded a video... https://youtu.be/w8r-U2C7UMs. It seems MSI has blocked the SecureBoot shim for Ubuntu and Debian versions of Linux, and I can't find any explanation for why. Also, I'm unsure if it's safe to remove these files without risking damage to the board... I thought about asking the community for advice.
Bricking a BIOS on that board isn't a concern because it includes the "flash back" function. Remove it and check the outcome—likely nothing serious. As for why it might be blacklisted, it probably doesn’t need Linux platforms anyway. Since Windows isn’t essential, the main point is why secure boot remains such a big deal today; it’s been around for years, and people didn’t care until Microsoft pushed W11 users away.
Yeah, this thing would only stop Ubuntu/Debian from booting if Secure Boot is enabled. Once disabled, everything goes! I'm just tired of having to enable/disable the bastard, and ironically enough, I don't think its an actual requirement for Windows 11 on BYOs because I actually stumbled on something quite by accident. When I got sick of Windows 11 not having thumbnails for folders, and went back to restore my Windows 10 image with Macrium Rescue Media, of course I had to disable Secure Boot to boot up my YUMI UEFI multiboot stick that has my Macrium Rescue ISO, right? Yep, so I disable Secure Boot, boot into Macrium Rescue, and get stuck with a 640x480 window that can't be resized. Since it can't be resized, I can't restore the image because confirmation buttons are off screen. Dammit! Have to rebuild the ISO and write to the ... Wait a second ... I can restore my Windows 10 image to my SSD from within Windows 11 because Macrium Reflect will automatically write the recuse environment to a temporary partition and boot off it! So here I am rebooting back into Windows 11 ......... without re-enabling Secure Boot ... and it worked just fine! No warnings. No nothing. Therefore, on BYO rigs, I think Windows 11 only requires Secure Boot for the in-place upgrade or clean install. This is probably NOT the case for Windows 11 pre-builds ...