From: Robert Martin <robertm83@gmail.com>
To: Robert Martin <robertm83@gmail.com>,
netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..
Date: Mon, 04 Dec 2006 18:46:35 -0500 [thread overview]
Message-ID: <4574B35B.5070207@gmail.com> (raw)
In-Reply-To: <8764cr190q.fsf@briny.internal.ondioline.org>
Paul Collins wrote:
> (Please use reply-to-all to keep Cc:s intact, and place new material
> below quoted material.)
>
> Robert Martin <robertm83@gmail.com> writes:
>
>
>> Paul Collins wrote:
>>
>>> Robert Martin <robertm83@gmail.com> writes:
>>>
>>>
>>>> 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.
>>>
>>>
>> I'm pretty sure that I'm using a 4311 chip... lspci -n gives...
>>
>> 03:00.0 0280: 14e4:4311 (rev 01)
>>
>> ...I might have been mistaken about it being a PCI-E chip in that
>> case. One additional question, it seems the link quality is very low;
>> "iwconfig wlan0" tells me it's 3/100 after associating with my AP.
>> Could that be the power issue that Johannes Berg was speaking of? I'm
>> curious as to what speeds you're running at, and what your link
>> quality is.
>>
>
> My card (a 4306) seems to be running at 11Mbps. No idea how to change
> it: iwconfig doesn't report the current rate (I had to go digging in
> sysfs) and trying to change it with iwconfig fails with "Operation not
> supported".
>
> Here's the signal info:
>
> Link Quality=228/100 Signal level=-32 dBm Noise level=-70 dBm
>
> The machine is about 3 metres from the AP.
>
>
A quick test just incase the information is somehow helpful... I moved
to within two meters of my AP with nothing blocking the way--the link
quality jumped up to 46/100 (vs 3/100 5m away and a wall blocking),
though there was no increase in speed (still limited to ~120 kilobits/s).
Before: Link Quality=3/100 Signal level=-73 dBm Noise level=-66 dBm
After: Link Quality=46/100 Signal level=-49 dBm Noise level=-69 dBm
next prev parent reply other threads:[~2006-12-05 0:46 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
[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 [this message]
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=4574B35B.5070207@gmail.com \
--to=robertm83@gmail.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).