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 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

nTia89 commented on 2016-12-17 09:52 (UTC)

@Xorg, your work is amazing and yes in this case will bring "only" a simplified and more ordered file anyhow, it would be a proof of concept and it will bring this package into the new pacman's hook era

UnicornDarkness commented on 2016-12-16 08:09 (UTC)

What is the problem with .install file? :( Ok, I'll try to write a hook, but I'm not sure it will change anything.

zerophase commented on 2016-12-14 15:00 (UTC)

I have a pacman hook I can toss up. Been using it so refind can find the binary.

nTia89 commented on 2016-12-14 10:38 (UTC)

do you plan to switch from .install script to a pacman hook?

Maniaxx commented on 2016-10-03 18:50 (UTC)

Yes, that should work as well but only affects one substitution per backslash whereas single quotes disable it globally (whole cat). I'm not sure why you choose that more error prone way (especially as you don't need substitution at all in the cat process) but its your decision. See Example 19-7. Parameter substitution turned off: http://www.tldp.org/LDP/abs/html/here-docs.html

UnicornDarkness commented on 2016-10-03 15:23 (UTC)

Yes, I understand that, that's why I think using [ "\$grub_platform" = "efi" ] should fix this problem. [ "x" = xefi ] is a nonsense, it should be always false.

Maniaxx commented on 2016-10-02 20:36 (UTC)

What i wanted to tell you is that this exactly happened here. Your script just copied this line: [ "x" = xefi ] and thus broke the condition completely in grub.cfg so the entry could never appear. I'm aware how that x comparison works. It started working properly once the single quotes around EOF were set.

UnicornDarkness commented on 2016-10-02 16:01 (UTC) (edited on 2016-10-02 16:02 (UTC) by UnicornDarkness)

@Maniaxx: Ok, after looking files in /etc/grub.d, I've added missing shebang. cat <<EOF is used is these scripts (I've removed training space before EOF). 'EOF' is not used. In "x${grub_platform}", 'x' is useless. Should be "\$grub_platform" according to other scripts. Changes are pushed. I don't increase pkgrel, due to memtest86-efi script doesn't update configuration.

Maniaxx commented on 2016-09-30 01:31 (UTC) (edited on 2016-09-30 20:02 (UTC) by Maniaxx)

The '86_memtest' script probably should start with #!/bin/sh like all the other scripts in /etc/grub.d (it works anyway though) and there's a bug in the first line (missing single quotes): cat << EOF should be: cat << 'EOF' Otherwise [ "x${grub_platform}" = xefi ] results in [ "x" = xefi ] as ${grub_platform} gets expanded at cat runtime from local environment (that is not set). The single quotes make sure that the text gets copied literally.

zerophase commented on 2016-08-08 16:16 (UTC)

This issue applies to Haswell E chips as well. http://www.passmark.com/forum/memtest86/6061-interesting-issue-running-memtest86-v7-0-free-with-i7-6700k