I installed OMV 5 in my Raspberry Pi 4B running Raspbian GNU/Linux 10 (buster), following this video https://www.youtube.com/watch?v=sYDyvr9Uc6Y (script installation).

Just right after install OMV 5 and reboot the RPi 4B the WiFi stopped working. As can be seen in the picture 1 the WiFi complains about that there's "No wireless interface found".

enter image description here

Well, I've checked my /etc/wpa_supplicant/wpa_supplicant.config, which contains:

pi@raspberrypi:~ $ cat /etc/wpa_supplicant/wpa_supplicant.conf 
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev



which looks correcto to me, and what I have before installing OMV 5. One thing that have changed is the /etc/network/interface file. It now looks like:

pi@raspberrypi:~ $ cat /etc/network/interfaces
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# Use systemd-networkd to configure additional interface stanzas.

when it used to contain:

pi@raspberrypi:~ $ 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

I've tried to raplace it with the original file but still doesn't work. I've downloaded a fresh Raspbian 10 image to check the differences between these files and everything looks the same except for this /etc/network/interface file. I've also checked the content of /etc/dhcp/ and is the same as the fresh Raspbian version.

Further, when I trie to use raspi-conf to change things in the wpa_supplicant is complains as follows: enter image description here enter image description here enter image description here enter image description here

I've also done a rpi-update to update the firmware. I've heard that OMV might disable or remove wifi drivers but when I do

pi@raspberrypi:~ $ sudo lshw -C network
     description: Ethernet interface
     physical id: 1
     logical name: eth0
     serial: dc:a6:32:60:6c:b2
     size: 1Gbit/s
     capacity: 1Gbit/s
     capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=bcmgenet driverversion=v2.0 duplex=full ip= link=yes multicast=yes port=MII speed=1Gbit/s
     description: Wireless interface
     physical id: 2
     logical name: wlan0
     serial: dc:a6:32:60:6c:b4
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=brcmfmac driverversion=7.45.202 firmware=01-72f6ece2 multicast=yes wireless=IEEE 802.11

Does anyonw know how to fix it? Any help?

  • Please don't post pictures of text. Instead paste the thext direct into the question. – Ingo Mar 30 '20 at 11:51
  • @Ingo Ok, sorry. I thought it would be more easy to understand. Should I change it? – Ignacio López de Arbina Mar 31 '20 at 8:56
  • Ok. I found a temporary solution. What I see is that wlan0 interface is down. To set it up I see you can do sudo ip link set wlan0 up and then sudo wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf But this fixes the problem for a while. After reboot everything is down again. – Ignacio López de Arbina Mar 31 '20 at 8:59
  • "Should I change it?" - next time :) – Ingo Mar 31 '20 at 9:10

Try adding id_str to the network definition:

    id_str = "wlan1"


    id_str = "wlan2"


It seems OMV completely occupies the network setup with its own settings and destroy the default Raspbian networking with dhcpcd. OMV modifies /etc/network/interfaces and claims to use systemd-networkd for network setups. Both systems are not used by Raspbian so I'm afraid you are without luck to use OMV with Raspbian if you do not find instructions from OMV how to configure the network to be compatible with Raspbian. B.t.w., using rpi-update will make things rather bad.

  • Yes, this is what it looks like. But I don't see the point, in case you cannot use (don't want to) Ethernet connection, as in my case, you cannot access your server via WiFi... Thanks for the answer, I'll as in OMV forum if they ever know how to fix it. However, I managed to make it work for a while using this WiFi set-up guide [linuxcommando.blogspot.com/2013/10/…. But after reboot the configuration is not saved. – Ignacio López de Arbina Mar 31 '20 at 8:37

Under Buster, you will need to set in raspi-config under

4 Localisation Options

the Wifi country

I4 Change Wi-fi Country

otherwise, the Wifi will be disabled by rfkill.

  • What does these lines mean? Where to set them? – Ingo Mar 30 '20 at 11:35
  • You may have recognized the 4 Localisation Options form the first menu that the OP posted. – Ljm Dullaart Mar 31 '20 at 8:14
  • Thanks for the answer @LjmDullaart. I've seen this "Set Country" in many places but I don't understand why the country is so importat. Could you explain? Further, as in the explample I put in my post trying to set the SSID via raspi-config, when trying to set the country it says the same that `Could not communicate with wpa_supplicant – Ignacio López de Arbina Mar 31 '20 at 8:52
  • Different countries have different laws for frequency assignments and allowed power. But for some reason, from Raspian Buster on, it has been decided to kill any WiFi until the country is set via the menu, via the localisation options. Set the coutry before you define the SSID. I don't know why that suddenly got so important, so I can't explain it. I just know that I spend hours trying to get WiFi going on buster, and this was the solution. – Ljm Dullaart Mar 31 '20 at 10:29
  • I see. Thanks for the info. I've seen this in many places so I guess Rapsbian Buster does what you say and requires to set the country via raspi-config. – Ignacio López de Arbina Mar 31 '20 at 11:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.