Am Sonntag, den 29.11.2009, 17:54 +0200 schrieb Dmitry Borodaenko:
> I was also affected by this bug, many thanks to Sebastian for posting
> the recovery instructions!
> 
> I also had os-prober and memtest86+ installed (but no grub-invaders),
> simply removing memtest86+ (and keeping os-probe) made the bug
> disappear, hope this helps to narrow it down. If not and you need help
> reproducing it, let me know and I will try to reinstall memtest86+ and
> see if it comes back.
> 

Did you really test this correctly?
I can't imagine the /etc/grub.d/20_memtest86+ provided by the memtest86+
package causes this.
As i already said in the report (though to someone else) the only reason
for that should be when the embed core.img is out of sync
with /boot/grub
Which only happens if grub-install gets run on a disk device where your
BIOS isn't booting from.
And that can happen because sometimes the kernel just thinks it's a good
idea to renumber them and so the stored device in the
grub-pc/install_devices debconf prompt is wrong.
-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to