Package Details: memtest86-efi 8.0-2

Git Clone URL: https://aur.archlinux.org/memtest86-efi.git (read-only)
Package Base: memtest86-efi
Description: A free, thorough, stand alone memory test as an EFI application
Upstream URL: http://www.memtest86.com
Licenses: GPL2, custom:PassMark
Submitter: Xorg
Maintainer: Xorg
Last Packager: Xorg
Votes: 69
Popularity: 1.978238
First Submitted: 2013-10-29 10:25
Last Updated: 2018-12-07 13:17

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Xorg commented on 2018-12-07 13:21

@feral_hedgehog: Fixed, thanks.

feral_hedgehog commented on 2018-12-07 13:05

I've been having issues with the grub entry install option after the latest update. The 86_memtest file that gets created under /etc/grub.d isn't executable and is missing a backslash before the '$' in the if-statement, which prevents the entry from being added to grub.

Xorg commented on 2018-07-05 19:14

@park0kyung0wo: I would say no. Software cannot damage hardware, but overheat and brutal shutdowns can.

park0kyung0won commented on 2018-07-04 20:53

Oh I see thanks for the reply

I'm asking for I do not know much about low level efi things, Can efi firmwares like memtest damage my hardware?... I hope not :(

Xorg commented on 2018-07-04 16:12

@park0kyung0won: I'm sorry, I can't help you: it's not a packaging issue.

If you shutdown your computer safely under MemTest86, it may be an upstream bug.

I suggest you to contact PassMark Support[3] or try MemTest86 forum[4].

[3] https://www.passmark.com/support/index.htm

[4] https://www.passmark.com/forum/memtest86

park0kyung0won commented on 2018-07-04 12:02

Hello

I have encountered a problem while using this package. I installed this memtest86-efi package, with option of adding entry to systemd-boot list. I aborted memtest in the middle(no particular reason, I couldn't wait), and booted back to Arch Linux. Then I got an error from S.M.A.R.T that my nvme SSD device has been degraded, which Arch Linux is installed. I had one "Media and Data Integrity Errors" on S.M.A.R.T record of that nvme SSD drive.

I was curious so I've conducted tests. Everytime I do memtest, that "Media and Data Integrity Errors" count increased by one, and that integrity error made status of my nvme SSD degraded. So I highly suspect this memtest was a cause...

buzo commented on 2018-02-27 19:33

Looks good, thanks for the quick fix!

Xorg commented on 2018-02-27 19:09

Ok, done in following commit: a1c4551125f1

Tell me if you encounter issue. And if you have a better idea than p7zip to extract .img file...

Xorg commented on 2018-02-27 18:16

@buzo: Try to delete the ISO file by yourself.

Ok, switched from md5sums to sha512sums. I found an upstream FTP, but that is the USB version, ISO seems not present: https://www.passmark.com/ftp/memtest86-usb-7.5.1001.tar.gz I'll investigate.

buzo commented on 2018-02-27 13:49

Now I get a validity check error because memtest86-efi-7.5-1-x86_64.pkg.tar.xz is still there, so makepkg does not download the new version. This is broken. I think the file should be renamed after download. (And upstream should add a version number to the file name.)

And I agree, MD5 is outdated and not secure. Please switch to a modern hash (sha256sum for instance) while you are at it.