EFI variables are not supported on this system

I don't see an EFI system partition (aka fat) in there.

1 Like

Just about all modern motherboards come with a UEFI now ─ a genuine legacy BIOS is not installed anymore ─ but just because you have a UEFI does not mean that you installed Manjaro in UEFI mode.

The error message you're seeing is telling you that Manjaro was installed in CSM (alias "legacy BIOS compatibility") mode. And if your UEFI is set up with both UEFI and CSM support, then the Manjaro installer will prefer the latter on some motherboards. It did on mine, which was set to "UEFI + CSM" by default, and I had to disable CSM to have Manjaro install itself in UEFI mode and recognize my EFI System Partition ─ which is where the efivars are stored.

[mak@manjaro ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
dev             3.9G     0  3.9G   0% /dev
run             3.9G  1.4M  3.9G   1% /run
/dev/sda2        30G   16G   13G  55% /
tmpfs           3.9G  209M  3.7G   6% /dev/shm
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
tmpfs           3.9G   43M  3.8G   2% /tmp
/dev/sda1       549M   69M  481M  13% /boot/efi
tmpfs           785M   32K  785M   1% /run/user/1000
/dev/sda3        30G   20G  8.8G  69% /run/media/mak/618d6b23-1d71-42c7-ab2e-e17543d413e2
/dev/sda6       134G   41G   87G  32% /run/media/mak/0d290645-2d8e-400c-a787-ab5698bf4886
/dev/sda4        30G  5.7G   23G  21% /run/media/mak/7c10aa52-cd83-4237-aa4a-e1ad41b97212
[mak@manjaro ~]$

So that output means:

1. You don't have an EFI system
You installed Manjaro in legacy mode.

What's the output on any of your other Linuxes? (Lots of Ubuntu and little Manjaro experience here)


(Edited after reading your second output)

/dev/sda1 is the EFI partition.
So this should work.

Can you post /etc/fstab ?

Only if Manjaro was installed in UEFI mode. The other operating systems on his machine may have been, but from the looks of it, he installed Manjaro in BIOS mode. :man_shrugging:

# /dev/sda2
UUID=abee32ce-60b8-4050-9aaf-862c00aeb10c	/         	ext4      	rw,noatime,discard	0 0

# /dev/sda1
UUID=00D6-33B1      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 0

# /dev/sda5
UUID=186ded84-e151-41dd-bee1-8dadefef1d83	none      	swap      	defaults,pri=-2	0 0

That, and because of the way Manjaro handles microcode, it has to be the one to handle the boot loader.

What OS are you running the efibootmgr from?
Please tell me Manjaro.



Looks indeed like a hybrid BIOS/EFI system. What's the output of sudo efibootmgr --verbose on any of the other Linuxes?

1 Like

There are also these reasons for it not working:

1 Like

I have one of those systems so I drop in an EFI shell regularly, but then it wouldn't allow anything to boot that didn't come pre-installed with he system...

1 Like

The linux installed on the other partition is also a manjaro based flavor (Plasma)

The efibootmgr works there. Here is the output:

[mak@jmak-pc ~]$ efibootmgr --verbose
BootCurrent: 0001
Timeout: 6 seconds
BootOrder: 0001,0002,0004,0008,0003,0005,0006
Boot0000* Windows Boot Manager  HD(2,GPT,398a36de-922e-4971-a348-0e54190b93bb,0xe2000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}....................
Boot0001* manjaro       HD(1,GPT,00004903-56b3-476d-a47a-3c507d3f94f6,0x800,0x113000)/File(\EFI\manjaro\grubx64.efi)
Boot0002* deepin        HD(1,GPT,00004903-56b3-476d-a47a-3c507d3f94f6,0x800,0x113000)/File(\EFI\deepin\shimx64.efi)
Boot0003* UEFI:CD/DVD Drive     BBS(129,,0x0)
Boot0004* Wayfire       HD(1,GPT,00004903-56b3-476d-a47a-3c507d3f94f6,0x800,0x113000)/File(\EFI\Wayfire\grubx64.efi)
Boot0005* UEFI:Removable Device BBS(130,,0x0)
Boot0006* UEFI:Network Device   BBS(131,,0x0)
Boot0007* UEFI:Network Device   BBS(131,,0x0)
Boot0008* rEFInd Boot Manager   HD(1,GPT,00004903-56b3-476d-a47a-3c507d3f94f6,0x800,0x113000)/File(\EFI\refind\refind_x64.efi)
[mak@jmak-pc ~]$

So the other Manjaro was installed in BIOS compatibility mode.

AFAIK, you're in for a reinstall on that one. Ensure you mount /boot/efi correctly during the re-install.

Sorry! :sob:

1 Like

OK. I guess, that is what I have to do.


After that works, please don't forget to come back here and mark this thread as solved by pushing the "Solution" button on the answer that helped most as per below screenshot.


We thank you! :innocent:

1 Like

I won't reinstall it right now, I wait till the brand new deepin update comes out hopefully within a few weeks.

Manjaro's a rolling release distribution, why would you need to wait?
Don't tell me your one of those, reinstall the OS every time an updated ISO is released?
I don't think I've re-installed my main system since I bought it (September 2018).
My office server has had Manjaro installed since June 2016.
My Laptop was installed in October 2014.

fs=$(df / | tail -1 | cut -f1 -d' ') && sudo tune2fs -l $fs | grep created

sudo dumpe2fs /dev/sdxX | grep 'Filesystem created:'

sudo tune2fs -l /dev/sdxX | grep 'Filesystem created:'

sudo ls -alct /

or even better yet on an arch based system:
head -n1 /var/log/pacman.log

1 Like

I know that.

The distro works perfectly other than this small glitch. So I am not in a rush.

1 Like

That's fine!
But if you want to know what kind of system you have (UEFI or MSDOS), you can either check at grub prompt (if using grub)

grub> echo $grub_platform

If output is pc , you've booted up in bios-legacy.
If output is efi , you've booted up in uefi.

Or verify update-grub finds all other systems (given they are UEFI) in the menu (os-prober search).

As others already said, you may have installed in MSDOS-Legacy mode, unless there is something else.
Previous reports only speculate for this. If you want to be sure, try what's proposed...
Good reference tutorial.

Have fun (playing with Linux)!! :laughing:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by