linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: <linux-wireless@vger.kernel.org>, b43-dev <b43-dev@lists.infradead.org>
Subject: Re: b43 bcm43228 and linux 3.18.3
Date: Mon, 19 Jan 2015 16:45:08 +0100	[thread overview]
Message-ID: <54BD2684.30701@broadcom.com> (raw)
In-Reply-To: <CACaajQs1r1tE-GXv7cmAL9w8q2cwn_iiDttp6tLFB7BdSBNDPw@mail.gmail.com>

+ b43-dev@lists.infradead.org

On 01/19/15 13:20, Vasiliy Tolstov wrote:
> Anybody can helps me debug this?
>
> 2015-01-17 20:59 GMT+03:00 Vasiliy Tolstov<v.tolstov@selfip.ru>:
>> Hi all. I have 3.18.3 kernel and bcm43228, firstly all works fine, but
>> after connection with my zyxel router i can't ping it ip (after 1-2
>> min). Connection worked fin, but nothing transmitted =(.
>> I'm try to disable qos, but this not helps, i'm try to enable
>> verbose=3, but in dmesg nothing interesting. Time after time b43
>> driver moved from 5Ghz to 2.4Ghz to 5Ghz and so.

What do you mean by "moved from 5Ghz to 2.4Ghz..". You mean it is 
roaming between the two bands? Anyway, there is a b43 specific mailing 
list which I added.

Regards,
Arend

>> How can i debug this issue? I'm realy love free opensource drivers.
>> Thanks
>>
>> --
>> Vasiliy Tolstov,
>> e-mail: v.tolstov@selfip.ru
>> jabber: vase@selfip.ru
>
>
>


  reply	other threads:[~2015-01-19 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17 17:59 b43 bcm43228 and linux 3.18.3 Vasiliy Tolstov
2015-01-19 12:20 ` Vasiliy Tolstov
2015-01-19 15:45   ` Arend van Spriel [this message]
2015-01-20 10:24     ` Vasiliy Tolstov
2015-01-20 10:31       ` Arend van Spriel
2015-01-20 10:48         ` Vasiliy Tolstov
2015-02-22 21:31           ` Vasiliy Tolstov

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=54BD2684.30701@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=v.tolstov@selfip.ru \
    /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).