Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
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
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
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. -- Francois Gouget fgou...@free.fr http://fgouget.free.fr/ Theory is where you know everything but nothing works. Practice is where everything works but nobody knows why. Sometimes they go hand in hand: nothing works and nobody knows why. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
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 :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
I think that this change should fix this bug. Memtest86+ menu entries will not be visible in uefi mode anymore... I think it masks the problem rather than fixing it: testing the memory is still impossible on UEFI systems. It's a bit sad that after two years this bug is still present. See this related bug on Launchpad: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/883017 -- Francois Gouget fgou...@free.fr http://fgouget.free.fr/ f u kn rd ts, ur wy 2 gky 4 ur wn gd. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
On Thu, Oct 02, 2014 at 04:55:26PM +0200, Francois Gouget wrote: It's a bit sad that after two years this bug is still present. See this related bug on Launchpad: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/883017 Thanks for pointing this out. The patch is easily transplanted to 5.01, but I don't have an UEFI system to check (will have to check OVMF some day ;). 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). 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
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
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. -- Francois Gouget fgou...@free.fr http://fgouget.free.fr/ Good judgment comes from experience, and experience comes from bad judgment -- Barry LePatner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
Hello,
in grub2 scripting language you can test if grub is running in
bios or uefi mode.
Now in /etc/grub.d/20_memtest86+ is:
===
cat EOF
menuentry Memory test (memtest86+) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
$LX $MEMTESTPATH
}
menuentry Memory test (memtest86+, serial console 115200) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
$LX $MEMTESTPATH console=ttyS0,115200n8
}
EOF
===
You can change it to:
===
cat EOF
if test \$grub_cpu = i386 -a \$grub_platform = pc; then
menuentry Memory test (memtest86+) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
$LX $MEMTESTPATH
}
menuentry Memory test (memtest86+, serial console 115200) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
$LX $MEMTESTPATH console=ttyS0,115200n8
}
fi
EOF
===
and both memtest86+ menu entries will be visible only if grub is
running in bios mode. In uefi mode grub_platform is set to efi.
I think that this change should fix this bug. Memtest86+ menu
entries will not be visible in uefi mode anymore...
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
Control: reassign 695246 memtest86+ On 12/05/2012 10:23 PM, Daniel Kahn Gillmor wrote: I've installed grub-efi-amd64 2.00-7 and memtest86+ 4.20-1.1 on this Thinkpad x220. However, the memtest86+ boot options don't work: * the normal memtest86+ stanza complains that there is no linux16 command. * the experimental multiboot memtest86+ stanza turns the screen black, and then reboots; no memory is tested. any suggestions about how i can run memtest86+ on this platform from grub-efi? Any more information i can provide to help debug? Hm, this may be an upstream issue with memtest86+. According to Doc TB: The issue is not 16 or 32 bits boot protocol, the main issue is the numerous BIOS calls required to do the memory initialization. EFI is a nice idea, but the first time I heard EFI will replace BIOS in the upcoming months !!! was in 2002 at an Intel Developer's forum. 10 years after, UEFI replaced EFI but BIOS is still present in 99% of PC Motherboard. It's an hard task to build an EFI-readyMemtest86+, with massive code rewrite, and that version will not be compatible with legacy BIOS. I will not consider supporting two forks at the same time, so when Memtest86+ will switch to EFI, the BIOS version will be discontinued. When BIOS will be not be available in standard PC components, I'll start working on en EFI revision. http://forum.canardpc.com/threads/68001-Memtest86-5.00-Beta-available-!-Need-betatesters-!?s=d809d0006a4881f7b3cf0374fcad6fadp=5467296viewfull=1#post5467296 So perhaps update-grub needs to recognize that grub-efi will not be able to use this and avoid injecting memtest86+ stanzas in grub.cfg? This should probably be done within /etc/grub.d/20_memtest86+, which itself belongs to the memtest86+ package, so i'm reassigning this bug. --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695246: grub-efi-amd64 has no linux16, fails to boot memtest86+ (multiboot also fails)
Package: grub-efi-amd64
Version: 2.00-7
Severity: normal
I've installed grub-efi-amd64 2.00-7 and memtest86+ 4.20-1.1 on this
Thinkpad x220. However, the memtest86+ boot options don't work:
* the normal memtest86+ stanza complains that there is no linux16
command.
* the experimental multiboot memtest86+ stanza turns the screen
black, and then reboots; no memory is tested.
any suggestions about how i can run memtest86+ on this platform from
grub-efi? Any more information i can provide to help debug?
--dkg
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/vg_alice0-root / ext4
rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_alice0-home /home ext4
rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_alice0-var /var ext4
rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/sda2 /boot ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/sda1 /boot/efi vfat
rw,nosuid,nodev,noexec,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if loadfont unicode ; then
set gfxmode=1024x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
c4425021-9542-4ff6-888c-548c08b4a69c
else
search --no-floppy --fs-uuid --set=root c4425021-9542-4ff6-888c-548c08b4a69c
fi
insmod png
if background_image /grub/.background_cache.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-5b7c89b1-cf26-4427-b8a9-8c74e4897111' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
c4425021-9542-4ff6-888c-548c08b4a69c
else
search --no-floppy --fs-uuid --set=root
c4425021-9542-4ff6-888c-548c08b4a69c
fi
echo'Loading Linux 3.2.0-4-amd64 ...'
linux /vmlinuz-3.2.0-4-amd64 root=/dev/mapper/vg_alice0-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-4-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
'gnulinux-advanced-5b7c89b1-cf26-4427-b8a9-8c74e4897111' {
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.2.0-4-amd64-advanced-5b7c89b1-cf26-4427-b8a9-8c74e4897111' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
c4425021-9542-4ff6-888c-548c08b4a69c
else
search --no-floppy --fs-uuid --set=root
c4425021-9542-4ff6-888c-548c08b4a69c
fi
echo'Loading Linux 3.2.0-4-amd64 ...'
linux /vmlinuz-3.2.0-4-amd64 root=/dev/mapper/vg_alice0-root
ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-4-amd64
}
