On Thursday 10 September 2009, Felix Zielcke wrote: > Am Mittwoch, den 09.09.2009, 19:20 -0400 schrieb Chris Knadle: ... > > If I understand you correctly, you're saying that booting > > Memtest86+ using a "linux" method _should_ work but doesn't > > because of a problem with Memtest86+ itself? > > > > Without any underlying reasoning it makes it seem like > > reassigning the bug to Memtest86+ may not be fitting; bug #539907 > > concerns not being able to boot Memtest86+ from grub2 (the same > > code as grub-pc), so how can we know that this isn't a problem > > with grub2/grub-pc? > > The /etc/grub.d/memtest86+ must use the linux16 command now. > and that file is provides by the memtest86+ package, not at all by > the grub2 ones. > It's impossible to load it with the linux command. > memtest86+.bin doestn't provide the 32bit booting protocol recent > Linux kernels have. > It even still uses zImage format and not the bzImage one, which was > introduced with kernel 1.3.73.
The changelog for the current Debian grub-pc package has an interesting entry: grub2 (1.95+20080105-1) ... - Fixes boot of "Linux" zImages (including memtest86+). (Closes: 436113) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436113 So last year grub-pc could boot memtest86+ zImage using the "Linux" command, but today it can't. :-/ > Or they could just implement multiboot, but then the linux command > needs to be changed to multiboot. > Robert provided a patch though for memtest86 without + to implement > multiboot. > > As I already said in my grub-devel mail: > > zImage doesn't suppoert 32-bit boot (try with linux16) > > grub tells you. > Use linux16 /memtest86+-2.11.bin Is it possible to have grub-pc expect to use the "linux16" command to boot memtest86+ in /etc/grub.d/20_memtest86+ by default? -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org