Search the Community

Issue is present in both Focal and Buster, wlan0 work with downloader image and become faulty after applying recent update ( probably new kernel) I've found that Wifi driver fail to start due to missing chipset firmware binaries in /lib/firmware/xr819 dmesg trace [ 70.648156] xradio ERR: FWIO: can't load sdd file xr819/sdd_xr819.bin. [ 70.648185] xradio ERR: BH: bh thread exiting However downloading firmware from https://github.com/armbian/firmware/tree/master/xr819 doesn't fix the issue, it seem that something is broken into kernel ( kernal side wifi driver of fwio loader? I don't know it yet) Board info : ___ ____ _ _____ / _ \| _ \(_) |__ /___ _ __ ___ | | | | |_) | | / // _ \ '__/ _ \ | |_| | __/| | / /| __/ | | (_) | \___/|_| |_| /____\___|_| \___/ Welcome to Armbian 20.08.16 Buster with Linux 5.8.16-sunxi System load: 2% Up time: 30 min Memory usage: 15% of 491M IP: 192.168.1.253 CPU temp: 10°C Usage of /: 2% of 58G [ General system configuration (beta): armbian-config ]

put 2 wifi dongles in cause xradio 819 on opi zero (if it's the original zero) is prob. the worst onboard wifi you can have prone to hang the kernel with it when it fails (I don't think that everybody ever took an effort to fix that)..

I guess they rebranded an armbian image which includes alternative drivers for xradio and added the temperature fix....

I had in mind all relevant changes. I see karabek is also not much up2date with commits from upstream > https://github.com/fifteenhex/xradio I would do myself, but in that case I risk changing my good mood ... "do i relly need to dig into this xradio stuff "

Alright, I rebased my changes on karabek's repository: https://github.com/dbeinder/xradio/tree/karabek_rebase The powersave commit is now split, with the power-lowering fix in the first part, and enabling userspace control over powersave in the second. After some more direct comparison, I'm starting to think the part about removing driver-level TX rate selection doesn't make a measurable difference, in either throughput or dropped packets. But since my much simpler code doesn't seem to make it worse either, I think that was just hacks built around the CW11x0 and simply never removed. But as long as there is no upside, it's probably better not to diverge too much from the CW1200 mainline version, so I left that in a separate branch for now: https://github.com/dbeinder/xradio/commits/karabek_rebase_minstrel

I know most of you probably don't want to hear any more about this chip, but I recently fixed quite a few long standing issues. It's not perfect yet, but it improves scanning/reliable reconnect, incoming frames missed in powersave, ping times, and rate selection. Here's the patch set: https://github.com/fifteenhex/xradio/pull/12 Edit: rebased from karabek: https://github.com/dbeinder/xradio/commits/karabek_rebase And some important comments about powersave: https://github.com/fifteenhex/xradio/pull/11#issuecomment-616226880 In short, relative to the current version, with powersave on, idle consumption is lower by 200mW, but with powersave off, it is 300mW higher - so that should be a consideration if you want to integrate this into Armbian builds for tiny boards like OPZero. Of course a 65MBit chip will never be fast, but I'd say it is pretty usable as an IoT node now. This hasn't seen much testing, so your comments are appreciated.

I guess what Igor meant to say was that you should search for XR819 or xradio in forums to find topics with similar issues and if users solved their issues. Regardless of that I'd still recommened that you upgrade your kernel to sunxi-current (to say Linux 5.4.x) and check if the issue persists.

Sorry, I have not clearly understood your suggestion yet. You mean that I should search and install the XR819 or xradio driver for my board to check first, right?

There are many many users with this board - better use a search engine and throw in: XR819 or xradio and check results.

I have set in the lib.config file the version 5.1 (same thing happen with version 5.6) After fixing all the compiling issues I was able to compule: dpkg-deb: building package 'linux-headers-5.1.21-sunxi64' in '../linux-headers-5.1.21-sunxi64_20.05.0-trunk_arm64.deb'. dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_20.05.0-trunk_arm64.deb'. dpkg-deb: building package 'linux-image-5.1.21-sunxi64' in '../linux-image-5.1.21-sunxi64_20.05.0-trunk_arm64.deb'. dpkg-buildpackage: info: binary-only upload (no source included) dpkg-deb: building package 'linux-source-5.1.21-dev-sunxi64' in '/home/ilan/armbian/build/.tmp/linux-source-dev-sunxi64_20.05.0-trunk_all.deb'. dpkg-deb: error: failed to read archive '/home/ilan/armbian/build/output/debs/linux-image-dev-sunxi64_20.05.0-trunk_arm64.deb': No such file or directory [ o.k. ] Starting rootfs and image building process for [ bananapim64 bionic ] [ o.k. ] Checking for local cache [ bionic-cli-arm64.881...e08.tar.lz4 ] [ o.k. ] Extracting bionic-cli-arm64.881...e08.tar.lz4 [ 2 days old ] [ .... ] bionic-cli-arm64.881...e08.tar.lz4: 364MiB [64.3MiB/s] [==========================================================================================================>] 100% [ o.k. ] Adding Armbian repository and authentication key [ /etc/apt/sources.list.d/armbian.list ] [ o.k. ] Applying distribution specific tweaks for [ bionic ] [ o.k. ] Applying common tweaks cp: cannot stat '/home/ilan/armbian/build/output/debs/linux-image-dev-sunxi64_20.05.0-trunk_arm64.deb': No such file or directory [ .... ] Installing [ linux-image-dev-sunxi64_20.05.0-trunk_arm64.deb ] [ .... ] Installing [ linux-u-boot-dev-bananapim64_20.05.0-trunk_arm64.deb ] cp: cannot stat '/home/ilan/armbian/build/output/debs/linux-headers-dev-sunxi64_20.05.0-trunk_arm64.deb': No such file or directory [ .... ] Installing [ linux-headers-dev-sunxi64_20.05.0-trunk_arm64.deb ] [ .... ] Installing [ armbian-config_20.05.0-trunk_all.deb ] [ .... ] Installing [ armbian-firmware_20.05.0-trunk_all.deb ] [ o.k. ] Enabling serial console [ ttyS0 ] As you can see it creates the headers and kernel version 5.1.21 but when it going to the stage to implement it in the image it looks for other deb files that are not created... also doesnt create the DTB deb file. eventually the image that is created doest work. So changing the linux-headers-5.1.21... and the linux-image-5.1.21 to linux-headers-dev... and the linux-image-dev.... then running the compilation again and switch the file names a second before it implement them I manage to overcome this error. but no DTB file and the implentation in the linux image doesnt work. there is not even a link from Image-> to the vmlinuz-5.1.21-sunxi64 at the boot folder. I havent found anywhere why it doesnt create the DTB file and why it doesnt link the image correctly. Here is the patch I have created for the compilation to complete. diff --git a/arch/arm64/boot/dts/allwinner/Makefile b/arch/arm64/boot/dts/allwinner/Makefile index f670458ae..b81175502 100644 --- a/arch/arm64/boot/dts/allwinner/Makefile +++ b/arch/arm64/boot/dts/allwinner/Makefile @@ -1,29 +1,3 @@ # SPDX-License-Identifier: GPL-2.0 -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-amarula-relic.dtb dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-bananapi-m64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-nanopi-a64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-olinuxino.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-orangepi-win.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pine64-lts.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pine64-plus.dtb sun50i-a64-pine64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pinebook.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-sopine-baseboard.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-teres-i.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-bananapi-m2-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-bananapi-m2-plus-v1.2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-emlid-neutis-n5-devboard.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-libretech-all-h3-cc.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo2-v1.1.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo-core2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-pc2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-k1-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-m1-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-prime.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-zero-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-zero-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-3.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-lite2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-one-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-pine-h64.dtb + diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts b/arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts index 7793ebb5d..38f54fef4 100644 --- a/arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts @@ -43,6 +43,7 @@ /dts-v1/; #include "sun50i-a64.dtsi" +#include "sun50i-a64-cpu-opp.dtsi" #include <dt-bindings/gpio/gpio.h> @@ -108,6 +109,22 @@ status = "okay"; }; +&cpu0 { + cpu-supply = <&reg_dcdc2>; +}; + +&cpu1 { + cpu-supply = <&reg_dcdc2>; +}; + +&cpu2 { + cpu-supply = <&reg_dcdc2>; +}; + +&cpu3 { + cpu-supply = <&reg_dcdc2>; +}; + &dai { status = "okay"; }; diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-cpu-opp.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a64-cpu-opp.dtsi new file mode 100644 index 000000000..578c37490 --- /dev/null +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-cpu-opp.dtsi @@ -0,0 +1,75 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * Copyright (C) 2020 Vasily khoruzhick <anarsoul@gmail.com> + */ + +/ { + cpu0_opp_table: opp_table0 { + compatible = "operating-points-v2"; + opp-shared; + + opp-648000000 { + opp-hz = /bits/ 64 <648000000>; + opp-microvolt = <1040000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-816000000 { + opp-hz = /bits/ 64 <816000000>; + opp-microvolt = <1100000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-912000000 { + opp-hz = /bits/ 64 <912000000>; + opp-microvolt = <1120000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-960000000 { + opp-hz = /bits/ 64 <960000000>; + opp-microvolt = <1160000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-1008000000 { + opp-hz = /bits/ 64 <1008000000>; + opp-microvolt = <1200000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-1056000000 { + opp-hz = /bits/ 64 <1056000000>; + opp-microvolt = <1240000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-1104000000 { + opp-hz = /bits/ 64 <1104000000>; + opp-microvolt = <1260000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + + opp-1152000000 { + opp-hz = /bits/ 64 <1152000000>; + opp-microvolt = <1300000>; + clock-latency-ns = <244144>; /* 8 32k periods */ + }; + }; +}; + +&cpu0 { + operating-points-v2 = <&cpu0_opp_table>; +}; + +&cpu1 { + operating-points-v2 = <&cpu0_opp_table>; +}; + +&cpu2 { + operating-points-v2 = <&cpu0_opp_table>; +}; + +&cpu3 { + operating-points-v2 = <&cpu0_opp_table>; +}; diff --git a/drivers/net/wireless/Makefile b/drivers/net/wireless/Makefile index 11f80feba..9f5145cdf 100644 --- a/drivers/net/wireless/Makefile +++ b/drivers/net/wireless/Makefile @@ -4,7 +4,6 @@ # obj-$(CONFIG_WLAN_VENDOR_ADMTEK) += admtek/ -obj-$(CONFIG_RTL8189ES) += rtl8189es/ obj-$(CONFIG_WLAN_VENDOR_ATH) += ath/ obj-$(CONFIG_WLAN_VENDOR_ATMEL) += atmel/ obj-$(CONFIG_WLAN_VENDOR_BROADCOM) += broadcom/ @@ -14,7 +13,6 @@ obj-$(CONFIG_WLAN_VENDOR_INTERSIL) += intersil/ obj-$(CONFIG_WLAN_VENDOR_MARVELL) += marvell/ obj-$(CONFIG_WLAN_VENDOR_MEDIATEK) += mediatek/ obj-$(CONFIG_WLAN_VENDOR_RALINK) += ralink/ -obj-$(CONFIG_WLAN_VENDOR_REALTEK) += realtek/ obj-$(CONFIG_WLAN_VENDOR_RSI) += rsi/ obj-$(CONFIG_WLAN_VENDOR_ST) += st/ obj-$(CONFIG_WLAN_VENDOR_TI) += ti/ @@ -30,8 +28,6 @@ obj-$(CONFIG_USB_NET_RNDIS_WLAN) += rndis_wlan.o obj-$(CONFIG_MAC80211_HWSIM) += mac80211_hwsim.o obj-$(CONFIG_VIRT_WIFI) += virt_wifi.o -obj-$(CONFIG_RTL8812AU) += rtl8812au/ + obj-$(CONFIG_WLAN_VENDOR_XRADIO) += xradio/ -obj-$(CONFIG_RTL8821CU) += rtl8811cu/ -obj-$(CONFIG_RTL8188EU) += rtl8188eu/ -obj-$(CONFIG_RTL8822BU) += rtl88x2bu/ + diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c index 8ee8af4e7..127247759 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c @@ -5886,7 +5886,7 @@ static s32 wl_init_priv(struct brcmf_cfg80211_info *cfg) s32 err = 0; cfg->scan_request = NULL; - cfg->pwr_save = true; + cfg->pwr_save = !cfg->pub->settings->powersave_default_off; cfg->dongle_up = false; /* dongle is not up yet */ err = brcmf_init_priv_mem(cfg); if (err) @@ -6653,8 +6653,10 @@ static int brcmf_setup_wiphy(struct wiphy *wiphy, struct brcmf_if *ifp) BIT(NL80211_BSS_SELECT_ATTR_BAND_PREF) | BIT(NL80211_BSS_SELECT_ATTR_RSSI_ADJUST); - wiphy->flags |= WIPHY_FLAG_NETNS_OK | - WIPHY_FLAG_PS_ON_BY_DEFAULT | + if( ! ifp->drvr->settings->powersave_default_off ) + wiphy->flags |= WIPHY_FLAG_PS_ON_BY_DEFAULT; + wiphy->flags |= WIPHY_FLAG_OFFCHAN_TX | + WIPHY_FLAG_NETNS_OK | WIPHY_FLAG_HAVE_AP_SME | WIPHY_FLAG_OFFCHAN_TX | WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL; diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c index 96b8d5b3a..2a6c79d4a 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c @@ -85,6 +85,10 @@ module_param_named(ignore_probe_fail, brcmf_ignore_probe_fail, int, 0); MODULE_PARM_DESC(ignore_probe_fail, "always succeed probe for debugging"); #endif +static int brcmf_powersave_default = -1; +module_param_named(powersave_default, brcmf_powersave_default, int, 0); +MODULE_PARM_DESC(powersave_default, "Set powersave default on/off on wiphy"); + static struct brcmfmac_platform_data *brcmfmac_pdata; struct brcmf_mp_global_t brcmf_mp_global; @@ -458,6 +462,8 @@ struct brcmf_mp_device *brcmf_get_module_param(struct device *dev, brcmf_dmi_probe(settings, chip, chiprev); brcmf_of_probe(dev, bus_type, settings); } + if( brcmf_powersave_default >= 0 ) + settings->powersave_default_off = !brcmf_powersave_default; return settings; } diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h index 4ce56be90..8d276ab4d 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h @@ -58,6 +58,8 @@ struct brcmf_mp_device { bool roamoff; bool iapp; bool ignore_probe_fail; + bool powersave_default_off; + struct brcmfmac_pd_cc *country_codes; const char *board_type; union { diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c index 84e337328..27fcc25ed 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c @@ -47,6 +47,9 @@ void brcmf_of_probe(struct device *dev, enum brcmf_bus_type bus_type, if (of_property_read_u32(np, "brcm,drive-strength", &val) == 0) sdio->drive_strength = val; + settings->powersave_default_off = of_property_read_bool(np, + "brcm,powersave-default-off"); + /* make sure there are interrupts defined in the node */ if (!of_find_property(np, "interrupts", NULL)) diff --git a/sound/soc/sunxi/Makefile b/sound/soc/sunxi/Makefile index 555aa08f5..e8ebd59f6 100644 --- a/sound/soc/sunxi/Makefile +++ b/sound/soc/sunxi/Makefile @@ -1,8 +1,5 @@ # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_SND_SUN8I_CODEC_ANALOG) += sun8i-codec-analog.o -obj-$(CONFIG_SND_SUN4I_CODEC) += sun4i-codec.o -obj-$(CONFIG_SND_SUN4I_I2S) += sun4i-i2s.o -obj-$(CONFIG_SND_SUN4I_SPDIF) += sun4i-spdif.o obj-$(CONFIG_SND_SUN50I_CODEC_ANALOG) += sun50i-codec-analog.o obj-$(CONFIG_SND_SUN8I_CODEC) += sun8i-codec.o obj-$(CONFIG_SND_SUN8I_ADDA_PR_REGMAP) += sun8i-adda-pr-regmap.o The issue is as follows: 1. I cannot use legacy version (4.19) since the Wireless is not recognized + no hdmi disply. 2. I cannot use the current 5.4, dev 5.5.4, dev 5.5.5 version since there is an issue with the python GPIO + I cannot invert the HDMI screen, when I select to inverted the screen goes black. The only version that worked before was 5.1.15 but I do not able to create image with version of 5.1.21. Is there anyone that know how to address this? [0m[1;35m dpkg-genchanges --build=binary >../linux-5.1.21-sunxi64_20.05.0-trunk_arm64.changes [0mdpkg-genchanges: warning: package linux-image-5.1.21-sunxi64-dbg in control file but not in files list dpkg-genchanges: info: binary-only upload (no source code included)

I guess that I have had issues with the armbian build environment I guess that I have deleted some files that I shouldnt, anyway I have removed the old environment and build armbian again. First I have tried to compile version 5.5.4 to see that all goes well and no errors, after confirm that it succeed to finish without any failures I went back to try compiling the 5.1 version. With each failure of compilation I have modified the relevant MakeFiles and removed things that are not specially for relevant for the BPI-M64 board anyway and that caused the compilation to stop. I end up with this: iff --git a/arch/arm64/boot/dts/allwinner/Makefile b/arch/arm64/boot/dts/allwinner/Makefile index f670458ae..9e5672ff7 100644 --- a/arch/arm64/boot/dts/allwinner/Makefile +++ b/arch/arm64/boot/dts/allwinner/Makefile @@ -1,29 +1,4 @@ # SPDX-License-Identifier: GPL-2.0 -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-amarula-relic.dtb + dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-bananapi-m64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-nanopi-a64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-olinuxino.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-orangepi-win.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pine64-lts.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pine64-plus.dtb sun50i-a64-pine64.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-pinebook.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-sopine-baseboard.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-a64-teres-i.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-bananapi-m2-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-bananapi-m2-plus-v1.2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-emlid-neutis-n5-devboard.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-libretech-all-h3-cc.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo2-v1.1.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-neo-core2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-pc2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-k1-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-nanopi-m1-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-prime.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-zero-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h5-orangepi-zero-plus2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-3.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-lite2.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-orangepi-one-plus.dtb -dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h6-pine-h64.dtb + diff --git a/drivers/net/wireless/Makefile b/drivers/net/wireless/Makefile index 11f80feba..cdb79e00d 100644 --- a/drivers/net/wireless/Makefile +++ b/drivers/net/wireless/Makefile @@ -4,7 +4,6 @@ # obj-$(CONFIG_WLAN_VENDOR_ADMTEK) += admtek/ -obj-$(CONFIG_RTL8189ES) += rtl8189es/ obj-$(CONFIG_WLAN_VENDOR_ATH) += ath/ obj-$(CONFIG_WLAN_VENDOR_ATMEL) += atmel/ obj-$(CONFIG_WLAN_VENDOR_BROADCOM) += broadcom/ @@ -14,7 +13,6 @@ obj-$(CONFIG_WLAN_VENDOR_INTERSIL) += intersil/ obj-$(CONFIG_WLAN_VENDOR_MARVELL) += marvell/ obj-$(CONFIG_WLAN_VENDOR_MEDIATEK) += mediatek/ obj-$(CONFIG_WLAN_VENDOR_RALINK) += ralink/ -obj-$(CONFIG_WLAN_VENDOR_REALTEK) += realtek/ obj-$(CONFIG_WLAN_VENDOR_RSI) += rsi/ obj-$(CONFIG_WLAN_VENDOR_ST) += st/ obj-$(CONFIG_WLAN_VENDOR_TI) += ti/ @@ -30,8 +28,5 @@ obj-$(CONFIG_USB_NET_RNDIS_WLAN) += rndis_wlan.o obj-$(CONFIG_MAC80211_HWSIM) += mac80211_hwsim.o obj-$(CONFIG_VIRT_WIFI) += virt_wifi.o -obj-$(CONFIG_RTL8812AU) += rtl8812au/ obj-$(CONFIG_WLAN_VENDOR_XRADIO) += xradio/ -obj-$(CONFIG_RTL8821CU) += rtl8811cu/ -obj-$(CONFIG_RTL8188EU) += rtl8188eu/ -obj-$(CONFIG_RTL8822BU) += rtl88x2bu/ + diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile index d1b17ddcd..5eee1d0b5 100644 --- a/drivers/staging/Makefile +++ b/drivers/staging/Makefile @@ -5,12 +5,6 @@ obj-y += media/ obj-$(CONFIG_PRISM2_USB) += wlan-ng/ obj-$(CONFIG_COMEDI) += comedi/ obj-$(CONFIG_FB_OLPC_DCON) += olpc_dcon/ -obj-$(CONFIG_RTL8192U) += rtl8192u/ -obj-$(CONFIG_RTL8192E) += rtl8192e/ -obj-$(CONFIG_RTL8723BS) += rtl8723bs/ -obj-$(CONFIG_R8712U) += rtl8712/ -obj-$(CONFIG_R8188EU) += rtl8188eu/ -obj-$(CONFIG_R8822BE) += rtlwifi/ obj-$(CONFIG_RTS5208) += rts5208/ obj-$(CONFIG_NETLOGIC_XLR_NET) += netlogic/ obj-$(CONFIG_OCTEON_ETHERNET) += octeon/ And now I am facing another issue that I cannot find the fix for it: CC [M] drivers/usb/serial/usb_wwan.o CC [M] drivers/usb/serial/ssu100.o CC [M] drivers/usb/serial/symbolserial.o CC [M] drivers/usb/serial/ti_usb_3410_5052.o CC [M] drivers/usb/serial/upd78f0730.o CC [M] drivers/usb/serial/visor.o CC [M] drivers/usb/serial/wishbone-serial.o CC [M] drivers/usb/serial/whiteheat.o LD [M] drivers/usb/usbip/usbip-vudc.o CC [M] drivers/usb/serial/xsens_mt.o LD [M] drivers/usb/serial/usbserial.o AR drivers/usb/built-in.a AR drivers/built-in.a [ error ] ERROR in function compile_kernel [ compilation.sh:378 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated Also happens with the 5.2 version.

@nairn62 the solution in the post above yours is the easiest, and addresses the issue directly (xradio driver doesn't allow setting mac from user space) - iwd is still not quite ready

Users wanting to use debian builds with NetworkManager/wpa_supplicant should add the following lines to /etc/NetworkManager/NetworkManager.conf: [device] wifi.scan-rand-mac-address=no Ubuntu builds (bionic, focal) already contain these lines. This seems to solve the current issue on systems with the xradio wifi chip (opi zero, nanopi duo etc.)

Thanks, that turned out be a good place to look. On a hunch, I tried swapping out wpa_supplicant for iwd as the wifi daemon for NetworkManager, and that did the trick. apt install iwd systemctl disable wpa_supplicant echo -e "\n[device]\nwifi.backend=iwd\n" >> /etc/NetworkManager/NetworkManager.conf I may just stick with iwd, but the root cause is probably that the aging xradio driver is missing support for some ioctl and it may just be a matter of time until a future release of iwd will send that one too.

Is it possible that there have been some image changes that broke the XR819 wifi completely? The available images for download on the Armbian page (5.3 server, and 5.4 minimal) as well as a custom built "legacy" branch linux-4.19 image all show the same behavior, The wlan0 interface is not active and it's not possible to bring it up. And dmesg shows that module has been initialized but not much more. Armbianmonitor support info: 5.3.9 official buster server image: http://ix.io/240Y 4.19.88 self-built, two days ago, legacy branch: http://ix.io/240U Everything below is from the official image, but the 4.19 image shows the exact same It is definitely not a hardware issue, I have a SD card with a an older 4.19.72 image (when the branch was still called "next") that works just fine. ifconfig -a ifconfig root@orangepizero:~# ifconfig wlan0 up SIOCSIFFLAGS: Invalid argument root@orangepizero:~# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@orangepizero:~# journalctl -b | grep xradio Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Input buffers: 30 x 1632 bytes Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Firmware Label:XR_C01.08.0043 Jun 6 2016 20:41:04 Nov 19 08:08:28 orangepizero NetworkManager[1057]: <info> [1574150908.3204] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/soc/1c10000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver xradio_wlan) root@orangepizero:~# uname -a Linux orangepizero 5.3.9-sunxi #19.11.3 SMP Mon Nov 18 18:49:43 CET 2019 armv7l GNU/Linux

I'm connected to my Orange PI Zero over serial. I have a WiFi connection configured in NetworkManager on the Zero to my home AP/gateway, and it can connect to the internet over it. However: the Zero does NOT reply to ARP requests. I have tried running wireshark on multiple other machines on the same LAN, both wired and wireless, i have run tcpdump on the router, and none of them have EVER seen an ARP reply coming from the Zero. Obviously this means that no machine on the network can discover the MAC address of the Zero, and cannot connect to it... unless... the Zero first connects out. once the Zero has sent a packet to a machine, the machine will have the Zero's mac address in its ARP table and it doesn't require additional ARP requests to send IP packets, and, say, ssh connections to the Zero will work, but before that it's broken. --- edit: actuall, i don't think the Zero is even receiving the ARP requests correctly, even if i send them directly from the AP. I have tried running `tcpdump arp` on the Zero, and I don't see any incoming ARP queries. you may notice the incoming packet errors in the logs above: ```` [ 1134.223998] xradio_wlan mmc1:0001:1: [RX] IF=0, Receive failure: 4. [ 1134.224007] xradio_wlan mmc1:0001:1: dropped received frame ```` i'm reasonably sure these are related: increasing the incoming ARP query rate, or incoming ICMP packet rate corresponds to an increase in the xradio interrupt rate and the rate of these errors in the logs. i have logged a bug over here: https://github.com/Icenowy/xradio/issues/11, but i don't even know if the armbian devs track that, or even who is the best person to help track down this issue. anyone know?

Thanks for your help, but I tried to compile using the code and the configuration from the deb files you mentioned (not through git and those patches) in the last post and I've got an error: "drivers/net/wireless/xradio/sdio.c:17:10: fatal error: asm/mach-types.h: No such file or directory" what am I missing?

so, if you like to spend some time "to tame this tiger" you will become famous start here: https://forum.armbian.com/topic/3243-orange-pi-zero-wireless-module-status-xradio-st-cw1200/ may be then this one: https://forum.armbian.com/topic/10493-opi-zero-xradio_wlan-driver-kernel-hang/

Known problem - its written on the download page. The only way is a serious driver R&D. Do some search for "xradio opi zero wireless" and you will quickly get the picture.

Just a follow up After changing the driver software some places and testing, without any in-depth understanding about this chip, I was not able to stop kernel hang on X-radio wifi driver. I noticed problems with xradio in 2 modes. 1) When using xradio in AP mode: kernel hang, reboot -f does not work 2) Using xradio in concurrent mode: kernel hang In either cases AP mode had the problem. I decided to stop using the xradio for good after all the testing. I stopped xradio module loading from boot: commented out 'xradio_wlan' from /etc/modules file I blacklisted xradio driver by adding 'blacklist xradio_wlan' to /etc/modprobe.d/blacklist.conf file After that there were no kernel hangs or 'reboot -f' problems. I use an external wifi module now. I have tested about 8 wifi modules now and I will make another post with my results and experience of them. Cheers!

Thanks, @Tido for the links. [20149.090066] [<bfb2d42d>] (wsm_handle_rx [xradio_wlan]) from [<bfb29e05>] (xradio_bh_exchange+0x27c/0x588 [xradio_wlan]) In the error logs, it seems program stalled on wsm_handle_rx in xradio_wlan. I found the official xradio_wlan driver to be fifteenhex http://linux-sunxi.org/Wifi I checked the fifteenhex wlan_driver code for "wsm_handle_rx" and found this line in wsm.c https://github.com/fifteenhex/xradio/blob/master/wsm.c It seems like kernel hang is done on purpose. After commenting out this section, I recompiled the xradio_wlan.ko module driver and retested. After running 11 the OrangePi Zeros with the new xradio driver, connected to a router which changes its channel occasionally when multiple devices are connected, 5 OPis stop responding. I ran the test overnight. I tested after connecting all OPis through the serial port (COM). @zador.blood.stained @Tido @martinayotte any idea how I can further test the driver to stop the kernel hang? p.s: I am ok with the dropped packets of the driver. Thank You. Sanju.

If we can't attach this to poor drivers ... perhaps Network manager is having troubles/bugs and it would not be the first time. I will try to dig-in when possible ... do you wait for a while - how long - or wifi connection just drop? - after disconnecting the cable? At least this is known xradio driver problem.

OrangePi Zero wireless chip is known for its "quality" and there is little to be done - I am not sure anyone will do any more debugging on this chip/driver combo. Check forum for topics associated with xradio, xr819, opi zero wireless. I would primarily suggest using something else, different board or something on USB. Any other wireless chip is better.

IIRC this module is known to have a bad driver. Maybe you find some hints in this thread: https://forum.armbian.com/topic/8101-nanopi-duo-no-wifi-with-lastest-ubuntu/ Or you just use the search in right hand corner for: xradio or XR819

We are trying to install wifi driver for Xradio Xr-819 and also for D-Link Wifi Adapter in Mainline Image of Orange Pi PC. We have tried for xradio by https://www.cnx-software.com/2016/11/10/allwinner-h2-linux-android-sdk-and-allwinner-xr819-wifi-driver-released/ and https://github.com/fifteenhex/xradio. Also, we have tried by installing u-boot https://notsyncing.net/?p=blog&amp;b=2016.orangepi-pc-custom-kernel. We have tried for D-Link by https://github.com/xk/rtl8812AU_rtl8821AU and http://www.philipzucker.com/getting-goddamn-wifi-on-the-goddamn-orange-pi-pc/. Also, we tried to made modifications in file /etc/network/interfaces but that file shows in Read Only Mode but nothing works out. Need help ASAP.