From: Alexander Hoogerhuis <alexh@ihatent.com>
To: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCMCIA and hermer/orinoco_cs drivers b0rken?
Date: 31 Dec 2002 06:44:16 +0100 [thread overview]
Message-ID: <878yy6zqrz.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <20021230085529.GA12575@localhost>
"Joshua M. Kwan" <joshk@ludicrus.ath.cx> writes:
> > Warning: Driver for device eth1 has been compiled with version 14
> > of Wireless Extension, while this program is using version 13.
> > Some things may be broken...
>
> First of all, what kernel are you using? That's an ancient version of
> the WE. If this is 2.4.2[01], download the following diffs from Jean's
> fine site:
>
> * http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/iw240_we15-6.diff
> * http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/iw241_we16-3.diff
>
No warnings anymore, and it all works. I now have a full 2 yards of
wireless netowrk and dont have to run a cat5 over to muy couch :)
Apart from that, Jean Tourrilhes' site was a treasure of HOWTOs and
FAQs, so I'll spend a lot of time reading up there. Next thing up is
bluetooth, and the site seems to be the right place for that, too.
> Next of all, try upgrading the firmware on your card.
>
Went trough the motions of finding NetGears support on this. NetGear
now officially has landed on my list of gear not to recommend. The
while sitiation on finding firmware and tools to flash it didn't
strike me as very orderly, and I ended up using some Dlink tools I
found through Google to get my card slightly upgraded, but it seemed
to do the trick. The other Lucent/Orinoco card I had was more simple
and done in a few minutes.
> The error writing packet to BAP error always seemed just like a small
> nuisance to me during large file transfers. It did not correlate with
> any connectivity problems, so I just commented it out in the
> orinoco/hermes/orinoco_cs source (it's in one of those files.)
>
I never got to try it on large files, I had a few dozen errors from a
card idling with no connectivity :)
> Hope your wireless endeavors succeed - I just spent all week getting
> hostap_plx to work (and I'm now reaping the benefits because I now have
> wifi access all over my house) :)
>
Any benefit of using an AP over an ad-hoc network if it's only two or
three nodes in a room?
> Regards
> -Josh
>
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
next prev parent reply other threads:[~2002-12-31 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 17:10 PCMCIA and hermer/orinoco_cs drivers b0rken? Alexander Hoogerhuis
2002-12-26 8:34 ` Joshua Kwan
2002-12-30 4:17 ` Alexander Hoogerhuis
2002-12-30 8:55 ` Joshua M. Kwan
2002-12-30 9:04 ` Alexander Hoogerhuis
2002-12-31 5:44 ` Alexander Hoogerhuis [this message]
2002-12-31 7:55 ` Joshua Kwan
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=878yy6zqrz.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=joshk@ludicrus.ath.cx \
--cc=linux-kernel@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