Created attachment 214020 [details] update of memtest86+ to 5.31b update of memtest86+ to 5.31b version, release a couple of months back. updated gcc dependency from 4.8 to 9 please let me know if you have any doubts or concerns
PR sent to wrong port. This is memtest86, not memtest86+ Thanks, Nuno
I'm not sure about your "no" feedback: isn't this patch referring to latest version from www.memtest.org, which is what *existing* memtest86+ port uses? Let me know if there's anything else you need from me.
(In reply to Alessandro Sagratini from comment #2) You are assigning PRs to sysutils/memtest86 and it should be sysutils/memtest86+ memtest86 its just a ISO
Oh, you are correct, I am not sure why maintainer feedback was assigned to you, I am going to see if I can change that on my own, otherwise, some developer can do that, hopefully :)
Assigning proper maintainer address in maintainer-feedback.
If the port builds and works then I do not have any objections. I am a bit out of time to test it myself, so could anyone please confirm this? It might be a good idea to advertise this update on ports@ and maybe hackers@. Thanks!
Created attachment 214186 [details] additional improvements on top of submitter's patch Thanks for the original patch. I made a few changes on top of it: * Reorder ONLY_FOR_ARCHS * USE_GCC= 9+ since it builds and this way we could benefit of future compiler improvementes (or go back to just 9 if something breaks) * Remake patches to comply with the ports standard. Additionally, when I tried to test this from boot loader, this is what I got: OK unload OK load /boot/opt/memtest86+ don't know how to load module '/boot/opt/memtest86+' Same thing happens with current version (5.01). Any ideas?
The port builds fine in {11.3,12.1}{amd64,i386} and 13-current amd64.
In reply to Fernando Apesteguía from comment #8) Thank you! I see this on the memtest86+ page: > 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. Maybe we should wait until the new version is out of beta? Or, perhaps, create a new port for the devel version?
(In reply to Fernando Apesteguía from comment #7) It's been a while since I last started memtest86+ from loader. Maybe something in loader changed. Let me look into it.
Andriy, since it's been a few months, I'm wondering if any progress has been made? Or do you feel it's better to wait for next release? Thank you
Alessandro, could you make it run?
mmmh, no, not yet, I am also getting "don't know how to load module '/boot/opt/memtest86+'" error message that was shown in previous messages
(In reply to Alessandro Sagratini from comment #13) OK, neither did I :-) I think we need to investigate a bit more before committing a new version. I will try to have a look this week.
I gave it another try but could not make it work. 12.1 amd64 --> don't know how to load module 13-current amd64 --> reboots the machine
Hi Alessandro. Does this mean that it works for you? In which arch/FreeBSD version? Cheers.
Reopening since it still reboots the machine in 14-current.
> … update to 5.31b Memtest86+ v6.01 at <https://www.memtest.org/>, if this helps. (In reply to Fernando Apesteguía from comment #15 and comment #17) I assume that the reboots are as outlined in bug 211204, and that an update here will resolve 211204. If not true, please correct me – thanks.
(In reply to Graham Perrin from comment #18) I think that is a bit too much to assume. Have you read this PR? My last test rebooted 13 amd64.
(In reply to Fernando Apesteguía from comment #19) Sorry for the misunderstanding. I did read both bug reports.
Memtest86+ is at version 7.0 now. I think that this PR can be closed now as there is no merit in upgrading to 5.35 when multiple 6.x versions and now 7.0 have been released.