From: Benjamin Reed <br33d@yahoo.com>
To: Ivan Matveich <ivan.matveich@gmail.com>, Dan Williams <dcbw@redhat.com>
Cc: linux-kernel@vger.kernel.org, linville@tuxdriver.com,
netdev@vger.kernel.org, breed@users.sourceforge.net,
achirica@users.sourceforge.net, jt@hpl.hp.com,
fabrice@bellet.info
Subject: Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
Date: Fri, 3 Nov 2006 09:08:06 -0800 (PST) [thread overview]
Message-ID: <20061103170806.60233.qmail@web51511.mail.yahoo.com> (raw)
In-Reply-To: <b5def3a40611021321h22ec79c3x51a54ec7d5b07b3@mail.gmail.com>
You might find this thread useful if it is just a case
of messed up firmware:
http://sourceforge.net/mailarchive/message.php?msg_id=2970511
The gist of it is that sometimes DOS utilities work
when all else fails.
ben
--- Ivan Matveich <ivan.matveich@gmail.com> wrote:
> On 11/2/06, Dan Williams <dcbw@redhat.com> wrote:
> > Do you know which kernel version that patch first
> appeared in?
>
> It was committed on 1 Dec 2005, and 2.6.15 was
> released on 3 Jan 2006.
>
> > That would be a great idea, let us know what the
> results are, especially
> > if you cna figure out which firmware version you
> have, or if the card
> > itself is really just dead.
>
> No luck with freebsd: error resetting card.
>
> I'll try my luck with Cisco's Windows
> utility---probably
> tomorrow---but I'd now wager that my card has simply
> croaked. (I've
> even taken it out and re-seated it in its slot, just
> in case that
> helped.) In any case, thanks for the help.
>
prev parent reply other threads:[~2006-11-03 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 3:14 [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command Ivan Matveich
2006-11-02 16:12 ` Dan Williams
2006-11-02 18:30 ` Ivan Matveich
2006-11-02 19:11 ` Dan Williams
2006-11-02 21:21 ` Ivan Matveich
2006-11-02 21:26 ` Jean Tourrilhes
2006-11-03 17:08 ` Benjamin Reed [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=20061103170806.60233.qmail@web51511.mail.yahoo.com \
--to=br33d@yahoo.com \
--cc=achirica@users.sourceforge.net \
--cc=breed@users.sourceforge.net \
--cc=dcbw@redhat.com \
--cc=fabrice@bellet.info \
--cc=ivan.matveich@gmail.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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 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).