From: Rob <capveg@cs.umd.edu>
To: Chris Leishman <masklin@debian.org>
Cc: linuxppc-dev@lists.linuxppc.org, capveg@cs.umd.edu
Subject: Re: airport woes?
Date: Tue, 24 Oct 2000 11:33:46 -0400 [thread overview]
Message-ID: <200010241533.LAA04867@xor.cs.umd.edu> (raw)
In-Reply-To: Your message of "Tue, 24 Oct 2000 15:16:44 +1100." <20001024151644.A660@nina.dev.fol>
>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.
Hope this helps,
- Rob
.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 15:33 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 [this message]
2000-10-24 15:36 ` Chris Leishman
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=200010241533.LAA04867@xor.cs.umd.edu \
--to=capveg@cs.umd.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=masklin@debian.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).