Search the Community

No difference even after upgrade. Ubuntu 16.04.3 LTS orangepizero ttyS0 orangepizero login: root Password: Last login: Fri Feb 2 07:41:04 IST 2018 on ttyS0 ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 3.4.113-sun8i System load: 0.91 0.60 0.24 Up time: 2 min Memory usage: 30 % of 494MB IP: 192.168.1.12 CPU temp: 41°C Usage of /: 59% of 3.2G [ 0 security updates available, 2 updates total: apt upgrade ] Last check: 2018-02-02 07:42 [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] /dev/mmcblk0p5 /media/root-rw/data ext4 rw,relatime,data=ordered 0 0 Warning: a reboot is needed to finish resizing the filesystem Please reboot the system as soon as possible root@orangepizero:~# rmmod xradio_wlan [ 322.130074] [WSM_WRN] Issue unjoin command(TX). [ 323.070700] [STA_WRN] !!! xradio_remove_interface: vif_id=0 [ 323.171445] xradio wlan power off [ 323.249236] [XRADIO] Remove SDIO card 1 root@orangepizero:~# root@orangepizero:~# root@orangepizero:~# root@orangepizero:~# date Fri Feb 2 07:48:35 IST 2018 root@orangepizero:~# [ OK ] Stopped target Graphical Interface. [ OK ] Stopped target Multi-User System. Stopping OpenBSD Secure Shell server... Stopping System Logging Service... Stopping Authenticate and Authorize Users to Run Privileged Tasks... Stopping LSB: Start NTP daemon... Stopping Unattended Upgrades Shutdown... [ OK ] Stopped target Sound Card. Stopping User Manager for UID 0... Stopping Session 2 of user root. ...

Actually I am facing issue - when my AP is OFF and I boot OPI Zero board boots and automatically shutdown and this cycle continues. If AP is ON then it connects with AP works perfectly and no automatic shutdown happens. To recreate scenario I just unloaded unloaded xradio_wlan module (rmmod xradio_wlan) and I could see the same behaviour that target reboots without doing anything else. My aim is to stop automatic shutdown/reboot when AP is off, so that connect to AP whenever it is switched on. But I am not able to find the reason why the target reboot if WiFi radio is down or configured WiFi AP is not available. One I know the reason I may try to find the workaround Please find the console log below. Ubuntu 16.04.1 LTS orangepizero ttyS0 orangepizero login: root Password: Last login: Thu Feb 1 17:15:00 IST 2018 on ttyS0 Error: Broken packages exist. ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN 5.25 stable Ubuntu 16.04.1 LTS 3.4.113-sun8i System load: 1.50 Up time: 1 min Memory usage: 29 % of 494Mb IP: 192.168.1.12 CPU temp: 32°C Usage of /: 66% of 3.2G /dev/mmcblk0p5 /media/root-rw/data ext4 rw,relatime,data=ordered 0 0 root@orangepizero:~# ifconfig eth0 Link encap:Ethernet HWaddr ee:87:90:c2:da:e5 inet6 addr: fe80::ec87:90ff:fec2:dae5/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:238 (238.0 B) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr dc:44:6d:e3:d0:72 inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::de44:6dff:fee3:d072/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:86 errors:0 dropped:0 overruns:0 frame:0 TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9894 (9.8 KB) TX bytes:6852 (6.8 KB) root@orangepizero:~# echo "Everything is fine and WiFi working without any issue" Everything is fine and WiFi working without any issue root@orangepizero:~# rmmod xradio_wlan [ 158.540068] [WSM_WRN] Issue unjoin command(TX). [ 159.470267] [STA_WRN] !!! xradio_remove_interface: vif_id=0 [ 159.560185] xradio wlan power off [ 159.629941] [XRADIO] Remove SDIO card 1 root@orangepizero:~# root@orangepizero:~# date Thu Feb 1 23:23:30 IST 2018 root@orangepizero:~# date Thu Feb 1 23:23:45 IST 2018 root@orangepizero:~# date Thu Feb 1 23:23:48 IST 2018 root@orangepizero:~# date Thu Feb 1 23:23:52 IST 2018 root@orangepizero:~# date Thu Feb 1 23:23:55 IST 2018 root@orangepizero:~# date Thu Feb 1 23:23:59 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:02 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:07 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:11 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:16 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:20 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:29 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:37 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:45 IST 2018 root@orangepizero:~# date Thu Feb 1 23:24:53 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:01 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:06 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:14 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:23 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:31 IST 2018 root@orangepizero:~# date Thu Feb 1 23:25:42 IST 2018 root@orangepizero:~# Stopping Session 1 of user root. Stopping User Manager for UID 0... [ OK ] Stopped target Graphical Interface. [ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Stopping Authenticate and Authorize Users to Run Privileged Tasks... [ OK ] Stopped target Multi-User System. Stopping LSB: Starts LIRC daemon.... Stopping LSB: Start/stop sysstat's sadc... Stopping System Logging Service... Stopping OpenBSD Secure Shell server... Stopping Regular background program processing daemon... Stopping LSB: Armbian gathering hardware information... Stopping LSB: Set sysfs variables from /etc/sysfs.conf... Stopping LSB: disk temperature monitoring daemon... [ OK ] Stopped target Login Prompts. Stopping LSB: Advanced IEEE 802.11 management daemon... Stopping Save/Restore Sound Card State... [ OK ] Stopped target Sound Card. Stopping RFID Reader Service... Stopping Serial Getty on ttyS0... [ OK ] Stopped target Timers. [ OK ] Stopped Daily apt activities. [ OK ] Stopped target System Time Synchronized. [ OK ] Stopped Daily Cleanup of Temporary Directories. [ OK ] Stopped Regular background program processing daemon. [ OK ] Stopped System Logging Service. [ OK ] Stopped OpenBSD Secure Shell server. [ OK ] Stopped Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Stopped RFID Reader Service. [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Stopped User Manager for UID 0. [ OK ] Stopped Session 1 of user root. [ OK ] Stopped LSB: Advanced IEEE 802.11 management daemon. [ OK ] Stopped Save/Restore Sound Card State. [ OK ] Stopped LSB: Armbian gathering hardware information. [ OK ] Stopped LSB: Starts LIRC daemon.. [ OK ] Stopped LSB: Start/stop sysstat's sadc. [ OK ] Stopped LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Stopped LSB: disk temperature monitoring daemon. [ OK ] Stopped User Manager for UID 0. Stopping LSB: set CPUFreq kernel parameters... [ OK ] Removed slice User Slice of root. Stopping Login Service... [ OK ] Removed slice system-serial\x2dgetty.slice. Stopping /etc/rc.local Compatibility... Stopping Permit User Sessions... Stopping Access Control Service... [ OK ] Stopped Login Service. [ OK ] Stopped /etc/rc.local Compatibility. [ OK ] Stopped Permit User Sessions. [ OK ] Stopped target Network is Online. [ OK ] Stopped Network Manager Wait Online. [ OK ] Stopped Access Control Service. [ OK ] Stopped LSB: set CPUFreq kernel parameters. Stopping LSB: Load kernel modules needed to enable cpufreq scaling... Stopping MySQL Community Server... [ OK ] Stopped LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Remote File Systems (Pre). [ OK ] Stopped MySQL Community Server. [ OK ] Stopped target Network. Stopping Network Manager... Stopping WPA supplicant... [ OK ] Stopped WPA supplicant. [ OK ] Stopped Network Manager. Stopping D-Bus System Message Bus... [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped target Basic System. [ OK ] Stopped target Sockets. [ OK ] Closed Syslog Socket. [ OK ] Stopped target Paths. [ OK ] Stopped Forward Password Requests to Wall Directory Watch. [ OK ] Stopped Dispatch Password Requests to Console Directory Watch. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Stopped target System Initialization. Stopping Entropy daemon using the HAVEGE algorithm... [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped target Swap. Deactivating swap /var/swap... Deactivating swap /media/root-rw/data/var/swapfile... [ OK ] Stopped target Encrypted Volumes. [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped target Local File Systems. Unmounting /var/log... Starting Unattended Upgrades Shutdown... Unmounting /var/log.hdd... Unmounting /run/user/0... Stopping Restore / save the current clock... [ OK ] Stopped Entropy daemon using the HAVEGE algorithm. [ OK ] Deactivated swap /var/swap. [ OK ] Deactivated swap /media/root-rw/data/var/swapfile. [ OK ] Unmounted /var/log. [ OK ] Unmounted /run/user/0. [ OK ] Stopped Restore / save the current clock. [FAILED] Failed unmounting /var/log.hdd. Unmounting /media/root-rw/data... Stopping Load/Save Random Seed... Unmounting /tmp... [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Stopped Load/Save Random Seed. [ OK ] Unmounted /tmp. [ OK ] Unmounted /media/root-rw/data. [ OK ] Reached target Unmount All Filesystems. [ OK ] Stopped target Local File Systems (Pre). [ OK ] Stopped Create Static Device Nodes in /dev. [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown.

Yesterday I ordered an Orange PI Zero Plus. I am planning to install the appropriate OMV Image. The SBC will be placed very close to the router/switch (FRITZ!Box). Thus, I am going to connect it via LAN and won't use Wi-Fi. With regards to the OPI0+ (H5) can I use the same command "(sleep 60 && echo 000 >/proc/driver/wifi-pm/power) &" to disable Wi-Fi, as for the predecessor OPI0? Enter this via console (e.g. PuTTY)? Sorry, the syntax appears a bit strange to me. If yes: how to embed this command into startup/reboot to keep Wi-Fi disabled in general? What staff must be removed from /etc/modules exactly (e.g. containing the string 'xradio' or 'wlan')? And how to remove (e.g. simply delete the relevant folders/subfolders)? As usual thanks in advance, and best regards, Joe

Yes, but I am afraid it is not much you can do. Try modern kernel or use the board with a decent wireless chip. It is virtually impossible to find worse than this one. Most of the people stopped wasting time on anything related to Orangepi zero xradio chip/driver. A long time ago and especially on the old EOL kernel.

Armbian is already based on stable Debian or Ubuntu - it uses upstream Debian/Ubuntu repositories with a custom package selection, additional userspace scripts, services and helpers, and a custom u-boot and kernel. So you can either install Armbian u-bot and kernel on top of a Debian image or start with an Armbian image and remove everything that you don't need. I'm pretty sure that this doesn't work that way - Debian/Ubuntu won't backport new hardware support to their stable kernel, and some hardware like Xradio wireless will not be supported at all.

Just thought I'd pop in and report that on my zero running the nightly stretch, the temp seems to have gone down a hell of a lot (when idle). It used to get quite toasty (58c+) idle but now it's much better & this is with the xradio enabled (I had it off before)! Well done guys!

After successfully having wlan0 in legacy kernel (with using 8189es and 8189fs) I did take a look at Armbian_5.34.171104_Orangepizero_Ubuntu_xenial_next_4.13.11 This 4.13.11 hasnt loaded xradio and did modprobe 8189fs fine: root@orangepizero:/rtl8189ES_linux# lsmod Module Size Used by 8189fs 802816 0 but there is no 8189es. So I couldnt test if the combination of 8189es and 8189fs does work for the next kernel and wlan0. So I did take a look at @y52s thread and did try to compile the module 8189es on the next kernel: armbian-config -> install kernel headers exit root@orangepizero:~# cd /usr/src/linux-headers-4.13.11-sunxi root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# make scripts CHK scripts/mod/devicetable-offsets.h root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# cd / root@orangepizero:~# git clone https://github.com/jwrdegoede/rtl8189ES_linux root@orangepizero:/usr/src/linux-headers-4.13.11-sunxi# cd /rtl8189ES_linux/ root@orangepizero:/rtl8189ES_linux# make ARCH=arm CROSS_COMPILE= -C /usr/src/linux-headers-4.13.11-sunxi M=/rtl8189ES_linux make: Entering directory '/usr/src/linux-headers-4.13.11-sunxi' Building modules, stage 2. MODPOST 0 modules make: Leaving directory '/usr/src/linux-headers-4.13.11-sunxi' But there is no module generated/compiled Iam wondering about only ONE line after the "make script" in the linux-header directory because at the other thread there was many more line output: root@orangepiplus:/usr/src/linux-headers-3.4.110-sun8i# make scripts CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash The next-kernel seems to produce less heat than the legacy kernel As information: root@orangepizero:/rtl8189ES_linux# armbianmonitor -u /var/log/armhwinfo.log has been uploaded to http://sprunge.us/LQbY

@tkaiser @the-ice @Ivan Voronov because my OrangePi R1 did arrive today I did download today the legacy xenial ubuntu and did a apt update/upgrade and cleared the 2 xradio entrys in /etc/modules: root@orangepirone:/etc# more modules #w1-sunxi #w1-gpio #w1-therm #sunxi-cir g_serial Also deleted the entry for xradio in /etc/modprobe.d/ = xradio_wlan.conf After a reboot the mod 8189es is loaded automatically (the OPi R1 did this already before) : root@orangepirone:~# lsmod Module Size Used by 8189es 1076034 0 pcf8591 3363 0 bmp085 3487 0 cdc_ether 3679 0 usbnet 14096 1 cdc_ether g_serial 27617 2 btrfs 712409 0 but no WiFi A short Google-search did tell me that : RTL8189ftv is corresponding to 8189fs.ko, while RTL8189etv isc orresponding to 8189es.ko (in https://de.scribd.com/document/356867489/OrangePi-Win-win-Plus-A64-User-Manual-v0-9-1 ) So the 8189es is WRONG for the RTL8189ftv on the OPi R1 Mainboard. A short test of "modprobe 8189fs": root@orangepirone:~# lsmod Module Size Used by 8189fs 1050451 0 8189es 1076034 0 pcf8591 3363 0 bmp085 3487 0 cdc_ether 3679 0 usbnet 14096 1 cdc_ether g_serial 27617 2 btrfs 712409 0 8189fs loaded successfully - AND some time before I did configure via nmtui a WiFi-Connection I did get instantly my wlan0 with the configured address in ifconfig root@orangepirone:~# ifconfig enxc0742bffe8ff Link encap:Ethernet HWaddr c0:74:2b:ff:e8:ff inet addr:192.168.6.151 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::c274:2bff:feff:e8ff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1301 errors:0 dropped:0 overruns:0 frame:0 TX packets:854 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:118959 (118.9 KB) TX bytes:133607 (133.6 KB) eth0 Link encap:Ethernet HWaddr e2:fc:56:2f:d5:dc UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:510 (510.0 B) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:76 errors:0 dropped:0 overruns:0 frame:0 TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6030 (6.0 KB) TX bytes:6030 (6.0 KB) wlan0 Link encap:Ethernet HWaddr 08:ea:40:7c:02:ad inet addr:192.168.6.101 Bcast:192.168.6.101 Mask:255.255.255.255 inet6 addr: fe80::aea:40ff:fe7c:2ad/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:654 errors:0 dropped:2 overruns:0 frame:0 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:107527 (107.5 KB) TX bytes:2689 (2.6 KB) root@orangepirone:~# iwconfig lo no wireless extensions. enxc0742bffe8ff no wireless extensions. wlan0 IEEE 802.11bgn ESSID:"My_SSID" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.462 GHz Access Point: C0:25:E9:44:71:68 Bit Rate:72.2 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-****-****-****-**** Security mode:open Power Management:off Link Quality=100/100 Signal level=71/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 eth0 no wireless extensions. but now I did try to unload 8189es via modprobe -r 8189es Did work, BUT then wlan0 disappears In this moment it looks like to me that 8189fs.ko will only work if 8189es.ko is loaded (which armbian did automatically). After reloading 8189es with modprobe 8189es wlan0 re-appears and is visible in ifconfig For Information about this installation: root@orangepirone:~# armbianmonitor -u /var/log/armhwinfo.log has been uploaded to http://sprunge.us/QLbe and a dmesg as attachment dmesg_OPi_R1.txt

@walt22/ @Larry Bankthere is a "community supported" armbian config for the NanoPi Duo now, supporting the Xradio WLAN chip - gives me 20-22Mbit/s over 1,5m. To build the kernel you have to specify the board in the compile command ("compile.sh BOARD=nanopi-duo") in the armbian dev environment.

Xradio is turned OFF in the kernel. Got the same issue root@orangepizero:~# modprobe 8189es modprobe: FATAL: Module 8189es not found in directory /lib/modules/4.13.9-sunxi Will check if it is available in the kernel config...

Funny thing about the SSH latency via WiFi: If I do play Internet Radio via mpg123 -v -@ /home/guido/absolut_128.m3u on the HDMI console using WiFi I can use SSH at puTTY with like no lantency - also via WiFi Seems like that when only my typeing is transmitted via WiFi - the XRadio would go in a like sleep mode between the chars

Hmm... there should be no need to execute scripts any more if you did the modifications above. According to dmesg output it already worked at startup and still loading the xradio_wlan module twice seems to be necessary. What about a quick check with 'nmtui-connect' to see whether Wi-Fi really works? And maybe even a quick iperf3 test to confirm that data can be transmitted? That would finally confirm fex settings so anyone interested in supporting this device long-term could then start to hack a .dts for the board suitable for mainline kernel (fairly easy when starting with the DT for OPi Zero and then adding the necessary node for eMMC/mmc2 and different pin mappings for XR819. It would also be a great idea to create a device page in linux-sunxi wiki similar to the one for Beelink X2 at least documenting Wi-Fi settings and DVFS situation (no voltage regulation and 1.2V VDD_CPUX) Maybe caused by the sound drivers? Usually crashes at shutdown are related to driver hassles. You could try to remove all the snd_* entries from /etc/modules so that only the two xradio lines remain.

I forgot to mention that of course contents of /etc/modules have to be adjusted prior to such tests (at least removing the xradio occurences there).

Hmm... let's stop. Too much waste of time. The contents of /etc/modules have to be checked (since dhd driver for Broadcom/Ampak seems to be loaded which is conflicting with xradio) and all the 'magic' needed to deal with this other TV box (Beelink X2) has to be moved out of the way (see armhwinfo for example -- different batches of X2 have different Wi-Fi modules so we had to add a few ugly hacks here and there but I fail to remember what we did exactly).

That one worked, imported the stuff into Armbian's build system and did then the usual modifications: https://github.com/armbian/build/commits/master So hopefully when you grab latest version of the fex file there you get Wi-Fi running after loading the xradio module. Some fex contents seemed to be weird (eg. PL06 as wake-up source) but when walking through the whole contents it became obvious that PL06 is not needed and the box does not implement voltage regulation. According to fex H2+ is fed with 1.2V all the time and max cpufreq therefore limited to 1008 MHz (reasonable choice). The thermal settings are funny since starting with 80°C and allowing to go up to as much as 115"C. On the other hand the throttling settings were 'typical Allwinner' so with the default Android you boot with 4 cores active and as soon as you do anything heavy one CPU core after the other gets killed. Those settings should be more sane now. Another problem: DRAM according to the Android fex is clocked with 576 MHz while the Beelink X2 image uses AFAIK 624 MHz already in u-boot. So in case instabilities occur a better base than an Armbian image for Beelink X2 might be one of the eMMC equipped H3 boards with single bank DRAM config (since those are clocking DRAM by default with 408 MHz). That's eg. NanoPi Air or Orange Pi Zero Plus 2 H3 (what a stupid name!)

Mainline linux uses a "device tree" data structure to represent specific properties of board hardware (such as wlan chips). Device tree files are usually part of the kernel building process - and at the moment there is no such file for the NanoPi Duo in the armbian kernel build environment (it would be called something like <sun8i-h2-plus-nanopi-duo.dts>). Alternatively there is a mechanism to adapt device tree entries for an existing kernel referred to as device tree overlays. An example for such an overlay explicitly for integrating an xradio wlan chip (for an orange pi zero) can be found at https://github.com/karabek/xradio/ (see file <xradio-mrk1.dts> in directory <dts>.

Thanks chwe for your comment. What I understood until now: - There is no dedicated Armbian for NanoPi Duo. - In case one use the Neo version, the XR819 WiFi driver must be installed manually. I have made an inquiry, but cannot interprete it: root@nanopineo:~# modinfo xradio_wlan filename: /lib/modules/4.13.5-sunxi/kernel/drivers/net/wireless/xradio/xradio_wlan.ko alias: xradio_core license: GPL description: XRadioTech WLAN driver core author: XRadioTech alias: sdio:c*v0020d2281* depends: mac80211,cfg80211 intree: Y name: xradio_wlan vermagic: 4.13.5-sunxi SMP mod_unload ARMv7 thumb2 p2v8 root@nanopineo:~# No hint on XR819. Regards Walter

@Igor quick fix (fix-xradio-interrupt.patch): diff --git a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts index 454408b..df356b5 100644 --- a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts +++ b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts @@ -49,6 +49,7 @@ #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> +#include <dt-bindings/pinctrl/sun4i-a10.h> / { model = "Xunlong Orange Pi Zero"; @@ -157,6 +158,10 @@ */ xr819: sdio_wifi@1 { reg = <1>; + compatible = "xradio,xr819"; + interrupt-parent = <&pio>; + interrupts = <6 10 IRQ_TYPE_EDGE_RISING>; + interrupt-names = "host-wake"; }; }; performance is back up to around 10 mbit/s ... (PCB rev 1.1).

There is now a working xradio/xr819 driver for the 4.11.12 and 4.11.5 kernels at https://github.com/karabek/xradio So when does this work back into the armbian "release management"?

My area is also very crowded - I haven't done the actual measurement but I would say I should be somewhere around your numbers. What does this test tell? That XRadio in typical condition simply sux but it's usable for sending small chunks of data on close distance. On both kernels. Don't have any 8192 2T2R around but 8812AU is 2T2R and its results were pretty decent. Of course, numbers should be different early in the morning ...

3.4.113 Xenial, Opi zero XR with stock antenna, AP at the same spot, but on crowded 2.4Ghz band Xradio with 4.13.4 RT5370 USB Atheros 9271 USB RTL8188CUS nano USB 8812AU with kernel 4.13.4 and on 2.4G After all, this comparison tells something ...

8812au ... and also anything that has Ralink RT5572 or RT3572. Those are not AC but are at least dual band up to 2T2R with good Linux support. I am working on to setup proper testing environment. The current problem is the other side. My router is just 10cm away and I will need to set up another AP. 2.4 band performance is pretty irrelevant in an urban area but our apartment condo has a lot of steel inside walls and it actually works quite well. Except Xradio I have 13 wireless adaptors in a dedicated USB3.0 hub and two more are on the way. The plan is to make some scripts and update the database compatibility/kernel properties. All this setup is early WIP.

If only any wifi were so simple... https://github.com/fifteenhex/xradio is an example of someone working on this. The readme excerpt below came from there: Also: The xr819 chip/firmware drops tons and tons of frames with FCS errors and this makes performance horrible at best. Most people have lost interest in having anything to do with the xr819 because of people being idiots and demanding that issues that are incredibly hard to fix without documentation be fixed because they spent $8 on a board and somehow people that got exactly zero of their $8 are responsible. Moral of the story: If you're going to post nasty things on the interwebs and demand people fix stuff because reasons at least have a bunch of packet dumps etc and have some idea about what you're talking about.

There were a lot of insanely stupid complaints about this but besides that there are/were also real issues like dropped frames and no way to cure this back then (due to lack of documentation and software). Since this NanoPi Duo image will run on every H2+/H3 board around I simply booted it and had a look. root@NanoPi-M1:/lib/firmware/xr819# ls -la -rw-r--r-- 1 root root 2308 Aug 29 06:37 boot_xr819.bin -rw-r--r-- 1 root root 975 Aug 29 06:37 device-xradio.mk -rw-r--r-- 1 root root 126416 Aug 29 06:37 fw_xr819.bin -rw-r--r-- 1 root root 744 Aug 29 06:37 sdd_xr819.bin root@NanoPi-M1:/lib/firmware/xr819# md5sum * 049abcb4768e92490f9fcafff114d1eb boot_xr819.bin 01a5e63ddf60e2a4af5b073cec783bb7 device-xradio.mk 7a313e6957e635d9c1cd0d6902739d14 fw_xr819.bin e5d4afaf1a8c24f79f6764c289f1102f sdd_xr819.bin That's at least no new firmware (contents identical as what ships with Armbian's firmware package). Let's look at the driver: root@NanoPi-M1:~# modinfo xradio_wlan filename: /lib/modules/4.11.2/extra/xradio_wlan.ko alias: xradio_core license: GPL description: XRadioTech WLAN driver core author: XRadioTech alias: sdio:c*v0020d2281* depends: vermagic: 4.11.2 SMP mod_unload ARMv7 p2v8 Interested OPi Zero users could simply give the nanopi-duo_ubuntu-core-xenial_4.11.2_20170829.img a try and on the other hand NanoPi Duo is that inexpensive that interested persons simply should order one and try it out themselve (reporting back of course).

MAC address should be set by u-boot first. In order to find network devices it looks for aliases named ethernetX (where X is a number) pointing to the network devices DT nodes. In the source DT an alias looks like this: https://github.com/megous/linux/blob/orange-pi-4.11/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts#L58 Regarding the wireless driver - no idea if it supports a fixed MAC address and what method should be used for it. Edit: the first OPi Zero uses the XRadio driver, not a Realtek one, and current mainline images don't have this driver at all in the kernel sources due to many issues with it) If you are using mainline kernel for production and it works good enough for you (even though I would not recommend it, especially for OPi Zero) - okay, fine, but please use apt-mark hold to freeze the kernel, DT and board support packages (or remove /etc/apt/sources.list.d/armbian.list) to minimize the chance of getting a 200 waterproof useless bricks broken by the upgrade.