![]() ![]() I don't know if that would be done with an EFI file or with something else, like the floppy image. hold down the spacebar).Īnd if there's also a way to add this to the installer ISO, as an option in the initial boot menu, that would make this useful for folks at the factory who are doing installation and testing, as well as for people trying to install Pop!OS and can't because they have a hardware problem. You can also add it to the firmware's boot device listing via efibootmgr, but I feel like the more important thing is having it in the systemd-boot menu, since that's where our users go to choose the recovery partition, and the command to open up that menu is universal across hardware (i.e. The following commands will build the new memtest86+ (v6 alpha) to include both an ISO you can burn to a USB stick and a memtest.efi file (although additional packages may be required, xorriso was the only additional one I had to install myself): The memtest.efi file is 135k and should not cause any space issues on /boot/efi. I feel like this would be very useful for troubleshooting purposes, and could be a proof-of-concept for adding other hardware troubleshooting tools to the EFI partition. This would allow us to add the new memtest86+ to our default Pop!OS installs, as another boot option that users can choose along with the recovery partition. But the most interesting feature that I'm seeing is that it compiles EFI executables by default, which work as expected when added to the /boot/efi partition. V6 is going to go into beta testing later this April, and it includes new features to make it useful once more, such as UEFI support, DDR5 testing, and more. ![]() The open-source memtest86+ (, distinct from the commercial memtest86 owned by PassMark at ) is under active development again.
0 Comments
Leave a Reply. |