From: Randy Dunlap <randy.dunlap@oracle.com>
To: Von Wolher <trilight@ns666.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19.1 failing
Date: Fri, 12 Jan 2007 20:30:59 -0800 [thread overview]
Message-ID: <20070112203059.78feb871.randy.dunlap@oracle.com> (raw)
In-Reply-To: <45A84ACB.5010904@ns666.com>
On Sat, 13 Jan 2007 03:58:19 +0100 Von Wolher wrote:
> Hi,
>
> I just build a 2.6.19.1 vanilla kernel based on the previous config
> (make oldconfig) but for some reason it is not starting. Despite
> following the usual procedure with lilo like many times before it seems
> that lilo tries to boot it and jumps back to the menu screen.
Was your previous config 2.6.18* or 2.6.19?
If it was 2.6.18* and you are using SATA, the config symbol
names for SATA changed and you'll need set them via make *config.
Otherwise we'll probably need more info.
> But selecting the old kernel boots just fine.
>
> Any one can advise on what could cause such behaviour beside the obvious
> steps like did i run lilo after kernel compile, check paths ...
---
~Randy
prev parent reply other threads:[~2007-01-13 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 2:58 2.6.19.1 failing Von Wolher
2007-01-13 4:30 ` Randy Dunlap [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=20070112203059.78feb871.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trilight@ns666.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