Unable to connect to WiFi network - VIM3

VIM3
1

Which system do you use? Android, Ubuntu, OOWOW or others?

Others (Custom image built using Yocto)

Which version of system do you use? Please provide the version of the system here:

Linux kernel version 6.0 + NPU patches (available in this repo)

Note: I use xfce4 desktop and NetworkManager to configure the network. Here is the NetworkManager.conf:

[main]

plugins=keyfile

[keyfile]

unmanaged-devices=none

Please describe your issue below:

The system boots up, I see WiFi firmware getting loaded / initialized (see dmesg log below). And the system is able to identify my home WiFi ssid and few others, but when I tried to connect, it doesn’t make a connection.

root@khadas-vim3:~# dmesg | grep brcm
[    6.348473] brcmfmac: F1 signature read @0x18000000=0x17294359
[    6.356289] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[    6.702613] Bluetooth: hci0: BCM: 'brcm/BCM4359C0.khadas,vim3.hcd'
[    6.708742] Bluetooth: hci0: BCM: 'brcm/BCM4359C0.hcd'
[    6.713803] Bluetooth: hci0: BCM: 'brcm/BCM.khadas,vim3.hcd'
[    6.719408] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
[    8.800412] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[    8.823068] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4359/9 wl0: Mar  6 2017 10:16:06 version 9.87.51.7 (r686312) FWID 01-4dcc75d9
[    9.199477] ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_TRIGGER error (-52)

Note: I had a similar issue with Raspberry Pi’s Yocto image and after loading the right firmware binary, this issue was fixed.

Kindly provide me pointers to fix this issue.

Post a console log of your issue below:

Here is my NetworkManager log

Aug 15 20:54:03 khadas-vim3 systemd[1]: Starting Network Manager...
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.8242] NetworkManager (version 1.48.10) is starting... (after a restart, boot:384586a5-29c9-4855-8734-c79c012d8093)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.8243] Read config: /etc/NetworkManager/NetworkManager.conf
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.8305] manager[0xaaaaf6842350]: monitoring kernel firmware directory '/lib/firmware'.
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9392] hostname: hostname: using hostnamed
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9392] hostname: static hostname changed from (none) to "khadas-vim3"
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9399] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9433] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/ffe03000.sd/mmc_host/mmc2/mmc2:0001/mmc2:0001:1/ieee80211/phy0/rfkill2) (driver brcmfmac)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9438] manager[0xaaaaf6842350]: rfkill: Wi-Fi hardware radio set enabled
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9438] manager[0xaaaaf6842350]: rfkill: WWAN hardware radio set enabled
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9453] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.48.10/libnm-device-plugin-wifi.so)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9453] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9454] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9455] manager: Networking is enabled by state file
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9459] settings: Loaded settings plugin: keyfile (internal)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9495] dhcp: init: Using DHCP client 'internal'
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9499] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9506] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9512] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9523] device (lo): Activation: starting connection 'lo' (cc97a0e3-ab13-4a04-a407-3c3a34c7dc80)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9531] device (end0): carrier: link connected
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9537] manager: (end0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9545] manager: (end0): assume: will attempt to assume matching connection 'ccn.eth0' (858ecb89-f258-342d-b121-4aeba4ea728e) (indicated)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9545] device (end0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9553] device (end0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9563] device (end0): Activation: starting connection 'ccn.eth0' (858ecb89-f258-342d-b121-4aeba4ea728e)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9777] device (wlan0): driver supports Access Point (AP) mode
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9795] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Aug 15 20:54:03 khadas-vim3 NetworkManager[2811]: <info>  [1723755243.9803] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.5694] device (wlan0): set-hw-addr: set MAC address to 2E:0D:80:08:F3:6F (scanning)
Aug 15 20:54:04 khadas-vim3 systemd[1]: Started Network Manager.
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6040] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6069] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6079] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6086] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6094] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6105] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6174] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6188] device (end0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6204] agent-manager: agent[139fcd6877e9d0c7,:1.14/org.freedesktop.nm-applet/0]: agent registered
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6222] policy: set 'ccn.eth0' (end0) as default for IPv4 routing and DNS
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6242] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <warn>  [1723755244.6248] dns-sd-resolved[1a2d466b2972e0bf]: send-updates SetLinkDomains@2 failed: GDBus.Error:org.freedesktop.resolve1.LinkBusy: Link end0 is managed.
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6256] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6267] device (lo): Activation: successful, device activated.
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6284] device (end0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6570] device (end0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6574] device (end0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6581] manager: NetworkManager state is now CONNECTED_SITE
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6586] device (end0): Activation: successful, device activated.
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.6598] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8218] device (wlan0): supplicant interface state: internal-starting -> disconnected
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8220] Wi-Fi P2P device controlled by interface wlan0 created
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8225] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8229] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8236] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Aug 15 20:54:04 khadas-vim3 NetworkManager[2811]: <info>  [1723755244.8245] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 15 20:54:05 khadas-vim3 NetworkManager[2811]: <info>  [1723755245.3621] manager: startup complete
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.0466] device (wlan0): Activation: starting connection 'cnnamhssbb' (a6fffa21-0c01-49b7-9954-792c1e605224)
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.0469] audit: op="connection-add-activate" uuid="a6fffa21-0c01-49b7-9954-792c1e605224" name="cnnamhssbb" pid=2609 uid=0 result="success"
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.0488] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6054] device (wlan0): set-hw-addr: reset MAC address to B8:13:32:E1:E5:2A (preserve)
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6299] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6307] device (wlan0): Activation: (wifi) access point 'cnnamhssbb' has security, but secrets are required.
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6307] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6312] sup-iface[0d16a0aa707dbda6,1,wlan0]: wps: type pbc start...
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6322] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6323] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6325] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6325] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> disconnected
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6347] device (wlan0): supplicant interface state: disconnected -> inactive
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6348] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6822] device (wlan0): supplicant interface state: inactive -> scanning
Aug 15 20:55:01 khadas-vim3 NetworkManager[2811]: <info>  [1723755301.6823] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2617] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2632] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2648] device (wlan0): Activation: (wifi) connection 'cnnamhssbb' has security, and secrets exist.  No new secrets needed.
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2649] Config: added 'ssid' value 'cnnamhssbb'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2650] Config: added 'scan_ssid' value '1'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2650] Config: added 'bgscan' value 'simple:30:-70:86400'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2651] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2652] Config: added 'auth_alg' value 'OPEN'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.2652] Config: added 'psk' value '<hidden>'
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.3585] device (wlan0): supplicant interface state: scanning -> associating
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.3586] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.9320] device (wlan0): supplicant interface state: associating -> associated
Aug 15 20:55:18 khadas-vim3 NetworkManager[2811]: <info>  [1723755318.9321] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 15 20:55:28 khadas-vim3 NetworkManager[2811]: <info>  [1723755328.9539] device (wlan0): supplicant interface state: associated -> disconnected
Aug 15 20:55:28 khadas-vim3 NetworkManager[2811]: <info>  [1723755328.9540] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Aug 15 20:55:29 khadas-vim3 NetworkManager[2811]: <info>  [1723755329.0619] device (wlan0): supplicant interface state: disconnected -> scanning
Aug 15 20:55:29 khadas-vim3 NetworkManager[2811]: <info>  [1723755329.0620] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Aug 15 20:55:29 khadas-vim3 NetworkManager[2811]: <info>  [1723755329.6260] device (wlan0): supplicant interface state: scanning -> associating
Aug 15 20:55:29 khadas-vim3 NetworkManager[2811]: <info>  [1723755329.6261] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Aug 15 20:55:30 khadas-vim3 NetworkManager[2811]: <info>  [1723755330.2832] device (wlan0): supplicant interface state: associating -> associated
Aug 15 20:55:30 khadas-vim3 NetworkManager[2811]: <info>  [1723755330.2833] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.1379] device (wlan0): supplicant interface state: associated -> disconnected
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.1380] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.2379] device (wlan0): supplicant interface state: disconnected -> scanning
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.2380] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.7898] device (wlan0): supplicant interface state: scanning -> associating
Aug 15 20:55:41 khadas-vim3 NetworkManager[2811]: <info>  [1723755341.7899] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Aug 15 20:55:42 khadas-vim3 NetworkManager[2811]: <info>  [1723755342.3632] device (wlan0): supplicant interface state: associating -> associated
Aug 15 20:55:42 khadas-vim3 NetworkManager[2811]: <info>  [1723755342.3633] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <warn>  [1723755343.1339] device (wlan0): Activation: (wifi) association took too long
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.1340] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.1346] sup-iface[0d16a0aa707dbda6,1,wlan0]: wps: type pbc start...
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <warn>  [1723755343.1350] device (wlan0): Activation: (wifi) asking for new secrets
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.1898] device (wlan0): supplicant interface state: associated -> disconnected
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.1899] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.2179] device (wlan0): supplicant interface state: disconnected -> scanning
Aug 15 20:55:43 khadas-vim3 NetworkManager[2811]: <info>  [1723755343.2180] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Aug 15 20:56:53 khadas-vim3 NetworkManager[2811]: <warn>  [1723755413.6306] device (wlan0): no secrets: User canceled the secrets request.
Aug 15 20:56:53 khadas-vim3 NetworkManager[2811]: <info>  [1723755413.6307] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Aug 15 20:56:54 khadas-vim3 NetworkManager[2811]: <info>  [1723755414.1935] device (wlan0): set-hw-addr: set MAC address to 7A:D2:98:09:C1:DB (scanning)
Aug 15 20:56:54 khadas-vim3 NetworkManager[2811]: <warn>  [1723755414.2093] device (wlan0): Activation: failed for connection 'cnnamhssbb'
Aug 15 20:56:54 khadas-vim3 NetworkManager[2811]: <info>  [1723755414.2104] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 15 20:56:54 khadas-vim3 NetworkManager[2811]: <info>  [1723755414.2834] device (wlan0): supplicant interface state: scanning -> disconnected
Aug 15 20:56:54 khadas-vim3 NetworkManager[2811]: <info>  [1723755414.2835] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
2

I seem to recall they have a gui setup and that is the best way to go. Typically with a desktop always use the desktop tools to avoid funky stuff.

Post your $pstree

3 
root@khadas-vim3:~# pstree
systemd-+-NetworkManager---3*[{NetworkManager}]
        |-agetty
        |-at-spi2-registr---3*[{at-spi2-registr}]
        |-atd
        |-avahi-daemon---avahi-daemon
        |-bluetoothd
        |-camera-udp-list---2*[{camera-udp-list}]
        |-crond
        |-2*[dbus-daemon]
        |-dbus-launch
        |-dnsmasq
        |-gpg-agent
        |-gvfs-gphoto2-vo---3*[{gvfs-gphoto2-vo}]
        |-gvfsd-+-gvfsd-network---3*[{gvfsd-network}]
        |       |-gvfsd-trash---4*[{gvfsd-trash}]
        |       `-3*[{gvfsd}]
        |-gvfsd-metadata---3*[{gvfsd-metadata}]
        |-psplash-systemd
        |-rpcbind
        |-sh---pstree
        |-syslogd
        |-systemd-journal
        |-systemd-logind
        |-systemd-network
        |-systemd-nsresou---6*[systemd-nsresou]
        |-systemd-resolve
        |-systemd-timesyn---{systemd-timesyn}
        |-systemd-udevd
        |-systemd-userdbd---4*[systemd-userwor]
        |-wpa_supplicant
        |-xfconfd---3*[{xfconfd}]
        `-xinit-+-Xorg---2*[{Xorg}]
                `-x-session-manag-+-Thunar---3*[{Thunar}]
                                  |-Xsession
                                  |-at-spi-bus-laun-+-dbus-daemon
                                  |                 `-3*[{at-spi-bus-laun}]
                                  |-nm-applet---4*[{nm-applet}]
                                  |-xfce4-notifyd---3*[{xfce4-notifyd}]
                                  |-xfce4-panel-+-panel-10-notifi---4*[{panel-10-notifi}]
                                  |             |-panel-14-action---4*[{panel-14-action}]
                                  |             |-panel-6-systray---3*[{panel-6-systray}]
                                  |             `-4*[{xfce4-panel}]
                                  |-xfdesktop---4*[{xfdesktop}]
                                  |-xfsettingsd---3*[{xfsettingsd}]
                                  |-xfwm4---4*[{xfwm4}]
                                  `-3*[{x-session-manag}]

Please note, WiFi with the same build setup is working on Raspberry Pi 4 and 5, after correcting the firmware bin image.

4 
$ nmcli radio wifi on

$ nmcli device wifi list

That should show what is in range if the wifi is actually working, if it shows stations you can use nmcli to set the password. If not it would be a more complicated issue.

2 Likes
5 
root@khadas-vim3:~# nmcli radio wifi on
root@khadas-vim3:~# nmcli device wifi list
        BE:A7:B9:58:80:15  my_ssid           Infra  40    270 Mbit/s  90      ****  WPA2 WPA3
        BE:A7:B9:58:80:14  --                Infra  40    270 Mbit/s  90      ****  WPA2
        BE:A7:B9:58:87:8D  my_ssid           Infra  40    270 Mbit/s  69      ***   WPA2 WPA3
        BE:A7:B9:58:87:8C  --                Infra  40    270 Mbit/s  69      ***   WPA2
        F0:ED:B8:2A:BE:0A  --                Infra  149   270 Mbit/s  47      **    WPA2
        F2:ED:B8:3A:BE:0A  --                Infra  149   270 Mbit/s  45      **    WPA2
        <truncated>

Here the first instance of my_ssid (name changed), appeared in green.

root@khadas-vim3:~# nmcli device wifi connect my_ssid password my_password
Error: Timeout 90 sec expired.

Here I checked for any errors from kernel drivers (particularly sdio) using dmesg, and nothing was found at the time-range when the above timeout happened.

Additional info:

root@khadas-vim3:~# iw wlan0 info
Interface wlan0
        ifindex 3
        wdev 0x1
        addr ca:94:d0:b7:89:69
        type managed
        wiphy 0
        channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
        txpower 31.00 dBm
6 
nmcli device wifi connect "SSID" password "password"

Be sure to use the " ".
Since it is on and working it has to be a credential issue/security type or the " " are missing.

Also, your gateway might be blocking. Your gateway only knows your board by the mac and if it smells something funky it will block. Like different hostname or ??, this happens when you have the same board with the same mac and sometimes use a different OS. Too many tries with the wrong credentials will also lock you permanently or a time interval. Log into your gateway and see what is up if it still does not connect.

Worst case and test only, open up a guest account without security and see what happens. Do not leave it open long if you are in a heavily populated area. If you can log in when its open, lock it back down immediately.

7

Added double quotes to the nmcli device wifi connect command, but the results are same (i.e., timeout after 90 sec).

Configured a guest network with empty password, the connection was successful and it remained stable for about a minute (but I disabled the network, for security reasons).

8

The vim3 is working fine based upon that. Do you have admin access to your internet gateway? It might be an issue with that. At this point I am running out possibilities to look at. Also is your gateway wifi running the same security as the board?
It might be easier to get another wifi AP, configure it and connect it to your gateway with ethernet. Then log into into it, sorry, I am running out suggestions.

9

Positive update:

If I unload the broadcom driver module and reload it manually after boot up (used following commands), I see that my WiFi connection is happening on my network with WPA3/WPA3 security.

modprobe -r brcmfmac
modprobe brcmfmac

This suggests me to think that, there could be some timing issue with the loading of firmware at the start. I will add a systemd script to delay the initialization of the driver or reload it as a temporary work around.

But I have to confess that, I generated a patch file between drivers/net/wireless/broadcom folders of kernel version v6.0 and v6.11. And then applied the patch on top of v6.0 (my version). This could also be a factor.

10

6.11 is RT capable and this might be creating an issue too, if RT is turned on in the kernel. Have you tried wpa2 and see what happens with that?

It would be better to have it follow a required service instead of a delay. A delay still might place it ahead of another service it depends on. With systemd it can load any core that is available to speed getting up and running. So it is important to have it in sequential order. Just don’t know what, that should be… I don’t have a vim3 up any more or I would look at how ours was configured. It should run out of the box without any problems, don’t recall us having any issues other than maybe wpa3 and our ap.

11

Thanks for the wpa2 suggestion, will look into it. My observation here is, if I unload & reload the brcmfmac module before wpa_supplicant.service, then the issue is still persisting. WiFi works only if do it after the wpa_supplicant.service. I see your point on wpa2.

Also, when I said “delay” I meant systemd service only. Here is the service file that I tested and found to be working:

12

Glad you have it running. The rx must needs some time to internally stabilize??.

1 Like