VIM3L + latest Ubuntu image from Krescue == no wireless adapter?

Which Khadas SBC do you use?

VIM3L

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

Ubuntu 20.04

Which version of system do you use? Khadas official images, self built images, or others?

Latest Khadas image from Krescue as of 20-May-2022

Please describe your issue below:

No wireless interface appears on boot after a fresh install of Ubuntu Server

Post a console log of your issue below:

Freshly installed + apt update && apt upgrade:

Welcome to Fenix 1.0.11 Ubuntu 20.04.4 LTS Linux 5.17.0  
 _  ___               _            __     _____ __  __ _____ _     
| |/ / |__   __ _  __| | __ _ ___  \ \   / /_ _|  \/  |___ /| |    
| ' /| '_ \ / _` |/ _` |/ _` / __|  \ \ / / | || |\/| | |_ \| |    
| . \| | | | (_| | (_| | (_| \__ \   \ V /  | || |  | |___) | |___ 
|_|\_\_| |_|\__,_|\__,_|\__,_|___/    \_/  |___|_|  |_|____/|_____|
                                                                   

 * Website:        https://www.khadas.com
 * Documentation:  https://docs.khadas.com
 * Forum:          https://forum.khadas.com

Last login: Fri May 20 23:27:10 2022 from 192.168.1.9
khadas@Khadas:~$ uname -a
Linux Khadas 5.17.0 #1.0.11 SMP Fri Apr 29 23:15:48 CST 2022 aarch64 aarch64 aarch64 GNU/Linux

Unfortunately, the wlan0 interface is missing:

khadas@Khadas:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether c8:63:14:71:2f:06 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.83/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
       valid_lft 86284sec preferred_lft 86284sec
    inet6 fe80::f2c8:6927:49f0:bdc7/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

It’s not available in rfkill:

khadas@Khadas:~$ rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: hci1: Bluetooth
        Soft blocked: no
        Hard blocked: no

And there’s nothing in the kernel logs about it:

khadas@Khadas:~$ dmesg | grep wlan
khadas@Khadas:~$ 

Of course, NetworkManager can’t see or manage it either:

khadas@Khadas:~$ nmcli device show
GENERAL.DEVICE:                         eth0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         C8:63:14:71:2F:06
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Wired connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.1.83/24
IP4.GATEWAY:                            192.168.1.1
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 100
IP4.ROUTE[2]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[3]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]:                             192.168.1.1
IP4.DOMAIN[1]:                          localdomain
IP6.ADDRESS[1]:                         fe80::f2c8:6927:49f0:bdc7/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 100

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ::1/128, nh = ::, mt = 256

Any suggestions? I can try the “desktop” image if that’s likely to be different somehow.

@rcoder The Wi-Fi of VIM3L is not very stable. When I tested it, it sometimes worked and sometimes failed.

Sorry, I’m a little unsure of your meaning.

“WiFi…is not very stable” meaning the board is unreliable, or that it simply fails to work reliably under the current Khadas-suggested Ubuntu kernel?

I ran this exact same board in a different project more than six months ago and WiFi definitely worked.

I’m starting to think that I need to spend some quality time with the Fenix toolkit again, as between this and some NVMe compatibility issues I’ve hit in recent weeks I suspect there is some kernel patching + compiling in my future.

we need to check last changes for mainline kernel , and prepare patch , its just a kernel problem

1 Like

What happens when you do this?

nmcli device wifi connect {ssid} password "[password]"

That…worked? Thanks, @foxsquirrel.

I’m somewhat mystified as to why the interface flat-out did not appear in any other configuration view – including nmtui – until running the above, but TIL to try nmcli first.

…at least until I switch away from having NetworkManager in the loop at all, as I’ll do shortly. (I prefer using systemd-networkd once I have >2 interfaces to manage, and this board is going to be running a few VMs + at least one Wireguard tunnel.)

Check nmcli for autostart of wifi. It “should” be on by default, not sure why this happens.

These are good networking platforms, I hope a future model will have at least 2 non-shared 1gb ethernet ports.

sure no

latest images with latest mainline kernel have problems with wi-fi
please check dmesg | grep brcm messages

1 Like