From: Tom Rini <trini@kernel.crashing.org>
To: Stefan Jeglinski <jeglin@4pi.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: whacked out 2.2.18preX - last gasp
Date: Tue, 21 Nov 2000 08:10:13 -0700 [thread overview]
Message-ID: <20001121081013.G552@opus.bloom.county> (raw)
In-Reply-To: <p04330100b63f9bce42dd@[192.168.0.1]>; from jeglin@4pi.com on Mon, Nov 20, 2000 at 11:03:43PM -0500
On Mon, Nov 20, 2000 at 11:03:43PM -0500, Stefan Jeglinski wrote:
> ERROR - Attempting to write value for
> unconfigured variable (CONFIG_SERIAL_CONSOLE).
>
> when using make xconfig. I can't see how this could be related, but it is true.
xconfig is buggy sometimes. Try make oldconfig afterwards, it'll prompt for
anything which didn't get set by xconfig.
> It's frankly hard at this point to buy that one of my PCI devices is
> walking over the kernel. Or if it is, it looks like the end of the
> Linux line for my PowerTowerPro with the 2940 card. I think this is
> either a bug in the aic7xxx driver that has been exposed by 2.2.18
> changes (highly doubtful, there are too many 2940s out there for it
> to have been missed), or a linux-pmac bug. I just don't know enough
> yet to prove it, much less find it.
Hmm. 2.2.18pre21 from linuxppc_2_2 bk works on my G4/Yikes! with a 2940UW
in it. What compiler are you using?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-21 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 4:03 whacked out 2.2.18preX - last gasp Stefan Jeglinski
2000-11-21 9:50 ` Michael Schmitz
2000-11-21 15:10 ` Tom Rini [this message]
2000-11-21 15:25 ` Stefan Jeglinski
2000-11-21 15:36 ` Tom Rini
2000-11-21 16:17 ` Benjamin Herrenschmidt
2000-11-21 21:48 ` Michel Lanners
2000-11-21 22:17 ` Stefan Jeglinski
[not found] <Pine.LNX.4.10.10011211049130.22058-100000@opal.biophys.uni-duesseldorf.de >
2000-11-21 14:03 ` Stefan Jeglinski
2000-11-21 14:29 ` Michael Schmitz
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=20001121081013.G552@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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).