From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: prism54: Out of memory, cannot handle oid, card/socket may be faulty, or IRQ line too busy
Date: Sat, 09 Feb 2008 11:09:51 +0100 [thread overview]
Message-ID: <47AD7BEF.9000709@wpkg.org> (raw)
In-Reply-To: <20080208221009.GA2919@tuxdriver.com>
John W. Linville schrieb:
> On Fri, Feb 08, 2008 at 11:01:26PM +0100, Tomasz Chmielewski wrote:
>> I just wanted to use a mini-PCI card using a prism54 module - however, it
>> fails to bring the interface up with "Out of memory, cannot handle oid" and
>> "Your card/socket may be faulty, or IRQ line too busy" messages.
>
> I vaguely recall seeing an error like that when I used the wrong
> firmware. What firmware are you using?
This is my card:
# lspci -nn
(...)
00:02.0 Network controller [0280]: Intersil Corporation ISL3890 [Prism
GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] [1260:3890] (rev 01)
According to http://prism54.org/newdrivers.html, my card is among the
supported devices, and I should use version 2.7.0.0 for PCI devices
firmware:
PCI Vendor (hex) PCI Product (hex) Common name
1260 3890 Generic ISL3890
It doesn't work and says "Your card/socket may be faulty, or IRQ line
too busy". With 2.7.0.0 firmware, it doesn't say "out of memory" anymore.
Are there more things to be done to make this card work?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-02-09 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 22:01 prism54: Out of memory, cannot handle oid, card/socket may be faulty, or IRQ line too busy Tomasz Chmielewski
2008-02-08 22:10 ` John W. Linville
2008-02-08 23:33 ` Tomasz Chmielewski
2008-02-09 10:00 ` Tomasz Chmielewski
2008-02-09 10:09 ` Tomasz Chmielewski [this message]
2008-02-10 1:27 ` Reinhard Biegel
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=47AD7BEF.9000709@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.