From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Mads Christensen <mfc@krycek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cannot boot 2.5.67
Date: Thu, 17 Apr 2003 10:54:36 -0700 [thread overview]
Message-ID: <20030417105436.3c70b895.rddunlap@osdl.org> (raw)
In-Reply-To: <1050601594.1073.1.camel@krycek>
There was also a thread about 1 week ago that indicated that
if CONFIG_LOG_BUF_SHIFT=<some very large number here>,
the kernel won't boot and won't tell you why.
E.g., if someone sets CONFIG_LOG_BUF_SHIFT to a buffer size in bytes
(or KB) instead of a shift value, it causes a very large log buffer
declaration and that's about all she wrote.
~Randy
On 17 Apr 2003 19:46:34 +0200 Mads Christensen <mfc@krycek.org> wrote:
| You have to get
| CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
| inorder for you to see anything =)
|
| On tor, 2003-04-17 at 19:16, Paul Rolland wrote:
| > Got the same starting with 2.5.67...
| > I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
| > and when booting, booh :-(
| >
| > It was a RH8 base, Lilo... I'll try tonite to find out which option
| > is responsible of that...
| >
| > Regards,
| > Paul
| >
| > > I have a rh9 installation, grub is properly configured, and
| > > when I select
| > > to boot a 2.5 kernel it does not even decompress it. It stops
| > > even before
| > > printing the kernel version.
next prev parent reply other threads:[~2003-04-17 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 17:03 cannot boot 2.5.67 Pau Aliagas
2003-04-17 17:16 ` Paul Rolland
2003-04-17 17:46 ` Mads Christensen
2003-04-17 17:54 ` Randy.Dunlap [this message]
2003-04-17 18:18 ` Paul Rolland
2003-04-17 17:56 ` Valdis.Kletnieks
2003-04-22 15:28 ` Pau Aliagas
2003-04-22 17:03 ` Valdis.Kletnieks
2003-04-22 18:25 ` Russell King
2003-04-24 20:14 ` Bill Davidsen
2003-04-17 18:16 ` Paul Rolland
2003-04-17 18:27 ` Mads Christensen
2003-04-18 4:07 ` Felipe Alfaro Solana
2003-04-17 18:36 ` John Bradford
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=20030417105436.3c70b895.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfc@krycek.org \
/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;
as well as URLs for NNTP newsgroup(s).