Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot boot memtest86+ in UEFI mode - efi_setup() failed #1417

Open
TimoVerbrugghe opened this issue Feb 21, 2024 · 2 comments
Open

Cannot boot memtest86+ in UEFI mode - efi_setup() failed #1417

TimoVerbrugghe opened this issue Feb 21, 2024 · 2 comments
Labels

Comments

@TimoVerbrugghe
Copy link

[X]: This bug persists when memory is increased beyond 8GB.

Describe the bug
When trying to boot memtest86+ 6.20 on menu 2.0.76 (latest one available while writing this) in EFI mode, I'm getting errors after the efi file of memtest86+ is downloaded (see screenshot).

To Reproduce
Steps to reproduce the behavior:

  1. Boot netbootxyz in EFI mode
  2. Go to Utilities (UEFI)
  3. Try to boot memtest86+ 6.20

Expected behavior
Memtest86+ boots

Screenshots
image

Additional context

  • Using netbootxyz docker container, latest tag feom ghcr.io
  • Computer that is trying to boot memtest86+ has following specs: Ryzen 5 3600, 64 gb DDR4 ram, GA-AB350-DS3H motherboard
  • Memtest86 does work while booting netbootxyz in BIOS
  • Other options in EFI mode (linux network installs or other utilities) do work normally (did not test every single one but proxmox installer, ubuntu live cd and system rescue CD all boot normally.
  • Tried both with preloaded memtest86+ assets as non-preloaded ones
  • Already tried fully deleting the docker container and its volumes and redeploying it with a freshly pulled image
@Firminator
Copy link
Contributor

[On a sidenote v7.00 was released recently: https://github.com/memtest86plus/memtest86plus/releases which I'm not sure would or would not fix this issue.]

@antonym
Copy link
Member

antonym commented Feb 23, 2024

Did you happen to try 7.x series. I saw different behaviors on Proxmox vs VMWare between versions so I left them both as available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants