2009/12/20 Felix Zielcke <fziel...@z-51.de>: > found 561766 1.98~20091210-1 > thanks > Am Sonntag, den 20.12.2009, 00:04 -0500 schrieb Simon Kjika'qawej: >> Package: grub2 >> Version: >> Severity: grave >> Justification: renders package unusable >> >> Hi, >> >> Due to this bug, grub2 1.98~20091210-1 and the previous version were >> unable to boot correctlẏ. The problem came up when trying to load >> the >> linux module. When you try to insmod 'linux' that error pops up and >> you're completely unable to load a kernel image at all. >> >> Say you're at the grub rescue prompt, you try `insmod linux`, grub >> then >> says "the symbol "grub_printf_" not found" and exits with an error, >> making it so that you cannot boot at all. This is why I call it grave. >> >> I'm using beta1 right now because of this. Some of the also working >> ones >> aren't present in the repos anymore (I wish archive.debian.org was >> still >> up). >> > > Unfortunately you reported this against the grub2 dummy package instead > of the correct grub-pc. > What does `echo GET grub-pc/install_devices | debconf-communicate' say? > Probable the postinst ran grub-install on the disk which you don't boot > from.
0 /dev/hda I only boot from one. And yes at the time it was correct. I haven't booted the ubuntu in weeks, and even then I made sure the debian partition was the last one I installed to the MBR. > And so this is probable just a duplicate of #554790 I see the issue, and I noticed that - in practice, understanding it in theory, but not having thought it out thoroughly - is that due to the hd to ds change, the core.img wasn't synced therefore causes this (and other potential) issue(s). I imagine you're running this new version? > -- > 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
