On the project website (https://www.memtest.org/#change) there is a new version. Changelog says: "After a long hiatus without updates and following numerous requests, I've started compiling many codes branches to release public builds again! Here is Memtest86+ 5.31b, with many bug fixes in the core functions. This build is not ready for production yet, because it lacks some feedbacks from beta-testers. Additional features and updated detection code will follow soon, as soon I have access to my lab with all the reference test platforms. It's currently inaccessible due to the COVID19 lockdown. If you find a bug or regression in this build, please send your feedback to memtest (-A-) memtest.org. Thank you!"
Created attachment 647426 [details] memtest86+ 5.31b test ebuild ebuild to get 5.31b building; this is largely based on the 5.01-r5 ebuild, with a number of the patches removed, since they've been upstreamed since 5.01. Refreshed patches coming shortly.
Created attachment 647428 [details, diff] memtest86+-5.31b-gcc-473.patch
Created attachment 647430 [details, diff] memtest86+-5.31b-hardcoded_cc.patch
Created attachment 647432 [details, diff] memtest86+-5.31b-no-clean.patch
Created attachment 647434 [details, diff] memtest86+-5.31b-objcopy.patch
Created attachment 647436 [details, diff] memtest86+-5.31b-test-random-cflags.patch
(In reply to J. Paul Reed from comment #1) > Created attachment 647426 [details] > memtest86+ 5.31b test ebuild > > ebuild to get 5.31b building; this is largely based on the 5.01-r5 ebuild, > with a number of the patches removed, since they've been upstreamed since > 5.01. > > Refreshed patches coming shortly. Thanks. I took the liberty of submitting a pull request with your ebuild and patches.
I would love to see sys-apps/memtest86+-5.31b in the main portage tree. Version 5.01 doesn't work on my new Ryzen 3 system (it reports memory errors), while version 5.31 works as expected.
I cannot get memtest86/memtest86+ to properly boot off of my system. How exactly do you start it? I have tried off of my NVME via a GRUB entry as well as off of a USB.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c08f36620da95e3f707a57b068bcd4ef5cb8e6e6 commit c08f36620da95e3f707a57b068bcd4ef5cb8e6e6 Author: PPed72 <paolo.pedroni@iol.it> AuthorDate: 2020-11-19 17:09:50 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2021-08-13 13:22:36 +0000 sys-apps/memtest86+: version bump to 5.31b Closes: https://bugs.gentoo.org/728766 Signed-off-by: Paolo Pedroni <paolo.pedroni@iol.it> Package-Manager: Portage-3.0.9, Repoman-3.0.2 Closes: https://github.com/gentoo/gentoo/pull/18324 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> sys-apps/memtest86+/Manifest | 1 + .../files/memtest86+-5.31b-gcc-473.patch | 13 +++ .../files/memtest86+-5.31b-hardcoded_cc.patch | 16 +++ .../files/memtest86+-5.31b-no-clean.patch | 19 ++++ .../files/memtest86+-5.31b-objcopy.patch | 21 ++++ .../memtest86+-5.31b-test-random-cflags.patch | 17 +++ sys-apps/memtest86+/memtest86+-5.31b.ebuild | 114 +++++++++++++++++++++ 7 files changed, 201 insertions(+)
@Larry the Git Cow: thanks for updating the package :-) @Kobboi: Have you seen the instructions at the end of 'emerge --oneshot sys-apps/memtest86+'? If you have any problems, please open a thread in the Gentoo forums. I can help you there.
