From: "Charles Lepple" <clepple@ghz.cc>
To: "michaelm" <admin@www0.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc
Date: Mon, 21 Jul 2003 13:02:11 -0400 (EDT) [thread overview]
Message-ID: <32425.216.12.38.216.1058806931.squirrel@www.ghz.cc> (raw)
In-Reply-To: <20030721163517.GA597@www0.org>
michaelm said:
> That is on a p1 150MMX 32MB PC, specifically an IBM ThinkPad 560E. It
I just did a diff between your configuration, and that of my ThinkPad 770
(233 MHz Pentium MMX).
Note to defconfig maintainers: can these options be enabled by default on
i386 (like they were in 2.4)?
Things that you might want to enable:
CONFIG_ISA=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_AT_KEYBOARD=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
You also might want to turn off Trident FB support, and turn on generic
VESA support. I have had good luck with the VESA driver, but odd,
irreproducible errors with the Trident code (several versions back;
haven't retested).
--
Charles Lepple <ghz.cc!clepple>
http://www.ghz.cc/charles/
next prev parent reply other threads:[~2003-07-21 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 16:35 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc michaelm
2003-07-21 16:49 ` James Simmons
2003-07-21 17:02 ` Charles Lepple [this message]
2003-07-22 0:37 ` Samuel Flory
2003-07-22 0:42 ` Make menuconfig broken Samuel Flory
2003-07-22 7:19 ` Sam Ravnborg
2003-07-22 9:50 ` Roman Zippel
2003-07-22 13:24 ` Vojtech Pavlik
2003-07-22 16:47 ` James Simmons
2003-07-22 18:17 ` Christoph Hellwig
2003-07-22 19:16 ` Sam Ravnborg
2003-07-22 19:35 ` Samuel Flory
2003-07-22 19:46 ` Charles Lepple
2003-07-22 20:30 ` James Simmons
2003-07-23 22:53 ` bill davidsen
2003-07-23 22:48 ` bill davidsen
2003-07-22 18:00 ` Samuel Flory
2003-07-22 19:21 ` michaelm
2003-07-22 2:49 ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc Thomas Molina
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=32425.216.12.38.216.1058806931.squirrel@www.ghz.cc \
--to=clepple@ghz.cc \
--cc=admin@www0.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.