Re: Broadcom 43340

Re: Broadcom 43340

[Arend van Spriel]

+ linux-wireless

On 03/14/15 20:27, Ochal Christophe wrote:
> Dear Sir,
>
> On 03/14/2015 08:12 PM, Arend van Spriel wrote:
>> The nvram file is board specific and so Asus should be able to provide
>> that. What OS does Asus provide on this eee book? The firmware file
>> will be submitted to linux-firmware soon, but in the mean time you can
>> also find it in Android repository [1]. Just rename the file
>> fw_43341.bin to brcmfmac43340-sdio.bin.
>>
>> Regards,
>> Arend
>>
>> [1]
>> https://android.googlesource.com/platform/hardware/broadcom/wlan/+/master/bcmdhd/firmware/bcm43341/
>>
>
> Thank you for the link, the Asus eebook x205ta comes with Windows 8.1,
> no idea how I'm going to get Asus to deliver that nvram, but at least
> I'm halfway there now, the firmware loads correctly.

For Windows 8.1 the nvram file is stored in EFI variable space. This is 
accessible in Linux as well. If I recall correctly it should be in 
/sys/firmware/efi/efivars. There should be a file named nvram-*. Copy 
that to /lib/firmware/brcm/brcmfmac43340-sdio.txt.

Regards,
Arend

Re: Broadcom 43340

[Ochal Christophe]

Dear Sir,

On 03/14/2015 08:54 PM, Arend van Spriel wrote:
> For Windows 8.1 the nvram file is stored in EFI variable space. This 
> is accessible in Linux as well. If I recall correctly it should be in 
> /sys/firmware/efi/efivars. There should be a file named nvram-*. Copy 
> that to /lib/firmware/brcm/brcmfmac43340-sdio.txt.
>
Okay.... Kind of wish I knew that a few hours ago before I formatted the 
thing :)
I'll see if I can either reinstall Windows on it (somehow) or find 
someone with the same machine, I'm getting close to get pretty much 
everything running

If I can get the file, should I send it to you?

With kind regards,
Christophe Ochal

Re: Broadcom 43340

[Stefan Lippers-Hollmann]

Hi

On 2015-03-14, Ochal Christophe wrote:
> Dear Sir,
> 
> On 03/14/2015 08:54 PM, Arend van Spriel wrote:
> > For Windows 8.1 the nvram file is stored in EFI variable space. This 
> > is accessible in Linux as well. If I recall correctly it should be in 
> > /sys/firmware/efi/efivars. There should be a file named nvram-*. Copy 
> > that to /lib/firmware/brcm/brcmfmac43340-sdio.txt.
> >
> Okay.... Kind of wish I knew that a few hours ago before I formatted the 
> thing :)
> I'll see if I can either reinstall Windows on it (somehow) or find 
> someone with the same machine, I'm getting close to get pretty much 
> everything running

You don't need to run windows for that, the nvram (calibration data, 
probably the MAC address and related device specific data) is stored in 
your mainboard's firmware - and exposed to userspace (under linux) via
/sys/firmware/efi/efivars/. You just need to identify the correct file
and copy it to a place where linux expects to find it 
(/lib/firmware/brcm/brcmfmac43340-sdio.txt).

Regards
	Stefan Lippers-Hollmann

Re: Broadcom 43340

[Ochal Christophe]

All,

On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
> You don't need to run windows for that, the nvram (calibration data, 
> probably the MAC address and related device specific data) is stored 
> in your mainboard's firmware - and exposed to userspace (under linux) 
> via /sys/firmware/efi/efivars/. You just need to identify the correct 
> file and copy it to a place where linux expects to find it 
> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan 
> Lippers-Hollmann 

Thanks for the hint, that did it, I'm online!

With Kind Regards,
Christophe Ochal

Re: Broadcom 43340

[Arend van Spriel]

On 03/14/15 23:13, Ochal Christophe wrote:
> All,
>
> On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
>> You don't need to run windows for that, the nvram (calibration data,
>> probably the MAC address and related device specific data) is stored
>> in your mainboard's firmware - and exposed to userspace (under linux)
>> via /sys/firmware/efi/efivars/. You just need to identify the correct
>> file and copy it to a place where linux expects to find it
>> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan
>> Lippers-Hollmann
>
> Thanks for the hint, that did it, I'm online!

Apparently my hint was not clear enough. Good to hear it works for you.

Regards,
Arend

Re: Broadcom 43340

[Jürgen Bausa]

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

> 
> On 03/14/15 23:13, Ochal Christophe wrote:
> > All,
> >
> > On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
> >> You don't need to run windows for that, the nvram (calibration data,
> >> probably the MAC address and related device specific data) is stored
> >> in your mainboard's firmware - and exposed to userspace (under linux)
> >> via /sys/firmware/efi/efivars/. You just need to identify the correct
> >> file and copy it to a place where linux expects to find it
> >> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan
> >> Lippers-Hollmann
> >
> > Thanks for the hint, that did it, I'm online!
> 
> Apparently my hint was not clear enough. Good to hear it works for you.
> 

Dear Arend,

would be nice, if you could make it clear.

I am in the exact some position (asus x205 with linux 4.0 rc3) but my
/sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
kernel taken from ubuntu. Am I missing something? Even loading efivars via
modprobe doesnt change a thing.

Juergen

Re: Broadcom 43340

[Arend van Spriel]

On 03/15/15 21:38, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>
>>
>> On 03/14/15 23:13, Ochal Christophe wrote:
>>> All,
>>>
>>> On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
>>>> You don't need to run windows for that, the nvram (calibration data,
>>>> probably the MAC address and related device specific data) is stored
>>>> in your mainboard's firmware - and exposed to userspace (under linux)
>>>> via /sys/firmware/efi/efivars/. You just need to identify the correct
>>>> file and copy it to a place where linux expects to find it
>>>> (/lib/firmware/brcm/brcmfmac43340-sdio.txt). Regards Stefan
>>>> Lippers-Hollmann
>>>
>>> Thanks for the hint, that did it, I'm online!
>>
>> Apparently my hint was not clear enough. Good to hear it works for you.
>>
>
> Dear Arend,
>
> would be nice, if you could make it clear.
>
> I am in the exact some position (asus x205 with linux 4.0 rc3) but my
> /sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
> kernel taken from ubuntu. Am I missing something? Even loading efivars via
> modprobe doesnt change a thing.

Maybe you need to mount it. This is what I found [1]:

$ sudo mount -t efivarfs none /sys/firmware/efi/efivars

Regards,
Arend

[1] http://firmware.intel.com/blog/accessing-uefi-variables-linux

> Juergen
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Broadcom 43340

[Jürgen Bausa]

QXJlbmQgdmFuIFNwcmllbCA8YXJlbmRALi4uPiB3cml0ZXM6Cgo+IAo+IE9uIDAzLzE1LzE1IDIxOjM4LCBKw7xyZ2VuIEJhdXNhIHdyb3RlOgo+ID4KPiA+IHdvdWxkIGJlIG5pY2UsIGlmIHlvdSBjb3VsZCBtYWtlIGl0IGNsZWFyLgo+ID4KPiAKPiBNYXliZSB5b3UgbmVlZCB0byBtb3VudCBpdC4gVGhpcyBpcyB3aGF0IEkgZm91bmQgWzFdOgo+IAo+ICQgc3VkbyBtb3VudCAtdCBlZml2YXJmcyBub25lIC9zeXMvZmlybXdhcmUvZWZpL2VmaXZhcnMKPiAKClRoYW5rcywgdGhhdCB3b3JrZWQuIE5vdyBJIGhhdmUgZmlybXdhcmUgYW5kIG52cmFtLWZpbGUgYW5kIHRoZSBkcml2ZXIgc2VlbXMKdG8gbG9hZCBvay4gQXQgbGVhc3QgSSBoYXZlIGFuIGludGVyZmFjZSB3bGFuMC4KCkhvd2V2ZXIsIEkgYW0gbm90IGFibGUgdG8gY29ubmVjdC5OZXR3b3JrLW1hbmFnZXIganVzdCBzYXlzICJpbnRlcmZhY2UgaXMKYmVpbmcgc2V0IHVwIC4uLiIgZm9yZXZlci4gSSBoYXZlIG5vIGlkZWEgaG93dG8gZGVidWcgdGhpcy4gSW4gdGhlIG90aGVyCnBvc3QgeW91IHNhaWQgdGhhdCB0aGUgbmw4MDIxMSBkcml2ZXIgc2hvdWxkIGJlIHVzZWQgaW5zdGVhZCBvZiB3ZXh0LiBJCmZvdW5kIHRoYXQgbmw4MDIxMSBpcyB0aGUgZGVmYXVsdCBmb3IgbmV0d29yay1tYW5hZ2VyLiBTbywgd2hhdHMgZ29pbmcgd3JvbmcKaGVyZT8KCgpKdWVyZ2Vu

Re: Broadcom 43340

[Arend van Spriel]

On 03/17/15 22:01, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>
>>
>> On 03/15/15 21:38, Jürgen Bausa wrote:
>>>
>>> would be nice, if you could make it clear.
>>>
>>
>> Maybe you need to mount it. This is what I found [1]:
>>
>> $ sudo mount -t efivarfs none /sys/firmware/efi/efivars
>>
>
> Thanks, that worked. Now I have firmware and nvram-file and the driver seems
> to load ok. At least I have an interface wlan0.
>
> However, I am not able to connect.Network-manager just says "interface is
> being set up ..." forever. I have no idea howto debug this. In the other
> post you said that the nl80211 driver should be used instead of wext. I
> found that nl80211 is the default for network-manager. So, whats going wrong
> here?

Could you provide output of these:

$ iw dev
$ iw list
$ ifconfig -a

Regards,
Arend

Re: Broadcom 43340

[Jürgen Bausa]

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

> 
> On 03/17/15 22:01, Jürgen Bausa wrote:
> >
> > Thanks, that worked. Now I have firmware and nvram-file and the driver 
seems
> > to load ok. At least I have an interface wlan0.
> >
> > However, I am not able to connect.Network-manager just says "interface is
> > being set up ..." forever. I have no idea howto debug this. In the other
> > post you said that the nl80211 driver should be used instead of wext. I
> > found that nl80211 is the default for network-manager. So, whats going 
wrong
> > here?
> 
> Could you provide output of these:
> 
> $ iw dev
> $ iw list
> $ ifconfig -a
> 

Here it is.

Juergen

root@lina:/home/jba# iw dev
phy#0
        Interface wlan0
                ifindex 2
                wdev 0x1
                addr 6c:fa:a7:34:50:7a
                type managed
root@lina:/home/jba# iw list
Wiphy phy0
        max # scan SSIDs: 10
        max scan IEs length: 2048 bytes
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports roaming.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP (00-0f-ac:4)
                * CMAC (00-0f-ac:6)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * P2P-client
                 * P2P-GO
                 * P2P-device
        Band 1:
                Capabilities: 0x1022
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        No RX STBC
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 16 usec (0x07)                                                                                                                                   
                HT TX/RX MCS rate indexes supported: 0-7                                                                                                                                        
                Bitrates (non-HT):                                                                                                                                                              
                        * 1.0 Mbps                                                                                                                                                              
                        * 2.0 Mbps (short preamble supported)                                                                                                                                   
                        * 5.5 Mbps (short preamble supported)                                                                                                                                   
                        * 11.0 Mbps (short preamble supported)                                                                                                                                  
                        * 6.0 Mbps                                                                                                                                                              
                        * 9.0 Mbps                                                                                                                                                              
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (no IR)
                        * 2472 MHz [13] (20.0 dBm) (no IR)
                        * 2484 MHz [14] (20.0 dBm) (no IR)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * join_ibss
                 * set_pmksa
                 * del_pmksa
                 * flush_pmksa
                 * remain_on_channel
                 * frame
                 * set_channel
                 * start_sched_scan
                 * start_p2p_device
                 * crit_protocol_start
                 * crit_protocol_stop
                 * connect
                 * disconnect
        Supported TX frame types:
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * managed: 0x40 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-device: 0x40 0xd0
        software interface modes (can always be added):
        valid interface combinations:
                 * #{ IBSS, managed } <= 1, #{ AP } <= 4, #{ P2P-client, P2P-
GO } <= 1, #{ P2P-device } <= 1,
                   total <= 3, #channels <= 2
        Device supports scan flush.
root@lina:/home/jba# ifconfig -a
lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX packets:178 errors:0 dropped:0 overruns:0 frame:0
          TX packets:178 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:16028 (15.6 KiB)  TX bytes:16028 (15.6 KiB)

wlan0     Link encap:Ethernet  Hardware Adresse 6c:fa:a7:34:50:7a  
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX packets:54 errors:0 dropped:54 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:20848 (20.3 KiB)  TX bytes:0 (0.0 B)

root@lina:/home/jba# 


Re: Broadcom 43340

[Dan Williams]

On Tue, 2015-03-17 at 21:01 +0000, Jürgen Bausa wrote:
> Arend van Spriel <arend@...> writes:
> 
> > 
> > On 03/15/15 21:38, Jürgen Bausa wrote:
> > >
> > > would be nice, if you could make it clear.
> > >
> > 
> > Maybe you need to mount it. This is what I found [1]:
> > 
> > $ sudo mount -t efivarfs none /sys/firmware/efi/efivars
> > 
> 
> Thanks, that worked. Now I have firmware and nvram-file and the driver seems
> to load ok. At least I have an interface wlan0.
> 
> However, I am not able to connect.Network-manager just says "interface is
> being set up ..." forever. I have no idea howto debug this. In the other
> post you said that the nl80211 driver should be used instead of wext. I
> found that nl80211 is the default for network-manager. So, whats going wrong
> here?

Could you provide more NetworkManager logs?  They should look like this;
where do your logs stop?

NetworkManager[1949]: <info>  (wlan0): Activation: starting connection 'my wifi'
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 1 of 5 (Device Prepare) started...
NetworkManager[1949]: <info>  (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 1 of 5 (Device Prepare) complete.
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 2 of 5 (Device Configure) starting...
NetworkManager[1949]: <info>  (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[1949]: <info>  (wlan0): Activation: (wifi) connection 'my wifi' has security, and secrets exist.  No new secrets needed.
NetworkManager[1949]: <info>  Config: added 'ssid' value 'my wifi'
NetworkManager[1949]: <info>  Config: added 'scan_ssid' value '1'
NetworkManager[1949]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[1949]: <info>  Config: added 'psk' value '<omitted>'
NetworkManager[1949]: <info>  Config: added 'proto' value 'WPA RSN'
NetworkManager[1949]: <info>  (wlan0): Activation: Stage 2 of 5 (Device Configure) complete.
NetworkManager[1949]: <info>  Config: set interface ap_scan to 1
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: inactive -> scanning
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: scanning -> authenticating
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: authenticating -> associating
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: associating -> associated
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: associated -> 4-way handshake
NetworkManager[1949]: <info>  (wlan0): supplicant interface state: 4-way handshake -> completed

Dan

Re: Broadcom 43340

[Jürgen Bausa]

Dan Williams <dcbw@...> writes:

> 
> > 
> > Thanks, that worked. Now I have firmware and nvram-file and the driver 
seems
> > to load ok. At least I have an interface wlan0.
> > 
> > However, I am not able to connect.Network-manager just says "interface is
> > being set up ..." forever. I have no idea howto debug this. In the other
> > post you said that the nl80211 driver should be used instead of wext. I
> > found that nl80211 is the default for network-manager. So, whats going 
wrong
> > here?
> 
> Could you provide more NetworkManager logs?  They should look like this;
> where do your logs stop?
> 


Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) starting 
connection 'tuxgang'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): device state 
change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 22:16:40 lina NetworkManager[532]: <info> NetworkManager state is now 
CONNECTING
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): device state 
change: prepare -> config (reason 'none') [40 50 0]
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'ssid' value 
'tuxgang'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
value '1'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
value 'WPA-PSK'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
value 'OPEN'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'psk' value 
'<omitted>'
Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: set interface 
ap_scan to 1
Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: inactive -> scanning
Mar 18 22:16:50 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: scanning -> associating
Mar 18 22:17:00 lina NetworkManager[532]: <warn> Connection disconnected 
(reason -3)
Mar 18 22:17:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: associating -> disconnected
Mar 18 22:17:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: disconnected -> scanning
Mar 18 22:17:05 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
association took too long.
Mar 18 22:17:05 lina NetworkManager[532]: <info> (wlan0): device state 
change: config -> need-auth (reason 'none') [50 60 0]
Mar 18 22:17:05 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
asking for new secrets
Mar 18 22:17:05 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:17:05 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:17:29 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
secret_name, error)' failed
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): device state 
change: need-auth -> prepare (reason 'none') [60 40 0]
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): device state 
change: prepare -> config (reason 'none') [40 50 0]
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'ssid' value 
'tuxgang'
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
value '1'
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
value 'WPA-PSK'
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
value 'OPEN'
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'psk' value 
'<omitted>'
Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
Mar 18 22:17:29 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: set interface 
ap_scan to 1
Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: scanning -> associated
Mar 18 22:17:29 lina NetworkManager[532]: <warn> Connection disconnected 
(reason -3)
Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: associated -> disconnected
Mar 18 22:17:29 lina NetworkManager[532]: <warn> Connection disconnected 
(reason 6)
Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: disconnected -> scanning
Mar 18 22:17:39 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: scanning -> associating
Mar 18 22:17:49 lina NetworkManager[532]: <warn> Connection disconnected 
(reason -3)
Mar 18 22:17:49 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: associating -> disconnected
Mar 18 22:17:49 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: disconnected -> scanning
Mar 18 22:17:54 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
association took too long.
Mar 18 22:17:54 lina NetworkManager[532]: <info> (wlan0): device state 
change: config -> need-auth (reason 'none') [50 60 0]
Mar 18 22:17:54 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
asking for new secrets
Mar 18 22:17:54 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:17:54 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:18:00 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
secret_name, error)' failed
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
change: need-auth -> prepare (reason 'none') [60 40 0]
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
change: prepare -> config (reason 'none') [40 50 0]
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'ssid' value 
'tuxgang'
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
value '1'
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
value 'WPA-PSK'
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
value 'OPEN'
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'psk' value 
'<omitted>'
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
Mar 18 22:18:00 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: set interface 
ap_scan to 1
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: scanning -> 4-way handshake
Mar 18 22:18:00 lina NetworkManager[532]: <warn> Connection disconnected 
(reason 6)
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: 4-way handshake -> disconnected
Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
disconnected during association, asking for new key.
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: disconnected -> inactive
Mar 18 22:18:07 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
secret_name, error)' failed
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): device state 
change: need-auth -> prepare (reason 'none') [60 40 0]
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): device state 
change: prepare -> config (reason 'none') [40 50 0]
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'ssid' value 
'tuxgang'
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
value '1'
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
value 'WPA-PSK'
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
value 'OPEN'
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'psk' value 
'<omitted>'
Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: set interface 
ap_scan to 1
Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: inactive -> associating
Mar 18 22:18:17 lina NetworkManager[532]: <warn> Connection disconnected 
(reason -3)
Mar 18 22:18:17 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: associating -> disconnected
Mar 18 22:18:17 lina NetworkManager[532]: <info> (wlan0): supplicant 
interface state: disconnected -> scanning
Mar 18 22:18:32 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
association took too long.
Mar 18 22:18:32 lina NetworkManager[532]: <info> (wlan0): device state 
change: config -> need-auth (reason 'none') [50 60 0]
Mar 18 22:18:32 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
asking for new secrets
Mar 18 22:18:32 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.
Mar 18 22:18:32 lina NetworkManager[532]: <warn> Couldn't disconnect 
supplicant interface: This interface is not connected.

Re: Broadcom 43340

[Dan Williams]

On Wed, 2015-03-18 at 21:24 +0000, Jürgen Bausa wrote:
> Dan Williams <dcbw@...> writes:
> 
> > 
> > > 
> > > Thanks, that worked. Now I have firmware and nvram-file and the driver 
> seems
> > > to load ok. At least I have an interface wlan0.
> > > 
> > > However, I am not able to connect.Network-manager just says "interface is
> > > being set up ..." forever. I have no idea howto debug this. In the other
> > > post you said that the nl80211 driver should be used instead of wext. I
> > > found that nl80211 is the default for network-manager. So, whats going 
> wrong
> > > here?
> > 
> > Could you provide more NetworkManager logs?  They should look like this;
> > where do your logs stop?
> > 
> 
> 
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) starting 
> connection 'tuxgang'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) scheduled...
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) started...
> Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): device state 
> change: disconnected -> prepare (reason 'none') [30 40 0]
> Mar 18 22:16:40 lina NetworkManager[532]: <info> NetworkManager state is now 
> CONNECTING
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) scheduled...
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) complete.
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) starting...
> Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): device state 
> change: prepare -> config (reason 'none') [40 50 0]
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'ssid' value 
> 'tuxgang'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
> value '1'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
> value 'WPA-PSK'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
> value 'OPEN'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: added 'psk' value 
> '<omitted>'
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) complete.
> Mar 18 22:16:40 lina NetworkManager[532]: <info> Config: set interface 
> ap_scan to 1
> Mar 18 22:16:40 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: inactive -> scanning
> Mar 18 22:16:50 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: scanning -> associating
> Mar 18 22:17:00 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason -3)

Something is still wrong with the driver/device.  Here, even though a
scan has already been done and the SSID found (otherwise NM wouldn't
have started a connection in the first place) the supplicant is doing
another scan (10s) and then attempting to associate, which takes 10s
before NM kills the attempt.

So ignoring the scan issues (eg, why is another 10s scan requires when
the SSID is already in the supplicant's network list) it still has
association problems.

NetworkManager allows up to 20s for an auth/assoc since that really,
really should be enough.  If it's not enough, then something is
seriously wrong with the hardware or the wifi network.

Next steps:

What does 'dmesg' say here?  Anything about association tries?

After that we try getting supplicant debug logs and figuring out what's
going on from its point of view.


Dan

> Mar 18 22:17:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: associating -> disconnected
> Mar 18 22:17:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: disconnected -> scanning
> Mar 18 22:17:05 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> association took too long.
> Mar 18 22:17:05 lina NetworkManager[532]: <info> (wlan0): device state 
> change: config -> need-auth (reason 'none') [50 60 0]
> Mar 18 22:17:05 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> asking for new secrets
> Mar 18 22:17:05 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:17:05 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:17:29 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
> secret_name, error)' failed
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) scheduled...
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) started...
> Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): device state 
> change: need-auth -> prepare (reason 'none') [60 40 0]
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) scheduled...
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) complete.
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) starting...
> Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): device state 
> change: prepare -> config (reason 'none') [40 50 0]
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'ssid' value 
> 'tuxgang'
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
> value '1'
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
> value 'WPA-PSK'
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
> value 'OPEN'
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: added 'psk' value 
> '<omitted>'
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) complete.
> Mar 18 22:17:29 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:17:29 lina NetworkManager[532]: <info> Config: set interface 
> ap_scan to 1
> Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: scanning -> associated
> Mar 18 22:17:29 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason -3)
> Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: associated -> disconnected
> Mar 18 22:17:29 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason 6)
> Mar 18 22:17:29 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: disconnected -> scanning
> Mar 18 22:17:39 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: scanning -> associating
> Mar 18 22:17:49 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason -3)
> Mar 18 22:17:49 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: associating -> disconnected
> Mar 18 22:17:49 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: disconnected -> scanning
> Mar 18 22:17:54 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> association took too long.
> Mar 18 22:17:54 lina NetworkManager[532]: <info> (wlan0): device state 
> change: config -> need-auth (reason 'none') [50 60 0]
> Mar 18 22:17:54 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> asking for new secrets
> Mar 18 22:17:54 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:17:54 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:18:00 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
> secret_name, error)' failed
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) scheduled...
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) started...
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
> change: need-auth -> prepare (reason 'none') [60 40 0]
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) scheduled...
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) complete.
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) starting...
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
> change: prepare -> config (reason 'none') [40 50 0]
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'ssid' value 
> 'tuxgang'
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
> value '1'
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
> value 'WPA-PSK'
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
> value 'OPEN'
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: added 'psk' value 
> '<omitted>'
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) complete.
> Mar 18 22:18:00 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Config: set interface 
> ap_scan to 1
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: scanning -> 4-way handshake
> Mar 18 22:18:00 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason 6)
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: 4-way handshake -> disconnected
> Mar 18 22:18:00 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
> disconnected during association, asking for new key.
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): device state 
> change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
> Mar 18 22:18:00 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: disconnected -> inactive
> Mar 18 22:18:07 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, 
> secret_name, error)' failed
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) scheduled...
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) started...
> Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): device state 
> change: need-auth -> prepare (reason 'none') [60 40 0]
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) scheduled...
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 1 
> of 5 (Device Prepare) complete.
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) starting...
> Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): device state 
> change: prepare -> config (reason 'none') [40 50 0]
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0/wireless): 
> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'ssid' value 
> 'tuxgang'
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'scan_ssid' 
> value '1'
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'key_mgmt' 
> value 'WPA-PSK'
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'auth_alg' 
> value 'OPEN'
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: added 'psk' value 
> '<omitted>'
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Activation (wlan0) Stage 2 
> of 5 (Device Configure) complete.
> Mar 18 22:18:07 lina NetworkManager[532]: <info> Config: set interface 
> ap_scan to 1
> Mar 18 22:18:07 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: inactive -> associating
> Mar 18 22:18:17 lina NetworkManager[532]: <warn> Connection disconnected 
> (reason -3)
> Mar 18 22:18:17 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: associating -> disconnected
> Mar 18 22:18:17 lina NetworkManager[532]: <info> (wlan0): supplicant 
> interface state: disconnected -> scanning
> Mar 18 22:18:32 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> association took too long.
> Mar 18 22:18:32 lina NetworkManager[532]: <info> (wlan0): device state 
> change: config -> need-auth (reason 'none') [50 60 0]
> Mar 18 22:18:32 lina NetworkManager[532]: <warn> Activation (wlan0/wireless): 
> asking for new secrets
> Mar 18 22:18:32 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> Mar 18 22:18:32 lina NetworkManager[532]: <warn> Couldn't disconnect 
> supplicant interface: This interface is not connected.
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Broadcom 43340

[Arend van Spriel]

On 03/18/15 22:29, Dan Williams wrote:
> On Wed, 2015-03-18 at 21:24 +0000, Jürgen Bausa wrote:
>> Dan Williams<dcbw@...>  writes:
>>
>>>
>>>>
>>>> Thanks, that worked. Now I have firmware and nvram-file and the driver
>> seems
>>>> to load ok. At least I have an interface wlan0.
>>>>
>>>> However, I am not able to connect.Network-manager just says "interface is
>>>> being set up ..." forever. I have no idea howto debug this. In the other
>>>> post you said that the nl80211 driver should be used instead of wext. I
>>>> found that nl80211 is the default for network-manager. So, whats going
>> wrong
>>>> here?
>>>
>>> Could you provide more NetworkManager logs?  They should look like this;
>>> where do your logs stop?
>>>
>>
>>
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) starting
>> connection 'tuxgang'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: disconnected ->  prepare (reason 'none') [30 40 0]
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  NetworkManager state is now
>> CONNECTING
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: prepare ->  config (reason 'none') [40 50 0]
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0/wireless):
>> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: added 'ssid' value
>> 'tuxgang'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: added 'scan_ssid'
>> value '1'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: added 'key_mgmt'
>> value 'WPA-PSK'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: added 'auth_alg'
>> value 'OPEN'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: added 'psk' value
>> '<omitted>'
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  Config: set interface
>> ap_scan to 1
>> Mar 18 22:16:40 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: inactive ->  scanning
>> Mar 18 22:16:50 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: scanning ->  associating
>> Mar 18 22:17:00 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason -3)
>
> Something is still wrong with the driver/device.  Here, even though a
> scan has already been done and the SSID found (otherwise NM wouldn't
> have started a connection in the first place) the supplicant is doing
> another scan (10s) and then attempting to associate, which takes 10s
> before NM kills the attempt.
>
> So ignoring the scan issues (eg, why is another 10s scan requires when
> the SSID is already in the supplicant's network list) it still has
> association problems.
>
> NetworkManager allows up to 20s for an auth/assoc since that really,
> really should be enough.  If it's not enough, then something is
> seriously wrong with the hardware or the wifi network.
>
> Next steps:
>
> What does 'dmesg' say here?  Anything about association tries?
>
> After that we try getting supplicant debug logs and figuring out what's
> going on from its point of view.

Hi Dan,

Thanks for checking the network manager log.

Jurgen,

Do you have brcmfmac driver built with CONFIG_BRCMDBG. If so you can 
enable debug output by:

sudo sh -c 'echo 0xd416 > /sys/module/brcmfmac/parameters/debug'

Regards,
Arend

> Dan
>
>> Mar 18 22:17:00 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: associating ->  disconnected
>> Mar 18 22:17:00 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: disconnected ->  scanning
>> Mar 18 22:17:05 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> association took too long.
>> Mar 18 22:17:05 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: config ->  need-auth (reason 'none') [50 60 0]
>> Mar 18 22:17:05 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> asking for new secrets
>> Mar 18 22:17:05 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:17:05 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:17:29 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
>> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting,
>> secret_name, error)' failed
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: need-auth ->  prepare (reason 'none') [60 40 0]
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: prepare ->  config (reason 'none') [40 50 0]
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0/wireless):
>> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: added 'ssid' value
>> 'tuxgang'
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: added 'scan_ssid'
>> value '1'
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: added 'key_mgmt'
>> value 'WPA-PSK'
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: added 'auth_alg'
>> value 'OPEN'
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: added 'psk' value
>> '<omitted>'
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Mar 18 22:17:29 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  Config: set interface
>> ap_scan to 1
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: scanning ->  associated
>> Mar 18 22:17:29 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason -3)
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: associated ->  disconnected
>> Mar 18 22:17:29 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason 6)
>> Mar 18 22:17:29 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: disconnected ->  scanning
>> Mar 18 22:17:39 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: scanning ->  associating
>> Mar 18 22:17:49 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason -3)
>> Mar 18 22:17:49 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: associating ->  disconnected
>> Mar 18 22:17:49 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: disconnected ->  scanning
>> Mar 18 22:17:54 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> association took too long.
>> Mar 18 22:17:54 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: config ->  need-auth (reason 'none') [50 60 0]
>> Mar 18 22:17:54 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> asking for new secrets
>> Mar 18 22:17:54 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:17:54 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:18:00 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
>> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting,
>> secret_name, error)' failed
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: need-auth ->  prepare (reason 'none') [60 40 0]
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: prepare ->  config (reason 'none') [40 50 0]
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0/wireless):
>> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: added 'ssid' value
>> 'tuxgang'
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: added 'scan_ssid'
>> value '1'
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: added 'key_mgmt'
>> value 'WPA-PSK'
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: added 'auth_alg'
>> value 'OPEN'
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: added 'psk' value
>> '<omitted>'
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Mar 18 22:18:00 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Config: set interface
>> ap_scan to 1
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: scanning ->  4-way handshake
>> Mar 18 22:18:00 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason 6)
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: 4-way handshake ->  disconnected
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  Activation (wlan0/wireless):
>> disconnected during association, asking for new key.
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: config ->  need-auth (reason 'supplicant-disconnect') [50 60 8]
>> Mar 18 22:18:00 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: disconnected ->  inactive
>> Mar 18 22:18:07 lina NetworkManager[532]: (NetworkManager:532): libnm-util-
>> CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting,
>> secret_name, error)' failed
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) scheduled...
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) started...
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: need-auth ->  prepare (reason 'none') [60 40 0]
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) scheduled...
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 1
>> of 5 (Device Prepare) complete.
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) starting...
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: prepare ->  config (reason 'none') [40 50 0]
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0/wireless):
>> connection 'tuxgang' has security, and secrets exist.  No new secrets needed.
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: added 'ssid' value
>> 'tuxgang'
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: added 'scan_ssid'
>> value '1'
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: added 'key_mgmt'
>> value 'WPA-PSK'
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: added 'auth_alg'
>> value 'OPEN'
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: added 'psk' value
>> '<omitted>'
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Activation (wlan0) Stage 2
>> of 5 (Device Configure) complete.
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  Config: set interface
>> ap_scan to 1
>> Mar 18 22:18:07 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: inactive ->  associating
>> Mar 18 22:18:17 lina NetworkManager[532]:<warn>  Connection disconnected
>> (reason -3)
>> Mar 18 22:18:17 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: associating ->  disconnected
>> Mar 18 22:18:17 lina NetworkManager[532]:<info>  (wlan0): supplicant
>> interface state: disconnected ->  scanning
>> Mar 18 22:18:32 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> association took too long.
>> Mar 18 22:18:32 lina NetworkManager[532]:<info>  (wlan0): device state
>> change: config ->  need-auth (reason 'none') [50 60 0]
>> Mar 18 22:18:32 lina NetworkManager[532]:<warn>  Activation (wlan0/wireless):
>> asking for new secrets
>> Mar 18 22:18:32 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>> Mar 18 22:18:32 lina NetworkManager[532]:<warn>  Couldn't disconnect
>> supplicant interface: This interface is not connected.
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Broadcom 43340

[Jürgen Bausa]

Arend van Spriel <arend@...> writes:
> 
> Do you have brcmfmac driver built with CONFIG_BRCMDBG. If so you can 
> enable debug output by:
> 
> sudo sh -c 'echo 0xd416 > /sys/module/brcmfmac/parameters/debug'
> 

No, it doesnt have dbg set. I will try to compile my own kernel and then come 
back.

Juergen

Re: Broadcom 43340

[Arend van Spriel]

On 03/19/15 22:00, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>>
>> Do you have brcmfmac driver built with CONFIG_BRCMDBG. If so you can
>> enable debug output by:
>>
>> sudo sh -c 'echo 0xd416>  /sys/module/brcmfmac/parameters/debug'
>>
>
> No, it doesnt have dbg set. I will try to compile my own kernel and then come
> back.

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

Regards,
Arend

> Juergen
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Broadcom 43340

[Jürgen Bausa]

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

Re: Broadcom 43340

[Arend van Spriel]

On 03/21/15 21:38, Jürgen Bausa wrote:
> 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.

That MAC address is only used for device that do have mac address in the 
device so you can ignore that one.

> 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!

Ah, I was wondering what type of sdio host controller was used. When 
sdio host controller uses runtime-pm it affect communication with wlan 
device. I recently posted a patch for that [1].

> 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.

Might be the driver is already loaded before root file system is loaded 
(from initramfs).

> 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.

Is that after reboot or really after powerup. Curious whether there is a 
difference between the two regarding this issue.

Regards,
Arend

[1] https://patchwork.kernel.org/patch/6038511/

> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Broadcom 43340

[Jürgen Bausa]

QXJlbmQgdmFuIFNwcmllbCA8YXJlbmRALi4uPiB3cml0ZXM6Cgo+IAo+IE9uIDAzLzIxLzE1IDIxOjM4LCBKw7xyZ2VuIEJhdXNhIHdyb3RlOgo+ID4gMS4gdGhlIG52cmFtIGZpbGUgdW5kZXIgL3N5cy9maXJtd2FyZS9lZmkvZWZpdmFycy8gaGFzIGEgd3JvbmcgTUFDIGFkZHJlc3MuCj4gPiBJIGNoYW5nZWQgaXQgdG8gdGhlIGNvcnJlY3Qgb25lLiBIb3dldmVyLCBJIGFtIG5vdCBzdXJlIGlmIHRoaXMgaXMgcmVhbGx5Cj4gPiBuZWNhc3NhcnkuCj4gCj4gVGhhdCBNQUMgYWRkcmVzcyBpcyBvbmx5IHVzZWQgZm9yIGRldmljZSB0aGF0IGRvIGhhdmUgbWFjIGFkZHJlc3MgaW4gdGhlIAo+IGRldmljZSBzbyB5b3UgY2FuIGlnbm9yZSB0aGF0IG9uZS4KCllvdSBhcmUgcmlnaHQsIGZvdW5kIGl0IG91dCBtYXlzZWxmIGluIHRoZSBtZWFudGltZS4gVGhlcmUgaXMgbm8gbmVlZCB0bwpjaGFuZ2UgdGhlIE1BQyBhZGRyZXNzLgoKPiAKPiA+IDIuIEZvdW5kIHRoZSBmb2xsb3dpbmcgb24gdGhlIHdlYjoKPiA+Cj4gPj4gcm1tb2QgYnJjbWZtYWMKPiA+PiBybW1vZCBicmNtdXRpbAo+ID4+IGVjaG8gb24+ICAvc3lzL2J1cy9wbGF0Zm9ybS9kcml2ZXJzL3NkaGNpLWFjcGkvSU5UMzNCQlw6MDAvcG93ZXIvY29udHJvbAo+ID4+IG1vZHByb2JlIGJyY21mbWFjCj4gPgo+ID4gQWZ0ZXIgdGhpcywgSSBjYW4gY29ubmVjdCB0byB3bGFuIQo+IAo+IEFoLCBJIHdhcyB3b25kZXJpbmcgd2hhdCB0eXBlIG9mIHNkaW8gaG9zdCBjb250cm9sbGVyIHdhcyB1c2VkLiBXaGVuIAo+IHNkaW8gaG9zdCBjb250cm9sbGVyIHVzZXMgcnVudGltZS1wbSBpdCBhZmZlY3QgY29tbXVuaWNhdGlvbiB3aXRoIHdsYW4gCj4gZGV2aWNlLiBJIHJlY2VudGx5IHBvc3RlZCBhIHBhdGNoIGZvciB0aGF0IFsxXS4KClNvLCBkbyBJIHVuZGVyc3RhbmQgY29ycmVjdGx5LCB0aGF0IHdpdGggeW91ciBwYXRjaCB0aGUgYWJvdmUgd29ya2Fyb3VuZAp3aWxsIG5vIGxvbmdlciBiZSBuZWVkZWQ/IEluIHdoaWNoIGtlcm5lbCB3aWxsIHlvdXIgcGF0Y2ggYmUgaW5jbHVkZWQ/IEFzCndpZmkgaXMgd29ya2luZyBub3csIEkgd291bGQgYXZvaWQgaW5zdGFsbGluZyB0aGUgcGF0Y2ggYW5kIGluc3RlYWQgd2FpdCBmb3IKdGhlIG5leHQga2VybmVsLgoKPiAKPiA+IERvZXMgdGhpcyBnaXZlIHlvdSBlbm91Z2ggaW5mb3JtYXRpb24gdG8gZmluZCBvdXQsIHdoYXQgdGhlIHByb2JsZW0gaXM/IE9yCj4gPiBkbyB5b3Ugc3RpbGwgbmVlZCBEQkcgb3V0cHV0IGZyb20gdGhlIGRyaXZlcj8gaWYgc28sIGp1c3QgdGVsbCBtZSBhbmQgSSB3aWxsCj4gPiB0cnkgdG8gY29tcGlsZSBhbmQgaW5zdGFsbCB0aGUga2VybmVsIHdpdGggREJHIHR1cm5kZWQgb24uIEl0cyBub3QgYSBiaWcKPiA+IGRlYWwgYnV0IEkgc3RvcHBlZCB3b3JraW5nIG9uIGl0IGFzIEkgZm91bmQgdGhpcyB3b3JrYXJvdW5kLgo+ID4KPiA+IEF0IHRoZSBtb21tZW50IEkgYW0gdHJ5aW5nIHRvIHB1dCB0aGVzZSBjb21tYW5kcyB0byByYyxsb2NhbC4gV2l0aCBsaW1pdGVkCj4gPiBzdWNjZXNzIHVudGlsIG5vdywgQnV0IHRoaXMgbWF5IGJlIGNhdXNlZCBieSB0aGUgZmFjdCwgdGhhdCB0aGV5IGFyZQo+ID4gZXhlY3V0ZWQgdG9vIGVhcmx5LiBXaWxsIGFkZCBzb21lIHNsZWVwLgo+IAo+IE1pZ2h0IGJlIHRoZSBkcml2ZXIgaXMgYWxyZWFkeSBsb2FkZWQgYmVmb3JlIHJvb3QgZmlsZSBzeXN0ZW0gaXMgbG9hZGVkIAo+IChmcm9tIGluaXRyYW1mcykuCgpJIG5vdyBnb3QgaXQgd29ya2luZy4gSnVzdCBwdXQgJ3NsZWVlcCAyMCcgYmVmb3JlIHRoZSBjb21tYW5kcyBhbmQgbm93IGl0CndvcmtzIHBlcmZlY3RseS4KCj4gCj4gPiBBbm90aGVyIHRoaW5nIEkgZm91bmQgb3V0IGlzLCB0aGF0IHRoZSBzeXN0ZW0gc29tZXRpbWVzIGNvbWVzIHVwIHdpdGhvdXQKPiA+IHdsYW4wLiBJdCBzZWVtcyBJIGhhdmUgaXQgb25seSBvbiBldmVyeSBzZWNvbmQgYm9vdC4gSG93ZXZlciwgdGhpcyBjb3VsZCBiZQo+ID4ganVzdCBieSBpbmNpZGVudCBhbmQgaXQgaXMgbm90IGV4YWN0bHkgZXZlcnkgc2Vjb25kIGJvb3QgYnV0IGFib3V0IDUwICUgb2YKPiA+IGFsbCBib290cy4KPiAKPiBJcyB0aGF0IGFmdGVyIHJlYm9vdCBvciByZWFsbHkgYWZ0ZXIgcG93ZXJ1cC4gQ3VyaW91cyB3aGV0aGVyIHRoZXJlIGlzIGEgCj4gZGlmZmVyZW5jZSBiZXR3ZWVuIHRoZSB0d28gcmVnYXJkaW5nIHRoaXMgaXNzdWUuCj4gCgpJdCB3YXMgYWZ0ZXIgcmVib290IGFuZCBhdCBjb2xkIGJvb3QuCgpIb3dldmVyLCB0aGlzIHByb2JsZW0gc2VlbXMgdG8gYmUgZ29uZS4gd2xhbjAgaXMgdXAgb24gZXZlcnkgYm9vdC4gSW4gdGhlCm1lYW50aW1lIGkgdXBncmFkZWQgdG8gcmM0LiBDb3VsZCB0aGlzIGJlIHRoZSByZWFzb24/CgpEbyB5b3Ugc3RpbGwgbmVlZCBzb21lIGRiZyBpbmZvcm1hdGlvbiBmcm9tIG15IG1hY2hpbmU/IElmIHNvLCBqdXN0IHRlbGwgbWUKYW5kIEkgd2lsbCBpbnN0YWxsIGEga2VybmVsIHdpdGggdGhlIG5lZWRlZCBvcHRpb25zLiBPdGhlcndpc2UsIEkgd2lsbCBzdGF5CndpdGggdGhlIGN1cnJlbnQgc2l0dWF0aW9uLgoKCj4+IE9rLCB0aGFua3MuIFdpbGwgdGhlIGRyaXZlciBhbHNvIGVuYWJsZSBibHVldG9vdGg/IEFzIEkgcmVhZCwgdGhlCj4+IGJjbTQzMzQxIGFsc28gaGFzIEJsdWV0b290aCBjYXBhYmlsaXRpZXMuCj4KPkl0IGhhcywgYnV0IG5vIGNsdWUgd2hhdCBob3N0IGludGVyZmFjZSBpcyB1c2VkLiBBbnl3YXksIGl0IHdpbGwgaGF2ZSAKPmEgc2VwYXJhdGUgZHJpdmVyLgoKRG8geW91IG5vdywgaWYgdGhlcmUgaXMgc29tZSBkZXZlbG9wbWVudCBnb2luZyBvbiBmb3IgdGhlIGJsdWV0b290aCBkcml2ZXI/CldobyBjb3VsZCBJIGNvbmFjdD8KCkp1ZXJnZW4KCg==

Re: Broadcom 43340

[Arend van Spriel]

On 03/22/15 21:14, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>
>>
>> On 03/21/15 21:38, Jürgen Bausa wrote:
>>> 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.
>>
>> That MAC address is only used for device that do have mac address in the
>> device so you can ignore that one.
>
> You are right, found it out mayself in the meantime. There is no need to
> change the MAC address.
>
>>
>>> 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!
>>
>> Ah, I was wondering what type of sdio host controller was used. When
>> sdio host controller uses runtime-pm it affect communication with wlan
>> device. I recently posted a patch for that [1].
>
> So, do I understand correctly, that with your patch the above workaround
> will no longer be needed? In which kernel will your patch be included? As
> wifi is working now, I would avoid installing the patch and instead wait for
> the next kernel.

Indeed. The patch basically does the same thing as the workaround. It is 
applied to wireless-drivers-next tree so it will be in 4.1 kernel. So it 
will take a while before that gets released by Linus. 4.1-rc1 will 
probably take approx. 6-7 wks.

>>
>>> 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.
>>
>> Might be the driver is already loaded before root file system is loaded
>> (from initramfs).
>
> I now got it working. Just put 'sleeep 20' before the commands and now it
> works perfectly.

Holding the boot for 20s is steep, but I guess a working device trumps a 
fast boot ;-)

>>
>>> 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.
>>
>> Is that after reboot or really after powerup. Curious whether there is a
>> difference between the two regarding this issue.
>>
>
> It was after reboot and at cold boot.
>
> However, this problem seems to be gone. wlan0 is up on every boot. In the
> meantime i upgraded to rc4. Could this be the reason?

Nothing in brcmfmac is changed that would explain this. Maybe something 
was fixed in sdio host controller, but it is all speculation.

> Do you still need some dbg information from my machine? If so, just tell me
> and I will install a kernel with the needed options. Otherwise, I will stay
> with the current situation.

If you are happy and the issue seems resolved there is no need. Thanks.

>>> Ok, thanks. Will the driver also enable bluetooth? As I read, the
>>> bcm43341 also has Bluetooth capabilities.
>>
>> It has, but no clue what host interface is used. Anyway, it will have
>> a separate driver.
>
> Do you now, if there is some development going on for the bluetooth driver?
> Who could I conact?

I am not sure what host-interface is used to bt part. Is it usb or uart? 
I know there are plans to mainline the bt uart driver, but not sure when 
that will make its way into the kernel. If it is usb you should be able 
to use btusb driver, but you need firmware. They added support for 
handling firmware in btusb recently.

Regards,
Arend

Re: Broadcom 43340

[Jürgen Bausa]

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

> > I now got it working. Just put 'sleeep 20' before the commands and now it
> > works perfectly.
> 
> Holding the boot for 20s is steep, but I guess a working device trumps a 
> fast boot 
> 

Systemd runs even rc.local in parallel. So it doesn't hold the boot process.

Juergen

Re: Broadcom 43340

[Arend van Spriel]

On 03/23/15 21:09, Jürgen Bausa wrote:
> Arend van Spriel<arend@...>  writes:
>
>>> I now got it working. Just put 'sleeep 20' before the commands and now it
>>> works perfectly.
>>
>> Holding the boot for 20s is steep, but I guess a working device trumps a
>> fast boot
>>
>
> Systemd runs even rc.local in parallel. So it doesn't hold the boot process.

You make me feel old ;-)

Regards,
Arend

Re: Broadcom 43340

[Stefan Lippers-Hollmann]

Hi

On 2015-03-15, Jürgen Bausa wrote:
> Arend van Spriel <arend@...> writes:
> > On 03/14/15 23:13, Ochal Christophe wrote:
[...]
> would be nice, if you could make it clear.
> 
> I am in the exact some position (asus x205 with linux 4.0 rc3) but my
> /sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
> kernel taken from ubuntu. Am I missing something? Even loading efivars via
> modprobe doesnt change a thing.

You need to have efivarfs mounted, which Debian/jessie and systemd 
should do by default (it certainly does, at least when booted in UEFI
mode - you probably won't have access to it in BIOS CSM mode):

$ grep efivarfs /proc/mounts 
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0

If it isn't for some weird reason, you'll have to mount it by hand.

# mount -t efivarfs -o rw,nosuid,nodev,noexec,relatime efivarfs /sys/firmware/efi/efivars

Regards
	Stefan Lippers-Hollmann

Re: Broadcom 43340

[Koen Bulcke]

Hi,

Finally I got some progress thanks to your comment, 
I can now see the Wifi
networks on my Asus X205TA (kernel 4.0RC3). 
However, connecting to any
network seems still to be an issue:

vempc:~$ sudo wpa_supplicant -Dwext -iwlan0 -cwpa.conf
[sudo] password 
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
wlan0: Trying to associate with a1:b1:e9:da:fd:75 
(SSID='WiFiD85' freq=2472 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with a1:b1:e9:da:fd:75 timed out.
wlan0: CTRL-EVENT-DISCONNECTED 
bssid=a1:b1:e9:da:fd:75 reason=3
locally_generated=1
ioctl[SIOCSIWSCAN]: Invalid exchange


Thanks,
Koen.

Re: Broadcom 43340

[Arend van Spriel]

On 03/15/15 03:03, Koen Bulcke wrote:
> Hi,
>
> Finally I got some progress thanks to your comment,
> I can now see the Wifi
> networks on my Asus X205TA (kernel 4.0RC3).
> However, connecting to any
> network seems still to be an issue:
>
> vempc:~$ sudo wpa_supplicant -Dwext -iwlan0 -cwpa.conf

Forget about wext and try nl80211 driver so:

$ sudo wpa_supplicant -Dnl80211 -iwlan0 -cwpa.conf

Regards,
Arend