From: Aviram Jenik <aviram@beyondsecurity.com>
To: Valdis.Kletnieks@vt.edu, mru@users.sourceforge.net (Måns Rullgård)
Cc: linux-kernel@vger.kernel.org
Subject: Re: orinoco_cs module broken in test8
Date: Sat, 18 Oct 2003 18:36:12 +0200 [thread overview]
Message-ID: <200310181836.12402.aviram@beyondsecurity.com> (raw)
In-Reply-To: <200310181624.h9IGOgLW023089@turing-police.cc.vt.edu>
On Saturday 18 October 2003 18:24, Valdis.Kletnieks@vt.edu wrote:
> On Sat, 18 Oct 2003 17:48:21 +0200, mru@users.sourceforge.net
(=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=) said:
> > Aviram Jenik <aviram@beyondsecurity.com> writes:
> > > Orinoco_cs worked for me in all previous 2.6.0-testx versions, but
> > > stopped working in test8. Message log shows:
> > > kernel: orinoco_cs: RequestIRQ: Unsupported mode
> >
> > You have to enable ISA bus support, i.e. CONFIG_ISA=y.
>
> If it worked for him in earlier -testX, he must have had it set before...
>
> Aviram: Is CONFIG_ISA=y in your -test8 .config? If so, it's some other
> *new* problem. If not, do you have any idea how it got turned off ('make
> oldconfig' weirdness??)
Man's suggestion of CONFIG_ISA=y did solve the problem. I can't figure out how
it was turned off, though. I just noticed several config options got disabled
on this test kernel.
I wasn't running make oldconfig, though - I'm always running make menuconfig.
Until now that was always saving my previous options (I've been trying every
2.6.0-testx version) so I was assuming it was the right way to do it :-)
- Aviram
prev parent reply other threads:[~2003-10-18 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 15:23 Aviram Jenik
2003-10-18 15:48 ` Måns Rullgård
2003-10-18 16:24 ` Valdis.Kletnieks
2003-10-18 16:36 ` Aviram Jenik [this message]
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=200310181836.12402.aviram@beyondsecurity.com \
--to=aviram@beyondsecurity.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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
Powered by JetHome