Just saying thanks, helped me a lot to identify faulty memory. :)
Search Criteria
Package Details: memtest86-efi 1:11.2build2000-1
Package Actions
| 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: | 113 |
| Popularity: | 0.26 |
| First Submitted: | 2013-10-29 10:25 (UTC) |
| Last Updated: | 2025-02-15 15:21 (UTC) |
Dependencies (3)
- p7zip (p7zip-full-binAUR, p7zip-natspecAUR, 7zip) (make)
- efibootmgr (efibootmgr-gitAUR) (optional) – to add a new EFI boot entry
- grub (grub-coreosAUR, grub-xen-gitAUR, grub-luks-keyfileAUR, grub-silentAUR, grub-gitAUR, grub-grubenv-btrfsAUR, grub-libzfsAUR, grub-improved-luks2-gitAUR) (optional) – to add MemTest86 entry in GRUB2 menu
Required by (0)
Sources (4)
francoism90 commented on 2021-04-25 12:24 (UTC)
Rhinoceros commented on 2021-03-13 08:29 (UTC)
Hi, the latest pkgver bump is actually less than the previous one. You can test with vercmp.
$ vercmp 9.0 9.0build2000
1
This should give -1. You might have to bump epoch if you want to change your PKGBUILD versioning.
UnicornDarkness commented on 2021-02-21 20:41 (UTC)
@leuko: Thanks for your comment. I improved this behavior in 3d058842b163. It is a shame I never run shellcheck on this script before. :)
leuko commented on 2021-02-21 14:37 (UTC)
I had the following error after invoking memtest86-efi --install with EFI entry addition (2. option):
...
Add a new EFI boot entry...
invalid numeric value -w
...
The problem was that I provided the path for my md array. Providing the real device name (/dev/sda instead of /dev/md/mycomp:boot) fixed the issue.
Thank you for this package Xorg!
UnicornDarkness commented on 2020-05-17 10:38 (UTC)
@buzo: My bad, I forgot to push my commits...
UnicornDarkness commented on 2020-01-29 14:50 (UTC) (edited on 2020-01-29 14:50 (UTC) by UnicornDarkness)
@jakub: Ok. BTW, the script tries to mount the partition on the given mount point if the partition is not mounted.
The script has been improved thanks to your feedback.
jakub commented on 2020-01-26 19:25 (UTC)
@Xorg: it seems it's not mounted, which is quite strange as I've set mount point during installation. Anyway, I'll have to sort it out. Thx for hint!
UnicornDarkness commented on 2020-01-26 19:10 (UTC)
@jakub: No, it is not correct. Are you sure /dev/sda1 is mounted? You can check with mount | grep /dev/sda1.
Otherwise, you can enter the mount point manually.
jakub commented on 2020-01-26 19:02 (UTC) (edited on 2020-01-26 19:02 (UTC) by jakub)
➜ ~ sudo memtest86-efi --install
This script is unofficial, written by an AUR (Arch User Repository) user. Use it at YOUR OWN RISK.
Press Enter if /dev/sda1 is your ESP partition, else enter device path manually (like /dev/sdXY):
Press Enter if is your mount point, else enter mount point manually (like /boot/efi):
As you see script did not show anything as "mount point". Is this correct?
UnicornDarkness commented on 2019-09-11 07:00 (UTC)
@capoeira: then run memtest86-efi --install...
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:To avoid this problem, I prefer to reupload
memtest86-usb.ziparchive 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.