From: David van Hoose <davidvh@cox.net>
To: walt <wa1ter@myrealbox.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.69] Fails on "Uncompressing Kernel" (detailed)
Date: Tue, 06 May 2003 13:33:55 -0500 [thread overview]
Message-ID: <3EB80013.3020502@cox.net> (raw)
In-Reply-To: <3EB7D399.4090109@myrealbox.com>
walt wrote:
> David van Hoose wrote:
>
>> I've managed to get 2.5.69 to boot *once*. Not trusting the kernel to
>> report the numerous problems until I can boot the kernel more than
>> once. I lost my config so I can't figure out what I managed to do so
>> right. I have tried a couple other configs that I normally use for
>> 2.4.x, but with the new 2.5.x options. Those I have attached.
>> All I get is the "Uncompressing Linux" and then no more output.
>> However, it appears that my system is booting anyway as if it is on
>> another TTY.
>
> The configuration menu has changed recently so that support for normal
> console operation is not included by default. To activate the usual
> console on VT and on VGA requires selecting options that are buried
> in the 'Character device' 'Input device' and 'Graphics support' menu
> sections. Go all the way to the bottom of each section and you will
> see the obvious items you need to select. Rather a confusing change.
That's all nice, but why have those options been removed if input
devices are created as modules? This somewhat breaks compatibility with
a lot of 2.4.x scripts. I run both kernels so I can compare things and
send bug reports with both trees. Also, 2.5.x has been rather cruel to
me in the past, so I tend to run the stable branch more often than not.
Can the VT and VGA options be placed back into the config if input
devices are created as modules? It would remove some confusion imo.
Thanks,
David
next prev parent reply other threads:[~2003-05-06 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.athqjpk.133cvik@ifi.uio.no>
2003-05-06 15:24 ` [2.5.69] Fails on "Uncompressing Kernel" (detailed) walt
2003-05-06 18:27 ` Bill Davidsen
2003-05-06 18:33 ` David van Hoose [this message]
2003-05-06 13:15 David van Hoose
2003-05-06 13:34 ` David van Hoose
2003-05-06 14:18 ` David van Hoose
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=3EB80013.3020502@cox.net \
--to=davidvh@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1ter@myrealbox.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