After updating from memtest86+-5.01-r2 (which still worked) to 5.01-r3: # lilo -v LILO version 24.2 (released 22-November-2015) * Copyright (C) 1992-1998 Werner Almesberger (until v20) * Copyright (C) 1999-2007 John Coffman (until v22) * Copyright (C) 2009-2015 Joachim Wiedorn (since v23) This program comes with ABSOLUTELY NO WARRANTY. This is free software distributed under the BSD License (3-clause). Details can be found in the file COPYING, which is distributed with this software. Reading boot sector from /dev/sda1 Using BITMAP secondary loader Calling map_insert_data Mapping bitmap file /boot/gentoo-cow.bmp Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-4.9.14-gentoo Mapping RAM disk /boot/initramfs.cpio.xz The initial RAM disk will be loaded in the high memory above 16M. [...] Boot image: /boot/memtest86plus/memtest Fatal: Kernel /boot/memtest86plus/memtest is too big
Relevant lines from /etc/lilo.conf: compact lba32 boot=/dev/sda1 prompt timeout=150 [...] image=/boot/memtest86plus/memtest label=Memtest86Plus
memtest is an ELF while memtest.bin is the small bootable one. you need to update your configs to point to memtest.bin if you want that one. older versions of memtest86+ used different names relative to upstream. 5.01-r3 moved us back to that. the elog at the end says to use memtest.bin by default now.
Well, no objections against the change itself. This will break everybody's configuration though, especially because the name "memtest" (which people have in their config files) is reused for something different. So IMHO the ebuild should be much more noisy about this.
(In reply to Ulrich Müller from comment #3) the breakage here seems fairly benign. they tried to boot a test program and it didn't work, so they just boot/move to a real system and update the config. the grub-2 config we install DTRT so there's no manual intervention required. i've added an explicit note about memtest & memtest.bin being renamed.
