From: Chris Leishman <masklin@debian.org>
To: Rob <capveg@cs.umd.edu>
Cc: Chris Leishman <masklin@debian.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: airport woes?
Date: Wed, 25 Oct 2000 02:36:42 +1100 [thread overview]
Message-ID: <20001025023642.B2505@nina.dev.fol> (raw)
In-Reply-To: <200010241533.LAA04867@xor.cs.umd.edu>; from capveg@cs.umd.edu on Tue, Oct 24, 2000 at 11:33:46AM -0400
On Tue, Oct 24, 2000 at 11:33:46AM -0400, Rob wrote:
>
> >I'm using benh's latest kernel and airport driver. Now I can't think what
> >would be causing this, but I thought you'd like to know. Anyone else seen
> >this problem?
>
> I have the above (with the patched pcmcia package), bronze lombard 400mhz, and
> everything works for me. It honestly sounds like a lack of signal problem.
> There are a couple of graphical signal strength monitors, or you could do what
> I did, and write a stupid shell script (ask me if you want it) to dredge the
> signal strength out of /proc.
>
I don't think its signal strength, since I'm almost sitting on top of the base
station 90% of the time - and it doesn't seem to affect data coming back to
me.
Also, I've got a pismo - with the built in "apple branded" airport card, and
I'm using BenH's airport driver (not the pcmcia one). Ben mailed me earlier
to say he is working on something...
Thanks,
Chris
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 4:16 airport woes? Chris Leishman
2000-10-24 15:33 ` Rob
2000-10-24 15:36 ` Chris Leishman [this message]
2000-11-02 20:15 ` Rod Stewart
2000-10-26 10:34 ` Topi Kanerva
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=20001025023642.B2505@nina.dev.fol \
--to=masklin@debian.org \
--cc=capveg@cs.umd.edu \
--cc=linuxppc-dev@lists.linuxppc.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).