Tiny Core Base > Raspberry Pi
Manage wifi (RPi3) with NetworkManager
Juanito:
--- Quote from: derjan on February 14, 2018, 08:55:24 AM ---Thanks for the reply, but not installing the wifi extension doesn't change the unavailability of wifi.
--- End quote ---
As mentioned, it's not an issue of the wifi extension per se - the problem is that networkmanager depends on the wpa_supplicant-dbus extension whereas wifi depends on the wpa_supplicant extension.
If you load both networkmanager and wifi, you will have the wpa_supplicant and wpa_supplicant-dbus extensions loaded on top of each other and it will not be obvious if either of them works properly.
In addition, if you are going to use networkmanager, you need to use it to manage all of your network connections, you cannot have it starting wpa_supplicant instances via dbus and the wifi extension starting wpa_supplicant instances directly without running the risk of conflicting commands.
Here's what works for me:
--- Code: ---$ tce-load -i firmware_iwlwifi-7260
$ tce-load -i networkmanager
$ sudo /usr/local/etc/init.d/dbus start
$ sudo /usr/local/etc/init.d/networkmanager start
$ nmcli d wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
juanitonet Infra 8 54 Mbit/s 72 *** WPA2
ane Infra 6 54 Mbit/s 62 *** WPA1 WPA2
AliNetwork Infra 6 54 Mbit/s 57 *** WEP
juanitonet Infra 48 54 Mbit/s 54 ** WPA2
...
$ nmcli d wifi connect juanitonet password ********
Device 'wlan0' successfully activated with '6ccf90b1-7dfb-4acf-a83d-b3db54c37c9b'.
--- End code ---
derjan:
Yes, I understand, that's why I set up a new SD card and did not install the wifi.tcz extension (which mentions wpa_supplicant in it's description), only the firmware-rpi3-wireless.tcz (which contains lib/firmware/brcm/brcmfmac43430-sdio.bin) and networkmanager extensions. So there shouldn't be a dbus incompatible wpa_supplicant version installed. ls /usr/local/tce.installed/ only lists wpa_supplicant-dbus and no other wpa_supplicant.
Without the firmware, the wireless interface isn't found/listed. Or is the Raspberry Pi wireless firmware also incompatible with wpa_supplicant via dbus? Then what's the alternative?
Juanito:
firmware-rpi3-wireless is the extension you need, but it needs to be loaded before wireless-KERNEL for the firmware to be loaded properly - you can check using "dmesg | tail -20" or similar.
You can use "tce-status -i" to check if networkmanager and all of it's recursive dependencies are loaded, see:
http://tinycorelinux.net/9.x/armv7/tcz/networkmanager.tcz.tree
Did you verify that the dbus and networkmanager daemons are running with, for example, "ps aux | grep dbus"
Juanito:
Hmm - there's something amiss here. If I modify the wifi extension dep file to use wpa_supplicant-dbus, the RPi3 wifi connects to my ap.
With networkmanager I get this:
--- Code: ---$ nmcli d status
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
wlan0 wifi unavailable --
lo loopback unmanaged --
--- End code ---
I'll try to fix this in the next couple of days.
derjan:
Thanks for still looking into this! The networkmanager output is the same on my RPi.
This is the output of tce-status -i – it seems like all the dependencies of networkmanager are installed:
--- Code: ---bluetooth-4.9.22-piCore-v7
bluez
bzip2-lib
ca-certificates
dbus
dbus-glib
dhcpcd
expat2
firmware-rpi3-wireless
gamin
gcc_libs
glib2
icu
kmaps
libICE
libSM
libX11
libXau
libXdmcp
libbluetooth
libedit
libelf
libgcrypt
libgpg-error
libical
libiw
liblzma
libmbim
libndp
libnl
libqmi
libsoup
libssh2
libudev
libxcb
libxml2
mc
modemmanager
ncurses
networkmanager
nspr
nss
openssh
openssl
pcre
ppp
readline
sbc
sqlite3
wireless-4.9.22-piCore-v7
wireless_tools
wpa_supplicant-dbus
--- End code ---
dbus and networkmanager are running:
--- Code: ---tc@box: ps aux | grep dbus
1122 tc /usr/local/bin/dbus-daemon --system
tc@box: ps aux | grep -i networkmanager
1126 root /usr/local/sbin/NetworkManager
1152 root /usr/local/sbin/dhcpcd -B -K -L -A -G -c /usr/local/lib/NetworkManager/nm-dhcp-helper -4 -h pi-sensor eth0
--- End code ---
If I kill the process nmcli just prints: Error: NetworkManager is not running.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version