From: "H. Peter Anvin" <hpa@zytor.com>
To: bbpetkov@yahoo.de
Cc: Xudong Guan <xudong.guan@gmail.com>,
linux-kernel@vger.kernel.org, Chuck Ebbert <cebbert@redhat.com>,
michal.k.k.piotrowski@gmail.com
Subject: Re: 2.6.23-rc1: no setup signature found... SOLVED!
Date: Thu, 02 Aug 2007 13:41:35 -0400 [thread overview]
Message-ID: <46B2174F.2070705@zytor.com> (raw)
In-Reply-To: <20070802051323.GA4152@gollum.tnic>
Borislav Petkov wrote:
>
> Hi,
>
> now this is one of those cases where one tries to shoot a small fly with a
> nuclear missile. The first assumption that something was wrong with the kernel
> setup code was wrong and here's how i know:
>
> The problem with my version of grub not hitting the breakpoint 0x90200 made me
> think that something might be messed up in the grub part of the boot sequence.
> Thus, i did the qemu simulation again and noticed on the initial boot screen of
> grub it saying "Grub version 0.91." However, you remember from a different post
> that the version of grub i have is the latest to be found in debian unstable,
> 0.97-29, so i thought that something has to be wrong with it and especially with all
> those grub stages binaries, in my case in /boot/grub, which grub-install setups.
> Checking their timestamps revealed that the files are from 2004 so i thought,
> well, these are OLD! :) After refreshing the grub installation and replacing
> the stages-binaries with the fresh ones, the kernel booted just fine :), here:
>
> [boris@gollum:07:02:07:~:9994)-> uname -a
> Linux gollum 2.6.22-4fd06960f120e02e9abc802a09f9511c400042a5-12 #12 PREEMPT Thu Jul 26 18:08:34 CEST 2007 i686 GNU/Linux
>
> so i guess the problem was with the ancient parts of a grub installation i had
> lying around which weren't replaced by the apt-get update process and somehow
> messed up newer grub versions. Anyway, in the end one still learns a lot while at it.
>
> Thanks for your help.
>
Very cool. I actually suspected that, but I wanted to explore all
avenues. I'm glad this can be written off.
-hpa
prev parent reply other threads:[~2007-08-02 17:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:26 2.6.23-rc1: no setup signature found Borislav Petkov
2007-07-26 15:08 ` Xudong Guan
2007-07-26 15:19 ` H. Peter Anvin
2007-07-26 15:26 ` Xudong Guan
2007-07-26 15:43 ` H. Peter Anvin
[not found] ` <46A8C7BA.3040008@zytor.com>
[not found] ` <20070726162439.GA13387@xguan-laptop>
[not found] ` <46A8CB3F.7040207@zytor.com>
[not found] ` <20070726171609.GA16236@xguan-laptop>
2007-07-26 17:55 ` H. Peter Anvin
2007-07-26 16:30 ` Borislav Petkov
2007-07-26 16:36 ` Xudong Guan
2007-07-26 16:59 ` Borislav Petkov
2007-07-26 17:09 ` Xudong Guan
2007-07-26 18:12 ` H. Peter Anvin
2007-07-27 1:36 ` Borislav Petkov
2007-07-27 4:31 ` H. Peter Anvin
2007-07-27 15:51 ` Chuck Ebbert
2007-07-29 8:51 ` Borislav Petkov
2007-07-29 9:24 ` Xudong Guan
2007-07-29 10:37 ` Borislav Petkov
2007-07-29 13:50 ` H. Peter Anvin
2007-07-29 19:15 ` Borislav Petkov
2007-07-30 14:05 ` H. Peter Anvin
2007-07-30 18:53 ` Borislav Petkov
2007-07-30 20:46 ` H. Peter Anvin
2007-08-01 4:38 ` Borislav Petkov
2007-08-01 12:41 ` H. Peter Anvin
2007-08-01 14:36 ` H. Peter Anvin
2007-08-02 5:13 ` 2.6.23-rc1: no setup signature found... SOLVED! Borislav Petkov
2007-08-02 17:41 ` H. Peter Anvin [this message]
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=46B2174F.2070705@zytor.com \
--to=hpa@zytor.com \
--cc=bbpetkov@yahoo.de \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=xudong.guan@gmail.com \
/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