From: Russell King <rmk@arm.linux.org.uk>
To: peterc@gelato.unsw.edu.au
Cc: david@gibson.dropbear.id.au, linux-kernel@vger.kernel.org
Subject: Re: Ejecting an orinoco card causes hang
Date: Wed, 23 Oct 2002 08:55:02 +0100 [thread overview]
Message-ID: <20021023085501.A22736@flint.arm.linux.org.uk> (raw)
In-Reply-To: <15797.63740.520358.783516@wombat.chubb.wattle.id.au>; from peterc@gelato.unsw.edu.au on Wed, Oct 23, 2002 at 11:18:52AM +1000
On Wed, Oct 23, 2002 at 11:18:52AM +1000, peterc@gelato.unsw.edu.au wrote:
> 4. Transferring lots of data causes the link to collapse, and the
> logs to fill up with `eth0: Error -110 writing Tx descriptor to
> BAP' messages
I see type of behaviour this with an Orinoco Silver card while trying to
set the mode/essid. I took the wvlan_cs code from my RH7.2 box and dropped
it into 2.5 - seems to work (although how reliable it is I don't know yet;
I need to get something for this card to talk to.)
http://ftp.linux.org.uk/pub/linux/rmk/wireless/wvlan_cs-2.5.44.diff
Another difference that I noticed was that when no AP is in range, and the
ESSID has never been set, orinoco v0.07 reports "unspecified SSID!!!" as
the ESSID, as does wvlan_cs on the same RH7.2 kernel and with wvlan_cs on
2.5.44. However, orinoco 0.13a reports an empty string.
Looking at the bytes read off the card, it seems that it returns a zero
length word, followed by the string "unspecified SSID!!!" with orinoco
0.13a.
Also, (iirc) I could make the card happier with the orinoco 0.13a driver
if I made it read excess bytes when reading the BAP (like wvlan_cs does.)
However, this didn't competely solve the problem - I still saw what I
think are firmware crashes.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-23 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 1:18 peterc
2002-10-23 6:37 ` David Gibson
2002-10-23 7:55 ` Russell King [this message]
2002-12-04 4:54 ` David Gibson
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=20021023085501.A22736@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/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