Package Details: memtest86-efi 7.4-3

Git Clone URL: (read-only)
Package Base: memtest86-efi
Description: A free, thorough, stand alone memory test as an EFI application
Upstream URL:
Licenses: GPL2, custom:PassMark
Submitter: Xorg
Maintainer: Xorg
Last Packager: Xorg
Votes: 56
Popularity: 2.150466
First Submitted: 2013-10-29 10:25
Last Updated: 2017-09-04 09:26

Dependencies (3)

Required by (0)

Sources (7)

Latest Comments

Xorg commented on 2017-12-15 07:12

@yi22588: Not exactly. You can't run .efi file on Arch (or on any OS). The memtest86-efi script provides a way to run this .efi file by your UEFI or your bootloader (GRUB2 and systemd-boot are supported).

For instance, I've chosen to add a new boot entry in my UEFI to launch MemTest86. Screenshot:

Your ESP is /dev/sda1. What's wrong with it?

yi22588 commented on 2017-12-05 01:09

@Xorg: Thanks for reply. So this package provides people to run .efi file right?

The command output: /dev/sda1 1 15567 125034839+ ee EFI GPT

Xorg commented on 2017-11-30 17:01

@yi22588: This package doesn't allow you to run MemTest86 on Arch. This package provides an EFI executable. If you want to run this executable, it must be placed in ESP in order to be usable by UEFI.
memtest86-efi is an interactive script written by myself to help people do to this stuff.

Can you paste 'fdisk -l | grep EFI' command output please?

yi22588 commented on 2017-11-30 08:09

@moll I type ./memtest86-efi -i Is it a right move? and if I can't mount ESP, I can't use this package right?

moll commented on 2017-11-30 07:47

@yi22588: Ensure the bootx64.efi file this package installs somewhere (I think it was /usr...) is copied to /boot and boot to it with your favorite bootloader. Arch's Wiki may help configuring your bootloader and where exactly to put it.

yi22588 commented on 2017-11-30 05:38

Can someone tell me how to use this package?

Xorg commented on 2017-09-04 09:29

@moll: Only tested for my SATA device... Stupid naming convention for NVMe devices.
With the last patch, seems good for both SCSI and NVMe naming.

moll commented on 2017-09-04 08:30

Yay. However, have you tested it? I haven't yet, but a quick glace at hints it uses a replacement pattern to strip out non-numbers which will fail for, let's say, the 3rd partition on the first NVMe disk on the first controller:

$ partition=/dev/nvme0n1p3; echo ${partition//[^0-9]/}

Also the latter `${partition//$partnumber}` is not a reliable approach if the controller and disk numbers happen to match.

I think the right way would be to pattern match from the right and assume only the last numeric component is the partition.

Xorg commented on 2017-09-04 08:18

@moll: Sorry for delay, it's fixed now.

moll commented on 2017-08-24 17:49

Xorg: I don't remember the exact error at the moment, but if you look at the install script, it uses Bash string indexing that assumes the disk name is always 8 characters. for example. You can immediately see that the disk name `/dev/nvme0n1` gets cut off at `/dev/nvm` which is not right. ;)

All comments