Neil Rickert composed on 2018-06-20 20:07 (UTC-0500):
Felix Miata wrote:
I guess that explains why not memtest86+, but not why not memtest86 7.4, which according to https://www.memtest86.com/technical.htm can be loaded by lilo or grub. If that site has an example menuentry for Grub2, I'm missing it. I tried creating one using the efiboot.img from a burned 7.4 iso, but get error message:
That looks unlikely. The file "efiboot.img" appears to be an image file for a FAT file system.
I suggest you instead try using: efi/boot/bootx64.efi
(relative to the CD). The "file" command says that it is a DOS bootable, but the naming and content of that directory suggests that it is an efi binary that you can probably chainload.
Note: I just loop mounted the iso, and looked in directory "efi".
When I later looked at that file "efiboot.img", I tried loop-mounting that, and it had similar content to the efi/boot directory
Thanks for the suggestion. I tried copying efi/boot/bootx64.efi from the burned CD to /mt74x64.efi and using this menuentry: insmod part_msdos search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 F6A8-27B2 chainloader (hd0,gpt1)/mt74x64.efi +1 It generates these error messages: error: no such device: F6A8-27B2. error: invalid sector size 65535. Next try after copying /mt74x64.efi to /bootx64.efi: insmod part_msdos search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 F6A8-27B2 linuxefi (hd0,gpt1)/bootx64.efi chainloader +1 With or without the insmod, it generates these error messages: error: no such device: F6A8-27B2. error: invalid sector size 65535. error: invalid EFI file path. Next try after copying CD's bootx64.efi to / on sda3: insmod ext2 search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 d8f505b4-9f5a-4f25-abea-f7738ede2de1 gb320usrlcl linuxefi (hd0,gpt3)/bootx64.efi chainloader +1 error: no such device: d8f505b4-9f5a-4f25-abea-f7738ede2de1. error: invalid sector size 65535. error: invalid EFI file path. Then: insmod ext2 search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 d8f505b4-9f5a-4f25-abea-f7738ede2de1 gb320usrlcl chainloader (hd0,gpt3)/bootx64.efi error: no such device: d8f505b4-9f5a-4f25-abea-f7738ede2de1. error: invalid sector size 65535. Trying to find meanings of grub2 error messages for me has been fruitless, e.g.: <https://www.gnu.org/software/grub/manual/grub/html_node/Troubleshooting.html#Troubleshooting> is empty. :-( -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org