From: Ryan Boder <boder@cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: airport transmit power
Date: 19 Mar 2002 01:39:53 -0500 [thread overview]
Message-ID: <1016519993.843.21.camel@TOBY> (raw)
I'm using airport in a big 802.11b network at school, with access points
all around campus. I have noticed that networking does not work as well
for me as it does for those using intel machines.
But the thing I just noticed tonight, is that my machine seems to
receive signals just as well as the intel machines, it's the
transmissions that cause trouble.
For example, I was downloading a 700 MB files and it kept downloading
withought a problem, but at the same time, I was trying to work on a
remote machine with ssh and it was acting really bad. Sometimes it would
not respond to my keyboard pressing for 30 seconds or more.
I also noticed that this is the only available txpower from iwlist.
eth1 1 available transmit-powers :
15 dBm (31 mW)
So for anyone who hacks the aiport driver, is that the only txpower the
card supports? Is it a hardware limitation or a driver limitation? Or is
it something that's unknown since apple won't release the documentation?
Ryan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-03-19 6:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1016519993.843.21.camel@TOBY \
--to=boder@cmu.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).