RPI 3 B+ No wireless interfaces found

[slajerek]

Hi!

When I boot to desktop I see error that "No wireless interfaces found" on a RPI 3 B+, and of course there's no network connection.
The same SD card works flawlessly when inserted to older RPI 3 B (without plus). What's wrong? How to fix this problem?

I tried rpi-update, upgrade, dist-upgrade. No luck... any ideas how to fix this problem?

Thanks in advance.

Regards,
Marcin

[pcmanbob]

Hi.

You need to run

Code: Select all

sudo raspi-config

then select localisation options
then change wifi country.

you may also need to unblock the wifi using this command

Code: Select all

sudo rfkill unbolck all

you can also see if the wifi and Bluetooth are blocked by running

Code: Select all

sudo rfkill list all

[slajerek]

Thank you for quick answer. I did this already.

The output of

Code: Select all

sudo rfkill list all

tells me

Code: Select all

0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

There's no information about wifi. If I run iwconfig I also do not see any wlan0 interfaces, telling me only that lo and eth0 have

Code: Select all

lo		no wireless extensions.
eth0 		no wireless extensions.

Am I missing something? The same SD card when I put to old Raspberry Pi 3 B v1.2 (not B+) works perfectly fine and wifi is started.

I think it is worth noting that the system is via NOOBs and it was upgraded from older version to the B+.

[HawaiianPi]

What OS? If it's Raspbian Jessie you should start over with the latest version of Raspbian Stretch 2018-04-18 or newer. Jessie predates the 3B+ and is not compatible (loading the possibly unstable testing firmware with rpi-update will get Jessie booting, but won't fix other problems).

[msp]

In case it helps someone else, adding this into network interface config was the fix for me (after much time spent). NB: whilst the WIFI is connected, the desktop UI still shows "No interfaces found".

Code: Select all

pi@msp-raspberrypi:~ $ sudo cat /etc/network/interfaces
# 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

# MSP HACK
allow-hotplug wlan0
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

I'd already upgrade the OS & configured my interface etc:

Code: Select all

pi@msp-raspberrypi:~ $ uname -a
Linux msp-raspberrypi 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
pi@msp-raspberrypi:~ $ sudo cat /etc/os-release 
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Code: Select all

pi@msp-raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf 
country=GB
network={
  ssid="XXXX"
  psk="XXXX"
  key_mgmt=WPA-PSK
}

[swastik]

Try this it worked for me
dtoverlay=pi3-enable-wifi

[sigithaq]

Try this it worked for me
dtoverlay=pi3-enable-wifi

so, what should i write in there ?

[ENCOMCTO]

I'm having the same problem on a RPI 3B and on a Zero W. If I try using raspi-config it's saying it can't communicate with WPA_Supplicant. This is on a clean download using Etcher.

[hajo]

I'm having the same problem on a RPI 3B and on a Zero W. If I try using raspi-config it's saying it can't communicate with WPA_Supplicant. This is on a clean download using Etcher.

Same here. After doing a system upgrade recently I lost all network connectivity - wireless and wired. journalctrl shows that the udev worker for all network interfaces fails with a segfault. I suspect a broken FW or driver, I think both got updated. Trying a rollback now but that's not so easy since I have no network left...

[hajo]

Hours later I gave up; rolling back with an apt which is not online is too much trouble. . My pi is almost stock anyway, so I did a fresh install of the latest distro. Problem solved, both interfaces are back up again. Unfortunately this is not the first time that apt-get upgrade bricked my distro. Fedora-user here — is this known of debian?

[Rasilon]

Last update also blew my wifi and bluetooth. I duno what to do

[HawaiianPi]

Last update also blew my wifi and bluetooth. I duno what to do

Really odd that you (and others) are having this problem. I'm SSH connected to both a Pi 3B and a 3B+ that have been recently updated (last night), and both are connected to my wireless network. The Pi 3B is USB booted from an SSD running Raspbian Stretch Lite. The Pi 3B+ is booting from a SanDisk Ultra A1 micro SD card (32GB) running Raspbian Stretch Desktop. The uname -r command on either system returns 4.14.70-v7+ for the kernel version.

The Pi 3B+ has been running for awhile now, and has been through several update/upgrade cycles, with the only problem being the shutdown kernel panic due to the recent (and buggy) 20180910 firmware release, which has since been fixed, and did not cause connection issues with my wireless network. The symptom of the bug was that shutdown would fail and end in a kernel panic if Bluetooth was turned off, but there were no problems booting and connecting to WiFi.

What are you using for a power supply?

[R-A]

What OS? If it's Raspbian Jessie you should start over with the latest version of Raspbian Stretch 2018-04-18 or newer. Jessie predates the 3B+ and is not compatible (loading the possibly unstable testing firmware with rpi-update will get Jessie booting, but won't fix other problems).

Is there any ways of getting the Wifi working in Jessie? I am using a custom build image (built by someone else) for my solar inverter which still runs on Jessie, and the wifi doesn't work after running apt-get update; apt-get upgrade.

[deanresin]

I updated from Jessie to Stretch and I'm bricked out from the Internet too. This is ridiculous.

I get "No wireless interfaces found" ... "Could not communicate with wpa_supplicant".

I can't even get into the Networking GUI.

[pcmanbob]

I updated from Jessie to Stretch and I'm bricked out from the Internet too. This is ridiculous.

I get "No wireless interfaces found" ... "Could not communicate with wpa_supplicant".

I can't even get into the Networking GUI.

It was never recommend to upgrade from Jessie to Stretch because a working system was never guaranteed after the upgrade, people found there was mixed success.

The recommend way to upgrade to Stretch has always been to flash a new image to an SD card.

[DavidS]

I understand that you had trouble with wifi, though one further question about your issues.

Why did you not have network? Wired ethernet should still have worked without problem, what else was wrong?

[androidi]

I *just* ran to this very same problem myself.

I was fiddling around with connman, which caused some havoc. After 20 mins of crazily whaking my keyboard, I ended up in a situation that wlan0 could not connect to an AP. whoops.

I decided to enter X, only to see that dreaded "No wireless interfaces found" message, and got those same wpa_supplicant error messages while running sudo raspi-config from a terminal.

To fix this, I did the following:

1. I checked my /etc/wpa_supplicant/wpa_supplicant.conf file, and removed all but one wifi network (examples of wpa_supplicant.conf can be found above in this thread).

2. I ran manually, from the CLI: "sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf" – and it werks! It was even displaying the available networks on top right corner of the screen. Yay! But, it kept the console session reserved... ok, so it's a service. Onwards..

3. enable service: "sudo systemctl enable wpa_supplicant.service"

4. "sudo reboot"

5. boom. instant profit.

PS. I also upgraded from Jessie to Stretch without creating a new SD card image. Oh, and connman does not work on Raspbian without first disabling some other services managing the wifi.

[mtroj]

Thanks for the tips androidi. I had the very same problem (it just cropped up a week or so ago) but with your suggestion, all is working again.

[Justen]

For mine, I had to use the old interfaces file, the new one was empty.

Code: Select all

sudo mv /etc/network/interfaces /etc/network/interfaces.old
sudo mv /etc/network/interfaces.dpkg-old /etc/network/interfaces
sudo reboot

the contents of interfaces should appear similar to this:

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

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

[iainfm]

Hi,

This doesn't answer the specific question, but it may help someone. My Pi3 (not 3b+) lost it's wlan interface last night after a dist-upgrade. I tracked the problem down the the wifi firmware. The error in dmesg was:

Code: Select all

[    3.971211] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2

My fix was to move all the files out of /lib/firmware/brcm and replace them with the ones from another Pi3 that was working.

Not sure what caused this, or if this is the best way to fix it, but it's got me working again

[iainfm]

Hi,

This doesn't answer the specific question, but it may help someone. My Pi3 (not 3b+) lost it's wlan interface last night after a dist-upgrade. I tracked the problem down the the wifi firmware. The error in dmesg was:

Code: Select all

[    3.971211] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2

My fix was to move all the files out of /lib/firmware/brcm and replace them with the ones from another Pi3 that was working.

Not sure what caused this, or if this is the best way to fix it, but it's got me working again

Looking at this again, the brcmfmac43430-sdio.txt file doesn't exist in the 'bad' copy of the brcm folder I made before replacing it. It doesn't seem to exist in any packages either, according to an apt-file search. It's .bin counterpart exists in firmware-brcm80211, but not the .txt

[gbleaves]

Hi there,
I have hit the Wi-fi problem big time today. I had initially setup fine at first wifi was good for a few weeks.
Today I installed a new router ready for an upgrade & I changed the SSID and passwords.
I tried the config.txt files nothing, after playing for hours various things, I came to some conclusions on this issue.

NOTE I realised the main symptom was a complete lack of IP setting at all (run ifconfig and check wlan0)
I can only see the MAC hardware address for wlan0.

From other suggestions, this procedure seemed to work for me, [with the latest build Octoprint / Octopi with a RPI 3B]

I tried using 'sudo raspi-config' interface and change the locale to US and reconfigure.
Then run network configure the SSID and WPA password, save & exit to command.
run 'sudo reboot'
all works OK


I hope this helps.
Steve

[moosey]

Try this it worked for me
dtoverlay=pi3-enable-wifi

This worked for me too! After a recent dist upgrade and reboot, there was no wifi hardware being reported. None of the other fixes did anything, but typing the above dtoverlay line into a terminal fixed the problem instantly.

[Pugg]

The update wiped out the Wifi operation, was working fine till it got to the update... nothing seems to fix it... tried all the excuses for it not working,, waste of time.. It use to work great, no longer..

[HawaiianPi]

The update wiped out the Wifi operation, was working fine till it got to the update... nothing seems to fix it... tried all the excuses for it not working,, waste of time.. It use to work great, no longer..

I recently ran an update/full-upgrade on my 4B2 with Raspbian Buster Lite & 4B4 with Raspbian Buster with desktop, and both are working fine (connected to my WiFi and accessible via SSH/VNC).

So whatever your problem is, it's likely on your end. You need to give us more details if you want help.