From: "H. Peter Anvin" <hpa@zytor.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23: GRUB reports "Setup signature not found"
Date: Fri, 09 Nov 2007 10:53:33 -0800 [thread overview]
Message-ID: <4734ACAD.3060001@zytor.com> (raw)
In-Reply-To: <20071109104635.11e504d2.rdunlap@xenotime.net>
Randy Dunlap wrote:
> On Fri, 09 Nov 2007 10:40:54 -0800 H. Peter Anvin wrote:
>
>> Randy Dunlap wrote:
>>> On Fri, 09 Nov 2007 11:48:20 -0500 Chuck Ebbert wrote:
>>>
>>>> Multiple people have now reported this error message with 2.6.23.
>>>> Updating GRUB fixes it:
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=370391
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=371321
>>> Thanks for the info.
>>> A better fix IMHO would be if one could get lilo to work. :)
>>>
>>> ---
>>> ~Randy [who is fed up with grub]
>> BTW, I definitely can agree with your feeling about grub (which is part
>> of why I maintain a different boot loader suite.) However, if you know
>> of any LILO problems, please speak up.
>
> I don't know of any lilo-specific problems and didn't mean to imply
> that LILO is at fault.
>
> The problems that I have seen when I have tried to switch from
> grub to LILO are more like config issues:
> either "can't find root device" or
> "cannot open /dev/console" or other initrd/initramfs issues.
>
OK. I'd be interested in your experience if you'd be willing to try out
syslinux (extlinux).
-hpa
next prev parent reply other threads:[~2007-11-09 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 16:48 2.6.23: GRUB reports "Setup signature not found" Chuck Ebbert
2007-11-09 16:59 ` Randy Dunlap
2007-11-09 18:37 ` H. Peter Anvin
2007-11-09 18:40 ` H. Peter Anvin
2007-11-09 18:46 ` Randy Dunlap
2007-11-09 18:53 ` H. Peter Anvin [this message]
2007-11-09 19:50 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4734ACAD.3060001@zytor.com \
--to=hpa@zytor.com \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox