linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jürgen Bausa" <juergen.Bausa@online.de>
To: linux-wireless@vger.kernel.org
Subject: Re: Broadcom 43340
Date: Sat, 21 Mar 2015 20:38:37 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150321T213803-13@post.gmane.org> (raw)
In-Reply-To: 550B4241.4040101@broadcom.com

Arend van Spriel <arend@...> writes:

> 
> 
> CONFIG_BRCM_TRACING is another way to get debug output, but I guess that 
> is not enabled either.
> 

Just found this via google to enable wlan:

1. the nvram file under /sys/firmware/efi/efivars/ has a wrong MAC address.
I changed it to the correct one. However, I am not sure if this is really
necassary.

2. Found the following on the web:

>rmmod brcmfmac
>rmmod brcmutil
>echo on > /sys/bus/platform/drivers/sdhci-acpi/INT33BB\:00/power/control
>modprobe brcmfmac

After this, I can connect to wlan!

Does this give you enough information to find out, what the problem is? Or
do you still need DBG output from the driver? if so, just tell me and I will
try to compile and install the kernel with DBG turnded on. Its not a big
deal but I stopped working on it as I found this workaround.

At the momment I am trying to put these commands to rc,local. With limited
success until now, But this may be caused by the fact, that they are
executed too early. Will add some sleep.

Another thing I found out is, that the system sometimes comes up without
wlan0. It seems I have it only on every second boot. However, this could be
just by incident and it is not exactly every second boot but about 50 % of
all boots.

Juergen




  reply	other threads:[~2015-03-21 20:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550482A2.3080803@gmail.com>
     [not found] ` <55048833.90408@broadcom.com>
     [not found]   ` <55048BB1.9080906@gmail.com>
2015-03-14 19:54     ` Broadcom 43340 Arend van Spriel
2015-03-14 20:07       ` Ochal Christophe
2015-03-14 20:39         ` Stefan Lippers-Hollmann
2015-03-14 22:13           ` Ochal Christophe
2015-03-15 11:37             ` Arend van Spriel
2015-03-15 20:38               ` Jürgen Bausa
2015-03-15 21:14                 ` Arend van Spriel
2015-03-17 21:01                   ` Jürgen Bausa
2015-03-17 22:20                     ` Arend van Spriel
2015-03-18 21:12                       ` Jürgen Bausa
2015-03-17 23:20                     ` Dan Williams
2015-03-18 21:24                       ` Jürgen Bausa
2015-03-18 21:29                         ` Dan Williams
2015-03-18 21:40                           ` Arend van Spriel
2015-03-19 21:00                             ` Jürgen Bausa
2015-03-19 21:40                               ` Arend van Spriel
2015-03-21 20:38                                 ` Jürgen Bausa [this message]
2015-03-22 13:11                                   ` Arend van Spriel
2015-03-22 20:14                                     ` Jürgen Bausa
2015-03-23  9:52                                       ` Arend van Spriel
2015-03-23 20:09                                         ` Jürgen Bausa
2015-03-23 20:50                                           ` Arend van Spriel
2015-03-15 21:20                 ` Stefan Lippers-Hollmann
2015-03-15  2:03       ` Koen Bulcke
2015-03-15 11:39         ` Arend van Spriel

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=loom.20150321T213803-13@post.gmane.org \
    --to=juergen.bausa@online.de \
    --cc=linux-wireless@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).