On Wednesday 09 September 2009 18:27:43, Felix Zielcke wrote:
> reassign 545910 memtest86+
> forcemerge 545910 539907
> thanks
>
> Am Mittwoch, den 09.09.2009, 17:58 -0400 schrieb Chris Knadle:
> > Package: grub-pc
> > Version: 1.97~beta2-2
> > Severity: grave
> > Justification: renders package unusable
> >
> >
> > Updating to grub-pc from grub-legacy creates a script in
> > /etc/grub.d/20-memtest+ but unfortunately the entry fails to
> > boot memtest+ after the upgrade. Specifically, this won't work:
> >
> > menuentry "Memory test (memtest86+)" {
> > linux $MEMTESTPATH
> > }
> >
> > But this does:
> >
> > menuentry "Memory test (memtest86+)" {
> > linux16 $MEMTESTPATH
> > }
> >
> > I was finally able to find the answer here (thank you Felix):
> > http://osdir.com/ml/grub-devel-gnu/2009-08/msg00101.html
>
> /etc/grub.d/memtest86+ belongs to the memtest86+ package.
> This has been already reported a month ago.
> I don't know why it's maintainer doestn't fix this.
> Maybe this will push it.
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?
-- Chris
--
Chris Knadle
[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
