19

A few days ago I realize that the following message appears when booting Ubuntu 20.04 (it didn't appear before):

[   0.113770] x86/cpu: SGX disable by BIOS.

After a little research I found other people having this "problem". On the cases I saw the OS didn't even boot after that error (it seems because the OS doesn't detect the disks) but that's not my case, my disks are detected correctly and Ubuntu 20.04 starts as nothing happens.

So for me isn't really a problem but I'm concerned that it can turn into one. So I want to know if there's a solution. I searched on my BIOS but I didn't see an option that allows me to enable the SGX.

My Motherboard and CPU are 'MSI H510M Pro-E' and 'Intel Core i5 10400'(I use the integraded graphics, specifically are called 'Intel HD Graphics 630')

Rinzwind
  • 309,379

3 Answers3

24

x86/cpu: SGX disable by BIOS

This message began to appear when you upgraded to kernel 5.13.

SGX stands for "Intel Software Guard eXtensions" and is "a hardware-based isolation and memory encryption mechanism provided by modern Intel® CPUs". In your BIOS you might find a switch with 2 or 3 possible options:

  • Disable: SGX instructions and resources are not available to applications
  • Enable: SGX instructions and resources are available to applications
  • Software Controlled: SGX can be enabled by software applications asking for it

If the option is not there you might get it through a BIOS upgrade. Otherwise, if you want to get rid of the message, add nosgx to the grub defaults (see How do I add a kernel boot parameter? on how to add a parameter). You can also safely ignore the message, as SGX is benign and not necessary.

Rinzwind
  • 309,379
3

On my dual boot Acer laptop, I booted on Windows 11, installed the Intel Software Guard Extensions Activation App and enabled SGX as explained here: https://www.intel.com/content/www/us/en/support/articles/000058952/software/intel-security-products.html.

Nothing new appeared in the BIOS, but the x86/cpu: SGX disable by BIOS. message at boot is now gone.

Flow
  • 2,476
0

For me this hang at SGX was caused by messing with X11/Synaptics config. If you did that, your solution maybe is to delete it's configs through recovery root terminal.

https://askubuntu.com/a/206289 desribes the needed step. You may also revert the changes you've made, seems like a much safer option than deleting it entirely.

I have no idea for why messing with config would have such dire almost untraceable implications. All i did are a couple of changes related to touchpad scroll speed.