From: Phil Auld <email@example.com>
To: DragonK <firstname.lastname@example.org>
Subject: Re: Linux Kernel 2.4.x Bug
Date: Wed, 25 Sep 2002 09:07:22 -0400 [thread overview]
Message-ID: <20020925090722.K4368@vienna.EGENERA.COM> (raw)
In-Reply-To: <200209250709.g8P79ip29724@Port.imtp.ilyichevsk.odessa.ua>; from email@example.com on Wed, Sep 25, 2002 at 10:04:05AM -0200
Rumor has it that on Wed, Sep 25, 2002 at 10:04:05AM -0200 Denis Vlasenko said:
> On 24 September 2002 19:34, DragonK wrote:
> > I'm sorry if I'm sending this to the wrong persons,
> > but I really don't know whom I should send this to.
> > My problem involves ALL linux kernels 2.4.x. All
> > versions I've tried on my machine lock up at boot time
> > (no panic, no oops, just plain old dead), just after
> > writing "Uncompressing linux kernel...Ok, now booting
> > the kernel...". The kernel banner DOES NOT appear. I
> > compiled every kernel with a minimal set of options
> > (and CPU=386) but nothing; I've even installed the
> > latest Lilo.
maybe too minimal :)
This sounds like what you get if you don't have VT configured.
Make sure you have these in your .config
prev parent reply other threads:[~2002-09-25 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 21:34 Linux Kernel 2.4.x Bug DragonK
2002-09-25 12:04 ` Denis Vlasenko
2002-09-25 13:07 ` Phil Auld [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).