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. ;)
Search Criteria
Package Details: memtest86-efi 1:11.1build1000-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.119473 |
First Submitted: | 2013-10-29 10:25 (UTC) |
Last Updated: | 2024-10-31 09:57 (UTC) |
Dependencies (3)
- p7zipAUR (p7zip-natspecAUR, p7zip-full-binAUR, 7-zip-fullAUR, 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-improved-luks2-gitAUR, grub-grubenv-btrfsAUR, grub-libzfsAUR) (optional) – to add MemTest86 entry in GRUB2 menu
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 15 Next › Last »
moll commented on 2017-08-24 17:49 (UTC) (edited on 2017-08-24 17:49 (UTC) by moll)
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.
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?
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.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.