RPi3 WiFi issues with onboard chip

business_kid · 02-09-2017, 04:18 AM

Right, your wlan0 seems to be sitting there but not joining the network. The driver etc looks ok so far. You're down to wpa_supplicant, protocols, & dhcp.
1. Os the psk in wpa_supplicant.conf passed through wpa_passpgrase? You get an output to paste into wpa_supplicant.conf

Code:

bash-4.3$ wpa_passphrase My_ESSID My_Password
network={
	ssid="My_ESSID"
	#psk="My_Password"
	psk=116c4b8b7dc9419a4f2a7e12c80e721ccd7650942b17781f79e38fc9632e04fc
}

Try invoking wpa_supplicant by hand. Kill any wpa_supplicant & dhcpcd or dhclient processes, and of course stop networkmanager, which I find to be NetworkMismanager. Then run

Code:

wpa_supplicant -c/path/to/wpa_supplicant.conf -i wlan0 -Dwext >> some.log && dhcpcd wlan0 >>some.log

You can of course just use dhclient instead of dhcpcd if that's installed. some.log might be interesting. It stops errors going to /dev/null anyhow.

slackist · 02-09-2017, 10:01 AM

Quote:

1. Os the psk in wpa_supplicant.conf passed through wpa_passpgrase? You get an output to paste into wpa_supplicant.conf

Yes, I snipped the full psk out just in case my neighbours grow a brain but it was generated by wpa_passphrase.

Quote:

Try invoking wpa_supplicant by hand. Kill any wpa_supplicant & dhcpcd or dhclient processes, and of course stop networkmanager, which I find to be NetworkMismanager. Then run

NetworkMismanager is not installed as I also find it to be a PITA, I did run the command you posted. As usual dhcpd overwrote my resolv.conf with useless cruft.

Code:

[root@darkmoon:log] # wpa_supplicant -c/etc/wpa_supplicant.conf -i wlan0 -Dwext >> /var/log/bk.log && dhcpcd wlan0 >> /var/log/bk.log

I was running a tail -f on the syslog:

Code:

Feb  9 22:22:05 darkmoon kernel: [95066.510646] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:05 darkmoon kernel: [95066.510668] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
Feb  9 22:22:17 darkmoon kernel: [95078.184872] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:17 darkmoon kernel: [95078.184895] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
Feb  9 22:22:29 darkmoon kernel: [95089.857325] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:29 darkmoon kernel: [95089.857348] brcmfmac: brcmf_cfg80211_scan: scan error (-11)

And /var/log/messages:

Code:

Feb  9 22:22:05 darkmoon kernel: [95066.279479] brcmfmac: power management disabled
Feb  9 22:22:05 darkmoon kernel: [95066.279977] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  9 22:24:31 darkmoon dhcpcd[23270]: wlan0: adding address fe80::9f6d:a6c9:2c45:3095
Feb  9 22:24:31 darkmoon dhcpcd[23270]: wlan0: waiting for carrier
Feb  9 22:24:31 darkmoon kernel: [95212.014419] brcmfmac: power management disabled
Feb  9 22:24:31 darkmoon kernel: [95212.017674] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  9 22:25:01 darkmoon dhcpcd[23270]: dhcpcd exited

And the log file generated:

Code:

[root@darkmoon:log] #cat /var/log/bk.log
Successfully initialized wpa_supplicant
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=1 duration=10 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=2 duration=23 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=3 duration=46 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=4 duration=77 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-TERMINATING 
wlan0: adding address fe80::9f6d:a6c9:2c45:3095
wlan0: waiting for carrier
dhcpcd exited

business_kid · 02-09-2017, 01:44 PM

On that output, the software looks ok, and you have driver or firmware trouble. One thing to try is that there's another -D option for wpa_supplicant, e.g. nl802.11. That's easy.

The messier bit is getting a driver & firmware your system agrees with, especially as you're Arm based & not x86. I think there's a big endian/little endian thing going on between those 2.

If that doesn't sort it, and you get drivers that work for others & not you, we might end up calling the hardware dud. Ebay has usb wifi modules that plug into usb & provide wifi. I think you need the usbnet kernel module. I got one for the RasPi 1 I had, and it worked like a dream.

justwantin · 02-09-2017, 03:40 PM

@ slackist,
Sorry, been busy, I note that your system sets up wlan0 and that you have setup your essid, After that have you run ifconfig wlan0 up and then iwlist wlan0 scan? If you did and get a list of networks including your own then may I suggest that you forget about wpa supplicant et.al. and try using wicd. Wicd does not require you to have wpa supplicant configured, nor does network manager for that matter, but I find wicd easier to use. Just be sure that you have removed any entries you may have made in /etc/rc.d/rc.inet1.conf or wicd will not work. I never bothered with wpa supplicant so I'm not sure what you should do with that but probably it too would need any configs to be removed.

slackist · 02-09-2017, 07:47 PM

Quote:

Originally Posted by business_kid

On that output, the software looks ok, and you have driver or firmware trouble. One thing to try is that there's another -D option for wpa_supplicant, e.g. nl802.11. That's easy.

The messier bit is getting a driver & firmware your system agrees with, especially as you're Arm based & not x86. I think there's a big endian/little endian thing going on between those 2.

If that doesn't sort it, and you get drivers that work for others & not you, we might end up calling the hardware dud. Ebay has usb wifi modules that plug into usb & provide wifi. I think you need the usbnet kernel module. I got one for the RasPi 1 I had, and it worked like a dream.

I've tried the -Dnl80211 switch (the output is in the last bit of post #15) and as mentioned upthread I have an old WiFi dongle that works fine (when it's plugged in or removed the system loads and unloads a driver as reported by lsmod and /var/log/messages and wpa_supplicant works with it as wlan1) but it's so big that it effectively takes up 2 of the 4 USB ports, I know I could stick it into a USB hub but I've already got cables all over my desk plus it is slow being so old, hence the efforts to get the onboard WiFi working!

Quote:

Originally Posted by justwantin

@ slackist,
Sorry, been busy, I note that your system sets up wlan0 and that you have setup your essid, After that have you run ifconfig wlan0 up and then iwlist wlan0 scan? If you did and get a list of networks including your own then may I suggest that you forget about wpa supplicant et.al. and try using wicd. Wicd does not require you to have wpa supplicant configured, nor does network manager for that matter, but I find wicd easier to use. Just be sure that you have removed any entries you may have made in /etc/rc.d/rc.inet1.conf or wicd will not work. I never bothered with wpa supplicant so I'm not sure what you should do with that but probably it too would need any configs to be removed.

I’ve tried wicd via wicd-curses and the Xfce4 panel applet several times with all the rc.inet1.conf references commented out and wpa_supplicant.conf renamed but it rolls around trying to connect and then gives up with a 'not connected' message to my AP.

justwantin · 02-09-2017, 08:54 PM

This may be a wicd configuration problem.

That happened to me on an install to a bananapro. I had first gotten the pro up and running with a wired connection to my lan. When I then tried to configure to wireless with configs known to be correct it just rolled around. It turned out that wireless was turned off in wicd. I was able to connect once I turned it on. I was in an x session via ssh when I did it and don't remember exactly how now. Here's a link that might give you some ideas http://www.linuxquestions.org/questi...ff-4175475544/ I remember at the time I found some other references to this problem and solution so have a look.

SCerovec · 02-10-2017, 02:02 AM

May I chime in some?
tcpdump can rely some of the 802 frame headers
Also aircrack-ng might help a bit
If not, alone the RTFMing of the respective chapters of said apps might shed a light of the culprits?

IIRC the problem is the immature driver/firmware of the wifi MAC, so reading the module source might help even

But before anything:
/sbin/modinfo <module of ours>
Would yield a clue?

yustin · 02-13-2017, 05:39 AM

maybe this solves your problem ....

https://debianforum.de/forum/viewtop...142749#p935640

# /etc/modprobe.d/regdomain.conf
options cfg80211 ieee80211_regdom=[your_country_code]

have phun

business_kid · 02-13-2017, 02:13 PM

I'm not confident that will sort it as his wifi is puking on normal setup instructions. At the risk of repeating myself from post #20

Quote:

On that output, the software looks ok, and you have driver or firmware trouble.

SCerovec · 02-14-2017, 04:38 AM

Reminds me of the days of ACX100 and how it got from a patch to mainline

My bet: kernel side (=not ready yet).

Remedy: try upgrade kernel until it works?

adamsimms · 11-21-2017, 01:40 PM

I believe I'm having a very similar issue. My Raspberry Pi was connecting to a WiFi network for months without issue. About a week ago it suddenly stopped and will not associate with the AP.

`iwlist wlan0 scan` shows the network is available:

Code:

Cell 02 - Address: D6:D9:19:9A:00:5A
                  Channel:1
                  Frequency:2.412 GHz (Channel 1)
                   Quality=56/70  Signal level=-54 dBm  
                   Encryption key:on
                   ESSID:"DiscoPro"
                   Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                             11 Mb/s; 12 Mb/s; 18 Mb/s
                   Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                   Mode:Master
                   Extra:tsf=0000000000000000
                   Extra: Last beacon: 10650ms ago
                   IE: Unknown: 0008446973636F50726F
                   IE: Unknown: 010882848B0C12961824
                   IE: Unknown: 030101
                   IE: Unknown: 050400010000
                   IE: Unknown: 0706555320010B1E
                   IE: Unknown: 2A0100
                   IE: Unknown: 32043048606C
                   IE: Unknown: 2D1A2C0101FF00000000000000000000000000000000000000000000
                   IE: Unknown: 3D1601000000000000000000000000000000000000000000
                   IE: IEEE 802.11i/WPA2 Version 1
                       Group Cipher : CCMP
                       Pairwise Ciphers (1) : CCMP
                       Authentication Suites (1) : PSK
                   IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00

/etc/network/interfaces contents:

Code:

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
wireless-power off

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf contents:

Code:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
        ssid="DiscoPro"
        psk="XXXX"
}

When I run `wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf` I receive this error:

Code:

Successfully initialized wpa_supplicant
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="DiscoPro" auth_failures=1 duration=10 reason=CONN_FAILED

Any suggestions would be appreciated.

business_kid · 11-22-2017, 05:10 AM

If the config hasn't changed since the problems began, I would leave them. They look believeable.

What else happened around the same time as the problems? Kernel update? Software update? That's where to look. You also can specify more authentication methods than just ccmp. I believe one of them is going out (don't remember which), but you can hedge your bets there.

If that fails, I would start reinstalling packages, and finally suspect hardware.

adamsimms · 11-22-2017, 08:10 AM

Thanks, @business_kid.

It could have been a software and/or kernel update. I try to keep the PI updated.

What packages do you suggest that I reinstall?

Can you point me to where I could learn about other authentication methods other than ccmp?

business_kid · 11-22-2017, 12:35 PM

I would first disable WPA altogether and see if you can connect with dhcpcd. If you succeed, that clears the rest of it. Reinstall WPA supplicant

Man wpa_supplicant.conf provides info.

uwedamm · 11-22-2017, 02:46 PM

Hello together,
maybe offtopic, but just a really stupid idea, which should be checked: Move the Raspberry more near to the Router

Rationale:
Some years in the past I got an issue with RPI2 and USB-WLANstick, I dont remember much details, but after hours of trying to connect and finding out the issue I fixed it as follows:

Setup was:
RPI2, WLAN accesspoint configured
S2-smartphone tries to connect

Network (SSID of the RPI) showed up on the smartphone, all seemed fine, but from my seat (3m away from the router) I got always "Authentication failed".
Once moving the Smartphone near to the Raspberry all worked fine ...:-)

just an idea, ignore if it does not help

Good job, thank you really much for your deep analysis above! It gave me some more hints how to analyze issues with the WLAN!

best regards
Uwe
PS: I currently have got the same issue like above, in a few days I will move the RPI setup to the 1st floor, where the router resides ... maybe it helps for me :-)