From: James Anslow <james@jamesanslow.net>
To: b43-dev@lists.infradead.org
Subject: [Bug]No probe response from after 500ms, disconnecting.
Date: Sat, 27 Aug 2011 23:53:58 +0100 [thread overview]
Message-ID: <4E597586.90307@jamesanslow.net> (raw)
In-Reply-To: <CACna6rw9HWCvXcDrmXBe4AssUCC_QZ-6KgEUTGfJYabmuAx2hQ@mail.gmail.com>
On 27/08/11 22:39, Rafa? Mi?ecki wrote:
> W dniu 27 sierpnia 2011 22:42 u?ytkownik Rafa? Mi?ecki
> <zajec5@gmail.com> napisa?:
>> W dniu 26 sierpnia 2011 21:15 u?ytkownik Rafa? Mi?ecki
>> <zajec5@gmail.com> napisa?:
>>> 2011/4/2 Szymon Zygmunt <szymon.zygmunt@gmail.com>:
>>>> 1. A description of the problem at hand:
>>>> Last time I changed my wireless card and I have problems with wireless
>>>> link when I copy large files over lan. Link is broken after some part of
>>>> file (eg. 50 - 200 MB) and I have to reload my b43 driver (modprobe -r
>>>> b43, modprobe b43). After that connection work again for a while and
>>>> situation is repeated.
>>>>
>>>> 2. When it happens:
>>>> Always when I copy large file from my ftp (sets on openwrt box) to my PC
>>>> over wifi.
>>>>
>>>> 3. How to reproduce:
>>>> Start to operation with high transmission rates (eg. copy larg file)
>>> Szymon, this is a damn late reply and I think I understand if you've
>>> already switched to some other card.
>>>
>>> In case you're still using b43 & BCM4318: did you manage to fix this
>>> problem yourself?
>> I've tested my BCM4318 which is
>> 06:05.0 0280: 14e4:4318 (rev 02)
>> Subsystem: 1468:0311
>> and it still works fine after using iperf for 20 minutes (about 3.2 GB
>> transfered to my notebook with 14e4:4318). Average speed was 22.5 Mb/s
>> and I was quite close to the AP.
>>
>> I'll try:
>> 1) Switching to the 478.104 firmware
>> 2) Using ftp instead of iperf
>> 3) Moving to some other room, to increase distance
> I've tried switching between firmwares 410.2160, 478.104 and 508.1092,
> without any difference.
>
> I've moved away from AP, the RX speed went down to 11.6 Mb/s (tested
> for 5 minutes), but not visible problems (received 414 MB).
>
> I guess Szymon can have affected BCM4318, will I don't. From
> https://forum.openwrt.org/viewtopic.php?id=24208 :
>> b43 in Backfire works on most BCM4306-BCM4318-based cards, included master (AP) mode. Unfortunately there are some models of BCM4318 which suffer from transmission problems and are unstable as a result, mostly noticeably when running as AP. Others models of BCM4318 seems to run fine.
Hi,
I just wanted to drop you a mail back to say thanks a lot for your help
and for your hard work.
I now have wlan on my mbp thanks to your instructions- life saver! :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110827/66205023/attachment.sig>
prev parent reply other threads:[~2011-08-27 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 21:48 [Bug]No probe response from after 500ms, disconnecting Szymon Zygmunt
2011-08-26 19:15 ` Rafał Miłecki
2011-08-27 20:42 ` Rafał Miłecki
2011-08-27 21:39 ` Rafał Miłecki
2011-08-27 22:53 ` James Anslow [this message]
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=4E597586.90307@jamesanslow.net \
--to=james@jamesanslow.net \
--cc=b43-dev@lists.infradead.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).