Memtest86+-efi

This package is not working for me under systemd-boot using “bit safe” Option 1 during install. Option 4 intended for bootctl fails via command not found which seems to be a bug.

This post provides some guidance but manually creating a configuration file and trying to add it

/efi/loader/entries/memtest86-efi.conf

title  memtest86-efi
efi    /EFI/memtest86/shellx64.efi

bootctl update

does not help.

Any advice? Does anyone have it work? Thanks.

You don’t need this. This updates the bootloader itself. This is run when systemd updates, not when you make changes.

It definitely should not be in the conf file.

Did you copy the appropriate file to this location /efi/EFI/memtest86/shellx64.efi

Select memtest86-efi action to perform:
1: Copy shellx64.efi file on ESP at /EFI/memtest86 (bit safe)
2: Add a new EFI boot entry (more safe)
3: Add a boot entry for GRUB2 menu
4: Add a boot entry for systemd-boot menu
5: Cancel
1

MemTest86 is installed into /efi/EFI/memtest86/ directory.
'/usr/share/memtest86-efi/blacklist.cfg' -> '/efi/EFI/memtest86/blacklist.cfg'
'/usr/share/memtest86-efi/mt86.png' -> '/efi/EFI/memtest86/mt86.png'
'/usr/share/memtest86-efi/unifont.bin' -> '/efi/EFI/memtest86/unifont.bin'
'/usr/share/memtest86-efi/bootx64.efi' -> '/efi/EFI/memtest86/shellx64.efi'
Writting configuration...
MemTest86 has been installed in ESP.

I should mention the hardware is an MSI board that is quirky with esp/efi.

Did you check to see if the files were actually written?

[root@z590 memtest86]# ls -al
total 3708
drwxr-xr-x  3 root root    4096 25. Apr 19:40 .
drwxr-xr-x 13 root root    4096 25. Apr 2023  ..
drwxr-xr-x  2 root root    4096 16. Apr 13:59 Benchmark
-rwxr-xr-x  1 root root    5685 25. Apr 19:40 blacklist.cfg
-rwxr-xr-x  1 root root    6823 25. Apr 19:40 mt86.png
-rwxr-xr-x  1 root root 1405880 25. Apr 19:40 shellx64.efi
-rwxr-xr-x  1 root root 2355408 25. Apr 19:40 unifont.bin

What does cat /efi/loader/entries/memtest86-efi.conf show?

[root@z590 memtest86]# cat /efi/loader/entries/memtest86-efi.conf
title  memtest86-efi
efi    /EFI/memtest86/shellx64.efi

I created it based on the post mentioned above, not sure, if the syntax is right.

What happens. Does it not work or does it not show up in the menu?

It does not show up and thus cannot be run as I do not know how else to run it.

unless you have a folder named EFI inside your efi-partition, remove that EFI in front :wink:

thats how my entry looks like and it works:

cat memtest.conf                                                         
title  Memtest86+
efi     /tools/memtest.efi

Edit: I used the official repo version: https://archlinux.org/packages/extra/any/memtest86+-efi/

1 Like

Most people do have a folder named EFI inside their ESP. i.e. It is mounted at /efi/EFI

OK, some issues are superimposed:

a) wrong package, the right one as mentioned has a plus attached to it
https://archlinux.org/packages/extra/any/memtest86+-efi/

b) looking into journalctl, I found

systemd-logind[511]: /efi/loader/entries/memtest.conf:2: Unknown line 'title ', ignoring.
systemd-logind[511]: /efi/loader/entries/memtest.conf:3: Unknown line 'efi ', ignoring.

The reason was that the package is not installed under /efi but under /boot.

Here is the final procedure to successfully run it:

# note plus
yay memtest86+-efi

$ locate memtest86+

/boot/memtest86+
/boot/memtest86+/memtest.efi
/etc/grub.d/60_memtest86+-efi

mv /boot/memtest86+ /efi/

# .conf, no tabs
sudo nano /efi/loader/entries/memtest.conf

title Memtest86+
efi /memtest86+/memtest.efi

BTW, nice test. :slight_smile:

Won’t work unless you remember to update the database after the memtest install :

sudo updatedb

You might prefer this :

yay -Ql memtest86+-efi

In my case, I didn’t have to do anything after the package install, because my efi partition is mounted on /boot/efi.

1 Like

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