Your message dated Thu, 1 Oct 2009 23:07:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#539907: still not working
has caused the Debian Bug report #539907,
regarding memtest86+ cannot be launched with GRUB 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
539907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: memtest86+
Version: 2.11-3
Severity: important
Tags: patch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
After upgrading GRUB 2 memtest86+ cannot be launched
anymore. GRUB says that the linux16 command should be used
to boot into memtest86+ instead of the linux command.
I've attached a patch against debian/grub that fixes this
and also fixes bug #522345.
Cheers,
Avi.
- -- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
memtest86+ depends on no packages.
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc [grub] 1.96+20090725-1 GRand Unified Bootloader, version
pn hwtools <none> (no description available)
pn kernel-patch-badram <none> (no description available)
pn memtest86 <none> (no description available)
pn memtester <none> (no description available)
ii mtools 4.0.10-1 Tools for manipulating MSDOS files
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkp4E8AACgkQwK8SobAxNVnHFACfb1P0OdENnKL4mHlmtk2F1FEp
EpAAnjI32UV+sD2wYlhV3jZpQEmEdBMB
=c75n
-----END PGP SIGNATURE-----
Index: memtest86+-2.11/debian/grub
===================================================================
--- memtest86+-2.11.orig/debian/grub 2009-08-04 12:37:21.000000000 +0300
+++ memtest86+-2.11/debian/grub 2009-08-04 12:41:20.000000000 +0300
@@ -1,16 +1,16 @@
#!/bin/sh
set -e
-. /usr/lib/grub/update-grub_lib
+. /usr/lib/grub/grub-mkconfig_lib
if test -e /boot/memtest86+.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root "/boot/memtest86+.bin" )
echo "Found memtest86+ image: $MEMTESTPATH" >&2
cat << EOF
menuentry "Memory test (memtest86+)" {
- linux $MEMTESTPATH
+ linux16 $MEMTESTPATH
}
menuentry "Memory test (memtest86+, serial console 115200)" {
- linux $MEMTESTPATH console=ttyS0,115200n8
+ linux16 $MEMTESTPATH console=ttyS0,115200n8
}
EOF
fi
--- End Message ---
--- Begin Message ---
found 539907 4.00-1
fixed 539907 4.00-2
thanks
On Thu, Oct 01, 2009 at 10:02:23PM +0200, Anders Boström wrote:
> reopen 539907
> stop
>
> Followup-For: Bug #539907
> Package: memtest86+
> Version: 4.00-1
>
> This bug is still not fixed... My /boot/grub/grub.cfg look like this
> after update to memtest86+ 4.00-1:
Yes, I messed things up in -1, it should be OK in -2, which is between
INCOMING and unstable already.
> ...
> ### BEGIN /etc/grub.d/20_memtest86+ ###
> menuentry "Memory test (memtest86+)" {
> prepare_grub_to_access_device /dev/md4 | sed -e "s/^/\t/"
> linux16 /boot/memtest86+.bin
> }
> menuentry "Memory test (memtest86+, serial console 115200)" {
> prepare_grub_to_access_device /dev/md4 | sed -e "s/^/\t/"
> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
> }
> ### END /etc/grub.d/20_memtest86+ ###
>
> And this fails with "unknown command prepare_grub_to_acce".
>
> / Anders
>
--- End Message ---
