Package Details: memtest86-efi 1:11.7build1000-1

Git Clone URL: https://aur.archlinux.org/memtest86-efi.git (read-only, click to copy)
Package Base: memtest86-efi
Description: A free, thorough, stand alone memory test as an EFI application
Upstream URL: https://www.memtest86.com
Licenses: GPL2, custom:PassMark
Submitter: UnicornDarkness
Maintainer: UnicornDarkness
Last Packager: UnicornDarkness
Votes: 110
Popularity: 0.35
First Submitted: 2013-10-29 10:25 (UTC)
Last Updated: 2026-05-04 18:17 (UTC)

Dependencies (3)

Required by (0)

Sources (4)

Pinned Comments

UnicornDarkness commented on 2019-06-08 08:52 (UTC) (edited on 2019-06-08 08:53 (UTC) by UnicornDarkness)

As you probably know, the <https://www.memtest86.com/downloads/memtest86-usb.zip> URL is likely to cause problems, like this error:

==> Validating source files with sha512sums...
    memtest86-efi-8.2.zip ... FAILED

To avoid this problem, I prefer to reupload memtest86-usb.zip archive somewhere else, where this kind of breakage will not appear.

I can't upload this archive on AUR directly (archive is 8 MB but AUR accepts 250 KiB maximum), so I decide to put this archive on my Git repository to avoid future breakages.

I hope it suits you.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

yi22588 commented on 2017-11-30 05:38 (UTC)

Can someone tell me how to use this package?

UnicornDarkness commented on 2017-09-04 09:29 (UTC)

@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 (UTC)

Yay. However, have you tested it? I haven't yet, but a quick glace at https://aur.archlinux.org/cgit/aur.git/commit/?h=memtest86-efi&id=b7b5bd892484b09b7bdcd68099727aa838ea2dca 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]/} 013 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.

UnicornDarkness commented on 2017-09-04 08:18 (UTC)

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

moll commented on 2017-08-24 17:49 (UTC) (edited on 2017-08-24 17:49 (UTC) by moll)

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. https://aur.archlinux.org/cgit/aur.git/tree/memtest86-efi?h=memtest86-efi#n98 for example. You can immediately see that the disk name `/dev/nvme0n1` gets cut off at `/dev/nvm` which is not right. ;)

UnicornDarkness commented on 2017-08-17 13:11 (UTC)

@moll: Install script is provided by myself. Can you paste your error, please?

moll commented on 2017-08-14 13:49 (UTC)

Hey, Thanks for the package. I'm not sure where to report this, but the install script fails for non 8-character disks like NVMe, whose 1st partition gets assigned /dev/nvme0n1p1.

zerophase commented on 2017-02-28 04:07 (UTC)

The latest update fixes booting from EFI boot into memtest86, on Asus mobos.

zerophase commented on 2017-01-03 10:35 (UTC)

This is what I use. [Trigger] Operation = Install Operation = Upgrade Type = Package Target = memtest86-efi [Action] Depends = coreutils When = PostTransaction Exec = /usr/bin/cp /usr/share/memtest86-efi/bootx64.efi /boot/EFI/tools/memtest86.efi It needs that name, and needs to be in that folder for rEFInd to detect memtest86.

UnicornDarkness commented on 2017-01-03 06:29 (UTC)

Sorry for delay. I have added hooks. Please tell me if you see something wrong.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 15 Next › Last »