Raspberry Pi 3 can not detect my wifi

[Zosima]

I just bought a new raspberry pi 3 and installed Raspbian on it. Now I want to connect to my wifi but it can not detect it. It can however detect many wifi ap's from my neighbours etc. Using my laptop I can see that my wifi has the strongest signal.

Does anyone know what the problem could be?

Thanks in advance!

[DirkS]

Does your AP use channel 12 or 13?
First of all run

Code: Select all

sudo apt-get update
sudo apt-get upgrade

Also set the correct wifi country using

Code: Select all

sudo raspi-config

(or use the GUI configuration utility)

[blacai]

Same problem here.
I connected through ethernet so I could update the system.

After that now it is even worse.
The default gw is not being recognized for eth0 and the wlan0 continues without finding my SSID.

Wifi is set to my country.
Wifi is set to channel 7
Wifi 5Ghz is set to channel 40

Any idea?

Edit:
I reinstalled the complete system with the noobs 1.9.
Wifi is being recognized whenever it isn't running on the channels 12/13

[WolfG]

Same problem here;
I changed from channel 'auto' to '9' and my wifi is visible.
Perhaps we need a new driver.
And yes, I've updated the system, change the wifi country etc.etc.

[DougieLawson]

Wifi is being recognized whenever it isn't running on the channels 12/13

Have you used sudo raspi-config to set your WiFi country code?

[blacai]

Wifi is being recognized whenever it isn't running on the channels 12/13

Have you used sudo raspi-config to set your WiFi country code?

Yes, I switched the country code to DE - Germany.
If I check the wpa config it shows the correct one.

Running

Code: Select all

iw list

only from channels 1-11 appears.

[DougieLawson]

Is it definitely set to Germany (DE)? Try the iw get reg command

Code: Select all

pi@challenger:~$ iw reg get
country GB: DFS-ETSI
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A)
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
        (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
        (57000 - 66000 @ 2160), (N/A, 40), (N/A)
pi@challenger:~$

Code: Select all

                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)
                        * 2472 MHz [13] (20.0 dBm)
                        * 2484 MHz [14] (disabled)

That shows up as a country code in /etc/wpa_supplicant/wpa_supplicant.conf

Code: Select all

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

network={
        ssid="redactedSSID"
        psk="redactedPSK"
        key_mgmt=WPA-PSK
}

you could cheat and set your RPi3B to "country=GB" and nobody will know any different.

[blacai]

Ok, thanks for the help.
I tried again and also with country code set to GB but no results

Code: Select all

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
pi@raspberrypi:~ $ 

DE

Code: Select all

pi@raspberrypi:~ $ iw reg get
country DE: DFS-ETSI
	(2400 - 2483 @ 40), (N/A, 20), (N/A)
	(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
	(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
	(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)
pi@raspberrypi:~ $ 

Code: Select all

pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf 
country=DE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
pi@raspberrypi:~ $ 

Code: Select all

pi@raspberrypi:~ $ 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.
	Device supports T-DLS.
	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: 0x1020
			HT20
			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)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * join_ibss
		 * set_pmksa
		 * del_pmksa
		 * flush_pmksa
		 * remain_on_channel
		 * frame
		 * set_channel
		 * tdls_oper
		 * 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, AP } <= 2, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
		   total <= 3, #channels <= 2
	Device supports scan flush.
pi@raspberrypi:~ $ 

GB

Code: Select all

pi@raspberrypi:~ $ iw reg get
country GB: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20), (N/A)
	(5170 - 5250 @ 80), (N/A, 20), (N/A)
	(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
	(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)
pi@raspberrypi:~ $ 

Code: Select all

pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf 
country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
pi@raspberrypi:~ $ 

Code: Select all

pi@raspberrypi:~ $ 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.
	Device supports T-DLS.
	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: 0x1020
			HT20
			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)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * join_ibss
		 * set_pmksa
		 * del_pmksa
		 * flush_pmksa
		 * remain_on_channel
		 * frame
		 * set_channel
		 * tdls_oper
		 * 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, AP } <= 2, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
		   total <= 3, #channels <= 2
	Device supports scan flush.
pi@raspberrypi:~ $ 

Kind of weird...

[DougieLawson]

Have you got the right broadcom firmware package installed?

dmesg shows

Code: Select all

[    7.496230] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c

on my RPi3B

[blacai]

Have you got the right broadcom firmware package installed?

dmesg shows

Code: Select all

[    7.496230] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c

on my RPi3B

Code: Select all

[    6.809877] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24
[    6.811189] usbcore: registered new interface driver brcmfmac
[    6.985431] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[    7.017336] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[    7.311146] bcm2835-rng 3f104000.rng: hwrng registered
[    7.615141] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[    7.615156] cfg80211: World regulatory domain updated:
[    7.615164] cfg80211:  DFS Master region: unset
[    7.615165] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    7.615180] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    7.615187] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    7.615193] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    7.615202] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    7.615211] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    7.615218] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    7.615225] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    7.615232] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    7.702449] systemd-journald[106]: Received request to flush runtime journal from PID 1
[    8.040399] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[    8.040433] brcmfmac: brcmf_add_if: ignore IF event
[    8.045761] brcmfmac: power management disabled

I uploaded the fulll output
http://pastebin.com/vP6uJs4q

Is this correct?

[DougieLawson]

OK. I'm stuck. I've no idea why your RPi3B won't play nicely with your AP.

It's probably time to report it on https://github.com/raspberrypi/firmware and see what the nice folks at the RPF make of your problem.

[blacai]

OK. I'm stuck. I've no idea why your RPi3B won't play nicely with your AP.

It's probably time to report it on https://github.com/raspberrypi/firmware and see what the nice folks at the RPF make of your problem.

thanks for your time and advice.
I checked again from the beginning and using the hash for the firmware 4.4.3 version did the trick.

Code: Select all

sudo rpi-update 41f8b4812ad653abf321b8c54cb4bee57ebdb129

This one brings the pi up to the version 4.4.3 v7+ which seems ok

Code: Select all

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.4.3-v7+ #849 SMP Mon Feb 29 15:13:28 GMT 2016 armv7l GNU/Linux

Code: Select all

		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)
			* 2472 MHz [13] (20.0 dBm)
			* 2484 MHz [14] (disabled)

Before I had the 4.1.18 and this morning I upgraded to the 4.1.20

Now my question is if the actual master branch of the firmware is still running on this problem.

Which version of the firmware do you run?

[DougieLawson]

I'm one of those crazies who knows what rpi-update does, knows how to recover if it fails to boot and understands the kernel & firmware. I also know how to report kernel / firmware bugs. So eight out of ten of my raspberries are running 4.4.6+ (or 4.4.6-v7+) #861 which is the BRANCH=next rpi-update version.

One of the odd ones is running the Wolfson sound card kernel. The other odd one is running an ancient version of NOOBS.

I'd still recommend posting your thoughts on Github to get this one looked at by the RPF folks.

[blacai]

You are right.
I downgraded to the latest master firmware and opened an issue in the github.
They suggested to open it in the kernel project.

Thanks again for your effort. At least it is clear what is the problem and how to resolve it.
So far it is not critical in my case, I can change the running channel of my WIFI.

[ismailA]

Hey there,

I am newbie too. Just bought a Pi3 and unable to connect it to the Airport Extreme wireless network as described above.

After reading comments in this post, changed my wifi channel from 12 to 3 and voila! It worked.

Thanks!