Hello comunity/maintainers,
Please could anyone help me?
After fesh install Debian 13 trixie Minimal (CLI)    —    current 6.18.44 there is no wlan0 nor hci0, only theese events in dmesg:

[    4.389072] Btrfs loaded, zoned=yes, fsverity=yes
[    4.987196] systemd[1]: systemd 257.13-1~deb13u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE)
[    5.729379] sysfs: cannot create duplicate filename '/devices/virtual/tty/ttyBT0'
[    5.729536]  mtty_probe+0x120/0x2c8 [sprdbt_tty]
[    5.729664]  mtty_pdev_init+0x50/0xfb0 [sprdbt_tty]
[    5.729796] kobject: kobject_add_internal failed for ttyBT0 with -EEXIST, don't try to register things with the same name in the same directory.
[    5.812146] WCN: start_marlin [MARLIN_WIFI]
[    5.812162] WCN: marlin power state:0, subsys: [MARLIN_WIFI] power 1
[   40.964296] unisoc_wifi unisoc_wifi: probe with driver unisoc_wifi failed with error -1


Any help is appreciated
Regards
Jan

This should be fixed already. Try building an image or kernel package from source https://docs.armbian.com/build-framework/

Weird, downloaded image on monday from armbian web...

I will try the build, will be first time:-)
Regards
Jan

7 hours ago, slmq said:

image on monday f

Doesn't mean the image was also made on Monday. Check kernel build date 

Sure not bulit on monday:-), just wanted to say, it was recent - web says built on 14.Aug 2026,  uname -v
#1 SMP PREEMPT Sun Aug  9 18:25:30 UTC 2026
 

Edited September 13Sep 13 by slmq

I had the same issue and built image from main branch with this command

$ ./compile.sh BOARD=orangepi4-lts RELEASE=trixie BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no

 

Wi-fi now works, but only 2.4Ghz, 5ghz doesn't work 😢

19 hours ago, ownik said:

Wi-fi now works, but only 2.4Ghz, 5ghz doesn't work

I see from http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/orange-pi-4-LTS.html

that it is 'dual-band', but what what works might depend on how you use the WiFi subsystem. It seems to me the -LTS is a cost-reduced/optimized variant of the non-LTS. At least completely different WiFi, that needs attention. Have a look at the firmware, how it is loaded and if it can do scanning, so sort of auto select band. In theory does not have to be, but lot more info is needed then.

Details for Orange Pi 4 LTS (UWE5622, sprdwl_ng), Armbian 26.11 trunk, kernel 6.18.57:

 

- Firmware loads fine (wcnmodem-38222.bin). 2.4 GHz works.
- 5 GHz (ch. 36, WPA2/CCMP, PMF disabled) depends on the AP mode (OpenWrt hostapd):
  * AX or AC (tried 20 and 40 MHz): CTRL-EVENT-ASSOC-REJECT status_code=1.
    AP logs "authenticated", then "Station sent an invalid association request"
  * N only, 20 MHz (no VHT): associates and connects normally on 5180 MHz
- disable_vht=1 in wpa_supplicant does not change it, so the malformed VHT part of the association request seems to be added by the driver/firmware.

 

The same symptom (2.4 GHz only) was already reported on this board in 2023 on
kernel 6.1.30, so it doesn't look like a recent regression:

 

 

Anything specific you'd like me to check?

Update: the driver README (armbian/uwe5622) lists only "802.11b/g/n, 2.4 GHz" and there is no info about support -LTS version, only non-LTS

In practice the board sees 5 GHz networks and the link is fully usable on 5 GHz (DHCP, ping and SSH work) when the AP runs in N mode.

LTS and non LTS has different wifi chip. 

BTW, (some) fixes are coming up https://github.com/armbian/build/pull/11056

11 hours ago, ownik said:

The same symptom (2.4 GHz only) was already reported on this board in 2023 on
kernel 6.1.30, so it doesn't look like a recent regression:

Good you provided various links/info, unfortunately, it doesn't look good to me and I recognize several issues from my experience with mt7921u (as USB-stick). I have 2 of them, 1 with a brand name and one without a brand name. Should behave the same, but do not. I tried various setups, but I just can confirm what is on internet for several years already.

 

My goal is coverage, so 5GHz not needed actually, but it is sold as also doing 5GHz, which I got working when client. As Access Point, I only can get 2.4GHz working and then still today now I see issues that I don't understand and thought were fixed with a kernel minor version upgrade, but that is another issue, nothing RF related (I think).

 

So w.r.t. uwe5622, I can not really help you further. I have not looked into specific HW/architecture/design, but make sure you know how specs are marketed.

Same as for myself, if you want solid WiFi, make sure you get something with a chipset or from a company that has proven itself for a decade or longer. Or accept that it is like it is and limit your deployment to what works. I personally stay away from something with DKMS, I actually removed the whole dkms from my Armbian installs as it causes too much issues in general throughout the years when using rolling release Linux. But if you already have the HW, maybe try a very latest kernel, build all yourself and hope it is something in the Linux kernel that causes the issue and not something related to unisoc firmware blob. The latter is closed source of course and may have a several updates and well documented what is fixed, or just a one shot and no updates. For my mt7921 for example, the bin/blob file has a name with different increasing timestamps, but contents are the same for years, doesn't matter if Debian or OpenWRT.