From: Miles Lane <miles@megapathdsl.net>
To: Andrew Rodland <arodland@noln.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
LKML <linux-kernel@vger.kernel.org>,
David Relson <relson@osagesoftware.com>
Subject: Re: CML2 funkiness
Date: 02 Jan 2002 17:42:47 -0800 [thread overview]
Message-ID: <1010022168.1142.12.camel@stomata.megapathdsl.net> (raw)
In-Reply-To: <web-54762827@admin.nni.com>
In-Reply-To: <web-54762827@admin.nni.com>
I am seeing other problems. Using CML2 with a 2.4.18-pre1
tree, I was unable to create a kernel that would boot.
It kept crashing with messages stating that the rivafb driver
did not support 8-bit color depth. I tried tweaking my
configuration for a while, but finally reverted to CML2
and was then able to get a working kernel. I'll investigate
further and send along a diff of the working and broken
configuration files.
Another thing I notice is that when I create a configuration
using CML2, then switch to CML1 and run "make oldconfig"
using the same kernel tree, it appears there are configuration
options that never got set in the CML2 .config file.
I suppose this may simply be due to CML2 writing out the
options in a different order.
Miles
next prev parent reply other threads:[~2002-01-03 1:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201010217.g012H2d00406@lists.us.dell.com>
2002-01-02 14:03 ` Andrew Rodland
2002-01-02 15:10 ` David Relson
2002-01-02 15:03 ` Eric S. Raymond
2002-01-03 6:40 ` Andrew Rodland
2002-01-03 7:31 ` Eric S. Raymond
2002-01-03 11:28 ` Andrew Rodland
2002-01-03 0:25 ` Andrew Rodland
2002-01-03 0:25 ` Andrew Rodland
2002-01-03 0:26 ` Andrew Rodland
2002-01-03 1:42 ` Miles Lane [this message]
2002-01-03 2:05 ` Andrew Rodland
2002-01-03 9:42 ` Eric S. Raymond
2002-01-03 0:34 ` Andrew Rodland
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=1010022168.1142.12.camel@stomata.megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=arodland@noln.com \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=relson@osagesoftware.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
all inboxes | Powered by JetHome®