From: Paul Collins <paul@briny.ondioline.org>
To: Robert Martin <robertm83@gmail.com>
Cc: netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..
Date: Tue, 05 Dec 2006 12:50:25 +1300 [thread overview]
Message-ID: <87ac231ari.fsf@briny.internal.ondioline.org> (raw)
In-Reply-To: <45745D2B.1090700@gmail.com> (Robert Martin's message of "Mon\, 04 Dec 2006 12\:38\:51 -0500")
Robert Martin <robertm83@gmail.com> writes:
> Paul Collins wrote:
>> I started playing with wireless-dev's bcm43xx-d80211 recently and
>> noticed that I had to set the frequency manually. When I did that,
>> setting the ap manually caused the card to associate immediately.
>
> Alas, that seems to have been the problem, I was getting different
> frequencies. Once I manually set the frequency, dhclient worked
> perfectly. The only problem now is that I seem to be limited to very
> slow speeds (on the order of 5-20K/s, or ~120 kilobits/s).
I guess the speed problem is due to the general state of BCM4318
support, as mentioned by the developers.
I'm glad the frequency thing isn't some weird glitch that only I am
experiencing though.
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
next prev parent reply other threads:[~2006-12-04 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 21:21 NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull Robert Martin
2006-12-04 8:30 ` Paul Collins
2006-12-04 13:00 ` Dan Williams
[not found] ` <1165237252.2738.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-12-04 18:28 ` Paul Collins
[not found] ` <45745D2B.1090700@gmail.com>
2006-12-04 23:50 ` Paul Collins [this message]
[not found] ` <45746370.4070205@gmail.com>
[not found] ` <45746370.4070205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2006-12-05 0:28 ` Paul Collins
2006-12-04 23:46 ` Robert Martin
2006-12-04 8:45 ` Johannes Berg
2006-12-04 18:17 ` Robert Martin
2006-12-05 9:25 ` Johannes Berg
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=87ac231ari.fsf@briny.internal.ondioline.org \
--to=paul@briny.ondioline.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=netdev@vger.kernel.org \
--cc=robertm83@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.