EFI variables are not supported on this system

vs0x309 · Nov 7, 2024

Hi Guys!
I have been through 7 circles of hell and still have not achieved the desired result. The title of the topic seems quite banal, and there are many answers to my question on the Internet. I actually know how to use Google search. But all this does not work for me.

It is impossible to install any Linux distribution. Only Arch Linux. The problem is that the system is allegedly not loaded in UEFI mode. My laptop does not allow loading in legacy modes.

The GRUB can only be installed with the following parameters: -nonvram or -removable

Fast Boot: Disabled
Secure Boot: Disabled

Do you have any ideas what the problem could be? The system efi is the latest version, updated a week ago. It has been like this since I bought the laptop.

My system: HP ProBook 460 G11 (2024)

efibootmgr: EFI variables are not supported on this system.

By the way, my laptop is on the list of officially supported operating systems Ubuntu 22.04 (Previous version with long-term support)
It installs without errors, but does not register the path to the EFI bootloader file in the nvram of the motherboard. And the operating system has the same problems that I described.
It boots simply because the motherboard sees bootloaders on the hard drive, which have a default location.

gvisoc · Nov 7, 2024

I have a very low confidence gut feeling that the EFI may be operating in legacy compatibility mode, and the drive may have a MBR partition table instead of a GPT.

That would trigger the system to appear to the operating system as a BIOS one instead of a EFI one, just for the sake of being compatible with the drive.

Does that make sense? Would you be able to look out for evidences in your UEFI configuration?

vs0x309 · Nov 7, 2024

Thanks for answer. There are no settings in the BIOS: Legacy, Bios, CSM modes... Only UEFI. In system boot menu flash drive and my nvme looks as UEFI

lsblk:

Code:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 953.9G  0 disk
├─nvme0n1p1 259:1    0     1G  0 part /boot
└─nvme0n1p2 259:2    0 952.9G  0 part /

cfdisk:

Code:

                                     Disk: /dev/nvme0n1
                 Size: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
                Label: gpt, identifier: 884FC092-DAD7-4CA2-B09A-BE9B9B7964E1

    Device                Start           End       Sectors      Size Type
>>  /dev/nvme0n1p1         2048       2099199       2097152        1G EFI System            
    /dev/nvme0n1p2      2099200    2000407215    1998308016    952.9G Linux root (x86-64)





 ┌────────────────────────────────────────────────────────────────────────────────────────┐
 │ Partition UUID: C8A7A600-9BF3-440D-9925-A55DA551ABCB                                   │
 │ Partition type: EFI System (C12A7328-F81F-11D2-BA4B-00A0C93EC93B)                      │
 │Filesystem UUID: EFA0-38D7                                                              │
 │     Filesystem: vfat                                                                   │
 │     Mountpoint: /boot (mounted)                                                        │
 └────────────────────────────────────────────────────────────────────────────────────────┘
     [ Delete ]  [ Resize ]  [  Quit  ]  [  Type  ]  [  Help  ]  [  Write ]  [  Dump  ]

Brickwizard · Nov 7, 2024

It may be that it is too new and not all components are being recognised, try MX Linux with AHS and see if that works

Condobloke · Nov 7, 2024

AS old as this thread may be there may be some joy there for you.....maybe ?

"EFI variables are not supported on this system"

I am attempting to install Arch linux to a new (and very crappy) HP Pavillion 15 Notebook. This is a UEFI-based machine. After several swings at it, I have managed to get pretty far. Legacy mode...

unix.stackexchange.com

vs0x309 · Nov 7, 2024

Thanks for the answers, Linux experts!

Brickwizard said:
It may be that it is too new and not all components are being recognised, try MX Linux with AHS and see if that works

Just tried this. Loaded it on my flash drive with the Ventoy app
Still the same. sudo efibootmgr -v --- EFI variables are not supported on this system

Condobloke said:
AS old as this thread may be there may be some joy there for you.....maybe ?

"EFI variables are not supported on this system"

I am attempting to install Arch linux to a new (and very crappy) HP Pavillion 15 Notebook. This is a UEFI-based machine. After several swings at it, I have managed to get pretty far. Legacy mode...

unix.stackexchange.com

I have seen this information before. Unfortunately, these methods do not help.

By the way, this is what the boot menu looks like

KGIII · Nov 7, 2024

If it's UEFI, you should probably have a /boot/efi mounted partition.

I'm not seeing that in the output above.

Not that this reply is much help, but it might be worth looking into.

vs0x309 · Nov 8, 2024

KGIII said:
If it's UEFI, you should probably have a /boot/efi mounted partition.

I'm not seeing that in the output above.

Not that this reply is much help, but it might be worth looking into.

No problems. Now this looks as:

lsblk

Code:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 953.9G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
├─nvme0n1p2 259:2    0   1.5G  0 part /boot
└─nvme0n1p3 259:3    0   400G  0 part /

df -h

Code:

Filesystem      Size  Used Avail Use% Mounted on
dev              16G     0   16G   0% /dev
run              16G  1.9M   16G   1% /run
/dev/nvme0n1p3  393G  6.6G  367G   2% /
tmpfs            16G   49M   16G   1% /dev/shm
tmpfs            16G   14M   16G   1% /tmp
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-udev-load-credentials.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-sysctl.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-sysusers.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-vconsole-setup.service
/dev/nvme0n1p2  1.5G  168M  1.2G  13% /boot
/dev/nvme0n1p1  511M   15M  497M   3% /boot/efi
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs           3.1G  160K  3.1G   1% /run/user/1000

I don't think it matters. It happens on every LiveCD or installed system we see now.

APTI · Nov 8, 2024

vs0x309 said:
Hi Guys!
I have been through 7 circles of hell and still have not achieved the desired result. The title of the topic seems quite banal, and there are many answers to my question on the Internet. I actually know how to use Google search. But all this does not work for me.

It is impossible to install any Linux distribution. Only Arch Linux. The problem is that the system is allegedly not loaded in UEFI mode. My laptop does not allow loading in legacy modes.

The GRUB can only be installed with the following parameters: -nonvram or -removable

Fast Boot: Disabled
Secure Boot: Disabled

Do you have any ideas what the problem could be? The system efi is the latest version, updated a week ago. It has been like this since I bought the laptop.

My system: HP ProBook 460 G11 (2024)

efibootmgr: EFI variables are not supported on this system.

By the way, my laptop is on the list of officially supported operating systems Ubuntu 22.04 (Previous version with long-term support)
It installs without errors, but does not register the path to the EFI bootloader file in the nvram of the motherboard. And the operating system has the same problems that I described.
It boots simply because the motherboard sees bootloaders on the hard drive, which have a default location.

go into the system bios and make sure that it is not restricted to windows only. You will have to look into each area of bios and make sure that protection for the OS is not turned on. Sometimes you will see an OS install option that has to be turned on or a protection turned off.
The next thing is make sure the drive has no partitions on it. delete all of them. I am of course assuming that you only want linux and not a dual boot.
I will suggest trying to download Fedora from fedoraproject.org, I think there is a link on this site to it also. Download the workstation version and put it on a usb drive. Not copied on but use something like mediawriter or any of the others that creates a UEFI bootable flash drive. Then boot off the USB drive. You can test the live version and delete drive partitions using utilities/disk.
You will have an option to install to the drive. Fedora is pretty up to date just like ubuntu is. If you boot the usb in UEFI mode it will install UEFI mode. Once it is done, shut down, remove the USB drive and turn it on. Then see what you get.
I refurbish many systems and the one you mention should work fine but I think the key is to go over every entry in the BIOS and make sure nothing there is set to block an OS install. Sometimes the security is set to not allow MBR or UEFI changes. It is to protect the OS from malicious attacks but also stops you from installing the OS.

vs0x309 · Nov 8, 2024

APTI said:
go into the system bios and make sure that it is not restricted to windows only. You will have to look into each area of bios and make sure that protection for the OS is not turned on. Sometimes you will see an OS install option that has to be turned on or a protection turned off.
The next thing is make sure the drive has no partitions on it. delete all of them. I am of course assuming that you only want linux and not a dual boot.
I will suggest trying to download Fedora from fedoraproject.org, I think there is a link on this site to it also. Download the workstation version and put it on a usb drive. Not copied on but use something like mediawriter or any of the others that creates a UEFI bootable flash drive. Then boot off the USB drive. You can test the live version and delete drive partitions using utilities/disk.
You will have an option to install to the drive. Fedora is pretty up to date just like ubuntu is. If you boot the usb in UEFI mode it will install UEFI mode. Once it is done, shut down, remove the USB drive and turn it on. Then see what you get.
I refurbish many systems and the one you mention should work fine but I think the key is to go over every entry in the BIOS and make sure nothing there is set to block an OS install. Sometimes the security is set to not allow MBR or UEFI changes. It is to protect the OS from malicious attacks but also stops you from installing the OS.

Thanks for answer.

I also plan to use Windows as a second system. But for now I want to figure out why my new laptop behaves this way. My old computer also has 2 systems installed with efi, Windows and Linux. It works for me, and I have experience setting it up.

I tried installing Fedora, it gives an error in the first seconds of installation. Used programs for recording the installation image, such as: Ventoy and Rufus. I use GPT partitioning of disks and flash drives.

I will try to record a video of what the BIOS looks like. There I also experimented and disabled a lot of things.

APTI · Nov 8, 2024

vs0x309 said:
Thanks for answer.

I also plan to use Windows as a second system. But for now I want to figure out why my new laptop behaves this way. My old computer also has 2 systems installed with efi, Windows and Linux. It works for me, and I have experience setting it up.

I tried installing Fedora, it gives an error in the first seconds of installation. Used programs for recording the installation image, such as: Ventoy and Rufus. I use GPT partitioning of disks and flash drives.

I will try to record a video of what the BIOS looks like. There I also experimented and disabled a lot of things.

Set the BIOS to default then go through it. Keep in mind that dual booting is often broken by updates especially windows firmware updates.

Egzoset · Nov 8, 2024

'YUMi-exFAT' (Ventoy) spares my sanity and i got these two on it: ArchLinux, Endeavour. Guess what, they're the exception which happens to stall hard if i dare try its « Boot in normal mode » option, as i get a red warning message about « Init not found » then can't access TTY...

But if i use its « Boot in grub2 mode » then that's OKay - well, at least in the begining i think. Anyway, looking closer at these two .ISOs i can't but notice a different structure with SysLinux present. All i could find that compares somewhat was Porteus v5.01 though this one ain't showing any trace of GrUB/GrUB2 or i'm not searching deep enough. Maybe that's a hint linked to Ventoy, another hint might come from 'rEFInd' shich i always install on a dedicated ESP of its own when dealing with UEFi systems.

What's nice with GrUB is that even if it won't find its .cfg one would still get access to its CLI...

Brickwizard · Nov 8, 2024

I have just finished converting my Dell to NVMe and had a similar problem
if you can get any linux boot terminal to run try
$ journalctl -b | grep ASPM
ASPM was my problem

vs0x309 · Nov 8, 2024

Brickwizard said:
I have just finished converting my Dell to NVMe and had a similar problem
if you can get any linux boot terminal to run try
$ journalctl -b | grep ASPM
ASPM was my problem

This seems to be ok, but there are a number of other problems.

Code:

[slava@hp460g11 ~]$ journalctl -b | grep ASPM
Nov 08 11:02:42 hp460g11 kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]

[slava@hp460g11 ~]$ sudo dmesg --level err
[sudo] password for slava:
[    3.350077] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
[    3.350319] intel_vpu 0000:00:0b.0: probe with driver intel_vpu failed with error -2
[    3.361262] ioremap error for 0x0-0x1000, requested 0x2, got 0x0
[    3.669073] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[    3.835151] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[    4.770378] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
[    5.072248] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    5.086057] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode

[slava@hp460g11 ~]$ sudo dmesg --level warn
[    0.144629]   #2  #4  #5  #7
[    0.626522] pnp 00:04: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
[    0.626525] pnp 00:04: disabling [mem 0x00000000-0x00000fff] because it overlaps 0000:00:02.0 BAR 7 [mem 0x00000000-0x06ffffff 64bit pref]
[    0.713134] hpet_acpi_add: no address or irqs in _CRS
[    0.851249] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.962150] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    3.340083] resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcffff], which spans more than pnp 00:04 [mem 0xfedc0000-0xfedc7fff]
[    3.340087] caller igen6_probe+0x15e/0x7c0 [igen6_edac] mapping multiple BARs
[    3.350193] intel_vpu 0000:00:0b.0: [drm] ivpu_hw_power_down(): NPU not idle during power down
[    3.361271] intel_pmc_core INT33A1:00: Assuming a default substate order for this platform
[    3.432296] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.547614] hp_wmi: query 0x4 returned error 0x5
[    3.566457] ACPI Warning: \_SB.PC00.XHCI.RHUB.HS10._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20240322/nsarguments-61)
[    3.896885] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred
[    4.097941] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
[   20.609307] block nvme0n1: No UUID available providing old NGUID

Brickwizard · Nov 8, 2024

vs0x309 said:
3.350077] intel_vpu 0000:00:0b.0: [drm] ERROR ivpu_fw_request(): Failed to request firmware: -2

After doing some searching, it Looks like it may be a problem with intel-fw-npu I can't help with rectifying any fault with kernel problems

vs0x309 · Nov 8, 2024

Brickwizard said:
After doing some searching, it Looks like it may be a problem with intel-fw-npu I can't help with rectifying any fault with kernel problems

Thanks. Do you think this is the main problem?

Brickwizard · Nov 8, 2024

Im just going by your dmesg report if I had to guess I would say the problem is with the Intel wi-fi drivers

Aristarchus · Nov 9, 2024

I think that the dmesg errors are not related to efi issues and benign
Try
modprobe efivars

..and the try to re-build initrd with efivarfs module and add to /etc/fstab this

efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 0

Alexzee · Nov 9, 2024

Brickwizard said:
After doing some searching, it Looks like it may be a problem with intel-fw-npu I can't help with rectifying any fault with kernel problems

n/m

Alexzee · Nov 9, 2024

vs0x309 said:
Thanks. Do you think this is the main problem?

FWIW, the Intel NPU is new generation neural processing unit for certain types of AI workloads.
Maybe look into telling the kernel a parameter and see if that helps?

Have a look at Intel's website and see if there are drivers for your nic.
Also, Install or Update the NPU driver for Linux. (that is if the driver isn't already installed)

Releases · intel/linux-npu-driver

Intel® NPU (Neural Processing Unit) Driver. Contribute to intel/linux-npu-driver development by creating an account on GitHub.

github.com

Information about NPU here:

Quick overview of Intel’s Neural Processing Unit (NPU) — Intel® NPU Acceleration Library documentation

I'll check back later....gotta go to work-

EFI variables are not supported on this system

New Member

Attachments

Well-Known Member

New Member

Well-Known Member

Well-Known Member

New Member

Attachments

Super Moderator

New Member

Well-Known Member

New Member

Well-Known Member

Active Member

Well-Known Member

New Member

Well-Known Member

New Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member