On Tue, Oct 07, 2014 at 08:50:17PM +0200, Yann Dirson wrote: > On Tue, Oct 07, 2014 at 12:28:31PM +0200, Francois Gouget wrote: > > On Fri, 3 Oct 2014, Yann Dirson wrote: > > > > > On Fri, Oct 03, 2014 at 01:36:46AM +0200, Francois Gouget wrote: > > > > On Thu, 2 Oct 2014, Yann Dirson wrote: > > > > [...] > > > > > You will find a test package at > > > > > http://ydirson.free.fr/soft/debian/memtest/, I'll wait for feedback > > > > > before uploading (just tested in qemu here). > > > > > > > > With this package I'm not getting the 'linux16' error anymore. However > > > > I'm not getting memtest86 either :-( > > > > > > > > The grub menu disappears and I'm left with the Debian's grub wallpaper > > > > and nothing happens. I had to use the power button to shutdown. > > > > > > OK, let's first check whether it is the patch that needs adjusting to > > > 5.01, or if the original for 4.20 does not work for you either. > > > > > > Uploaded 4.20-2grub2 to same location. > > > > The 4.20-2grub2 package behaves the same way as the 5.01-2grub2 one: > > when I select the memtest86+ entry only the Debian background image > > remains and nothing furether happens. The computer is unresponsive to > > the keyboard and I have to press the power button to shut it down. > > OK, thanks for the feedback. > > So the bottom line is, today we don't have a working patch for UEFI, > so the best for the user is to disable the menu entries. > > To do anything better, we'll need to get someone with the time and > will to look at it to get access to an UEFI box. Maybe qemu+OVMF can > be of some help - I could find some time to have a look at that, but > that's no promise :)
FWIW, memtest86 5.1.0 is now UEFI-only, and they achieve BIOS compatibility by a dualboot image (with v4 for BIOS :). What's less funny (aside from their definitely non-free-software-friendly culture) is that they have apparently botched their releases, releasing only 4.3.7 source as part of their images. I have sent them a bugreport for this, let's hope they will fix things (or else it will likely have to be considered a GPL violation, let's hope it is rather just a human error...). Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
