Search the Community

Thanks, this turned out to be much more involved than I expected. To save the next person some time, here's what it took: Activate the uart(s) and change stdout-path in the device tree, then add CONFIG_CONS_INDEX=3 (starts from 1) in configs/orangepi_zero_defconfig: diff --git a/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts b/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts index d166ffc0..abcc1874 100644 --- a/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts +++ b/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts @@ -56,13 +56,15 @@ aliases { serial0 = &uart0; + serial1 = &uart1; + serial2 = &uart2; /* ethernet0 is the H3 emac, defined in sun8i-h3.dtsi */ ethernet0 = &emac; ethernet1 = &xr819; }; chosen { - stdout-path = "serial0:115200n8"; + stdout-path = "serial2:115200n8"; }; leds { @@ -172,13 +174,13 @@ &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>; - status = "disabled"; + status = "okay"; }; &uart2 { pinctrl-names = "default"; pinctrl-0 = <&uart2_pins>; - status = "disabled"; + status = "okay"; }; &usb_otg { diff --git a/configs/orangepi_zero_defconfig b/configs/orangepi_zero_defconfig index ef0c6884..956f6a28 100644 --- a/configs/orangepi_zero_defconfig +++ b/configs/orangepi_zero_defconfig @@ -17,3 +17,4 @@ CONFIG_SUN8I_EMAC=y CONFIG_USB_EHCI_HCD=y CONFIG_USB_OHCI_HCD=y CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE=y +CONFIG_CONS_INDEX=3 \ No newline at end of file But CONFIG_CONS_INDEX is currently missing the pinmux code for uart1/uart2 in u-boot, so this also needs to be patched: diff --git a/arch/arm/include/asm/arch-sunxi/gpio.h b/arch/arm/include/asm/arch-sunxi/gpio.h index 40a3f845..e6048983 100644 --- a/arch/arm/include/asm/arch-sunxi/gpio.h +++ b/arch/arm/include/asm/arch-sunxi/gpio.h @@ -148,6 +148,7 @@ enum sunxi_gpio_number { #define SUN6I_GPA_SDC2 5 #define SUN6I_GPA_SDC3 4 #define SUN8I_H3_GPA_UART0 2 +#define SUN8I_H3_GPA_UART2 2 #define SUN4I_GPB_PWM 2 #define SUN4I_GPB_TWI0 2 @@ -188,6 +189,7 @@ enum sunxi_gpio_number { #define SUN8I_GPG_SDC1 2 #define SUN6I_GPG_TWI3 2 #define SUN5I_GPG_UART1 4 +#define SUN8I_H3_GPG_UART1 2 #define SUN6I_GPH_PWM 2 #define SUN8I_GPH_PWM 2 diff --git a/arch/arm/mach-sunxi/board.c b/arch/arm/mach-sunxi/board.c index effbd032..e022bee4 100644 --- a/arch/arm/mach-sunxi/board.c +++ b/arch/arm/mach-sunxi/board.c @@ -133,10 +133,18 @@ static int gpio_init(void) sunxi_gpio_set_cfgpin(SUNXI_GPG(3), SUN5I_GPG_UART1); sunxi_gpio_set_cfgpin(SUNXI_GPG(4), SUN5I_GPG_UART1); sunxi_gpio_set_pull(SUNXI_GPG(4), SUNXI_GPIO_PULL_UP); -#elif CONFIG_CONS_INDEX == 3 && defined(CONFIG_MACH_SUN8I) +#elif CONFIG_CONS_INDEX == 2 && defined(CONFIG_MACH_SUNXI_H3_H5) + sunxi_gpio_set_cfgpin(SUNXI_GPG(6), SUN8I_H3_GPG_UART1); + sunxi_gpio_set_cfgpin(SUNXI_GPG(7), SUN8I_H3_GPG_UART1); + sunxi_gpio_set_pull(SUNXI_GPG(7), SUNXI_GPIO_PULL_UP); +#elif CONFIG_CONS_INDEX == 3 && defined(CONFIG_MACH_SUN8I) && !defined(CONFIG_MACH_SUNXI_H3_H5) sunxi_gpio_set_cfgpin(SUNXI_GPB(0), SUN8I_GPB_UART2); sunxi_gpio_set_cfgpin(SUNXI_GPB(1), SUN8I_GPB_UART2); sunxi_gpio_set_pull(SUNXI_GPB(1), SUNXI_GPIO_PULL_UP); +#elif CONFIG_CONS_INDEX == 3 && defined(CONFIG_MACH_SUNXI_H3_H5) + sunxi_gpio_set_cfgpin(SUNXI_GPA(0), SUN8I_H3_GPA_UART2); + sunxi_gpio_set_cfgpin(SUNXI_GPA(1), SUN8I_H3_GPA_UART2); + sunxi_gpio_set_pull(SUNXI_GPA(1), SUNXI_GPIO_PULL_UP); #elif CONFIG_CONS_INDEX == 5 && defined(CONFIG_MACH_SUN8I) sunxi_gpio_set_cfgpin(SUNXI_GPL(2), SUN8I_GPL_R_UART); sunxi_gpio_set_cfgpin(SUNXI_GPL(3), SUN8I_GPL_R_UART); diff --git a/include/configs/sunxi-common.h b/include/configs/sunxi-common.h index 47ea1243..46866c5d 100644 --- a/include/configs/sunxi-common.h +++ b/include/configs/sunxi-common.h @@ -255,7 +255,7 @@ extern int soft_i2c_gpio_scl; #else #define OF_STDOUT_PATH "/soc@01c00000/serial@01c28000:115200" #endif -#elif CONFIG_CONS_INDEX == 2 && defined(CONFIG_MACH_SUN5I) +#elif CONFIG_CONS_INDEX == 2 && (defined(CONFIG_MACH_SUN5I) || defined(CONFIG_MACH_SUN8I)) #define OF_STDOUT_PATH "/soc@01c00000/serial@01c28400:115200" #elif CONFIG_CONS_INDEX == 3 && defined(CONFIG_MACH_SUN8I) #define OF_STDOUT_PATH "/soc@01c00000/serial@01c28800:115200" This will make U-Boot output to uart1/uart2, but the Linux kernel has a low level debug output (e.g. to write "uncompressing kernel...") which writes to uart0 and simply freezes if it hasn't been initialized by U-Boot. So you'll need to compile a custom kernel with (Kernel Hacking -> Low Level debug functions) turned off. Then the linux console can be moved the normal way, using a boot param: e.g. console=ttyS2,115200

The sticker on the PCB also says H3, also the XR819 is the companion WiFi chip from Allwinner... That's definitely an Allwinner chip, most probably an H3 with a minor possibility it is an H2+ (which is almost the same as H3)

@hexdump I think axp_dummy is really just that, dummy driver. However, at some point I saw that it may call to AR100 to do voltage switching instead, but I think that's not the case here. I'm really not specialist in DVFS, so I can't answer your questions regarding that. No, I didn't do much regarding PHY driver. I just researched the topic in kernel. AFAIK we will have big pain to get it mainlined. There is no other PHY in kernel which has similar initialization sequence. We'll see. These days I was focused on implementing "half DQ" support in H6 DRAM driver for Tanix TX6 mini. Why would someone use that in media center oriented box is beyond me. It brings (much?) lower memory bandwitdh. I guess they really wanted to lower the price of the box, because they also used XR819 wifi. But yes, I received my TX6. I'm trying to add support for it to LE, but in the process I broke all other already supported boards. It has something to do with GPU, frequency and voltage regulator. In the process I also found regressions in AXP805 mainline driver (I didn't send patches yet). P.S.: These days it's very hot here, so I'm a bit slow with all this stuff. Fortunately, next days will not be so hot.

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.

I tested it on OPi Zero (basically the same device) with u-boot master branch and it passed the loopback test. defconfig changes: diff --git a/configs/orangepi_zero_defconfig b/configs/orangepi_zero_defconfig index e5a4c1d9fc..39528026a6 100644 --- a/configs/orangepi_zero_defconfig +++ b/configs/orangepi_zero_defconfig @@ -9,10 +9,19 @@ CONFIG_DRAM_ODT_EN=y CONFIG_SPL_SPI_SUNXI=y CONFIG_NR_DRAM_BANKS=1 # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set +# CONFIG_USE_BOOTCOMMAND is not set CONFIG_CONSOLE_MUX=y # CONFIG_CMD_FLASH is not set +CONFIG_CMD_SF=y +CONFIG_CMD_SF_TEST=y +CONFIG_CMD_SPI=y CONFIG_DEFAULT_DEVICE_TREE="sun8i-h2-plus-orangepi-zero" +CONFIG_MTD=y +CONFIG_DM_SPI_FLASH=y CONFIG_SUN8I_EMAC=y -CONFIG_USB_OHCI_HCD=y +CONFIG_SPI=y +CONFIG_DM_SPI=y +CONFIG_SOFT_SPI=y CONFIG_USB_EHCI_HCD=y +CONFIG_USB_OHCI_HCD=y CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE=y DT changes: diff --git a/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts b/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts index 0bc031fe4c..40b078723d 100644 --- a/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts +++ b/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts @@ -59,6 +59,8 @@ /* ethernet0 is the H3 emac, defined in sun8i-h3.dtsi */ ethernet0 = &emac; ethernet1 = &xr819; + spi0 = &softspi0; + spi1 = &softspi1; }; chosen { @@ -89,6 +91,26 @@ gpio = <&pio 0 20 GPIO_ACTIVE_HIGH>; }; + softspi0: soft-spi0 { + compatible = "spi-gpio"; + status = "okay"; + gpio-sck = <&pio 2 2 0>; + gpio-mosi = <&pio 2 0 0>; + gpio-miso = <&pio 2 1 0>; + cs-gpios = <&pio 2 3 0>; + num-chipselects = <1>; + }; + + softspi1: soft-spi1 { + compatible = "spi-gpio"; + status = "okay"; + gpio-sck = <&pio 0 14 0>; + gpio-mosi = <&pio 0 15 0>; + gpio-miso = <&pio 0 16 0>; + cs-gpios = <&pio 0 13 0>; + num-chipselects = <1>; + }; + wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <&r_pio 0 7 GPIO_ACTIVE_LOW>; Partial console log: => echo loopback wire disconnected loopback wire disconnected => sspi 1:0 16 1234 0000 => echo loopback wire connected loopback wire connected => sspi 1:0 16 1234 1234 => dm tree Class Index Probed Driver Name ----------------------------------------------------------- root 0 [ + ] root_driver root_driver simple_bus 0 [ + ] generic_simple_bus |-- soc mmc 0 [ + ] sunxi_mmc | |-- mmc@1c0f000 blk 0 [ ] mmc_blk | | `-- mmc@1c0f000.blk mmc 1 [ + ] sunxi_mmc | |-- mmc@1c10000 blk 1 [ ] mmc_blk | | `-- mmc@1c10000.blk phy 0 [ + ] sun4i_usb_phy | |-- phy@1c19400 usb 0 [ + ] ehci_generic | |-- usb@1c1a000 usb_hub 0 [ + ] usb_hub | | `-- usb_hub usb 1 [ + ] ohci_generic | |-- usb@1c1a400 usb_hub 1 [ + ] usb_hub | | `-- usb_hub usb 2 [ + ] ehci_generic | |-- usb@1c1b000 usb_hub 2 [ + ] usb_hub | | `-- usb_hub usb 3 [ + ] ohci_generic | |-- usb@1c1b400 usb_hub 3 [ + ] usb_hub | | `-- usb_hub clk 0 [ + ] sun8i_h3_ccu | |-- clock@1c20000 reset 0 [ + ] sunxi_reset | | `-- reset gpio 0 [ + ] gpio_sunxi | |-- pinctrl@1c20800 gpio 1 [ + ] gpio_sunxi | | |-- PA gpio 2 [ + ] gpio_sunxi | | |-- PB gpio 3 [ + ] gpio_sunxi | | |-- PC gpio 4 [ + ] gpio_sunxi | | |-- PD gpio 5 [ + ] gpio_sunxi | | |-- PE gpio 6 [ + ] gpio_sunxi | | |-- PF gpio 7 [ + ] gpio_sunxi | | |-- PG gpio 8 [ + ] gpio_sunxi | | |-- PH gpio 9 [ + ] gpio_sunxi | | `-- PI eth 0 [ + ] eth_sun8i_emac | |-- ethernet@1c30000 serial 0 [ + ] ns16550_serial | |-- serial@1c28000 gpio 10 [ + ] gpio_sunxi | `-- pinctrl@1f02c00 gpio 11 [ + ] gpio_sunxi | `-- PL spi 0 [ + ] soft_spi |-- soft-spi0 spi_generi 0 [ + ] spi_generic_drv | `-- generic_0:0 spi 1 [ + ] soft_spi |-- soft-spi1 spi_generi 1 [ + ] spi_generic_drv | `-- generic_1:0 clk 1 [ + ] fixed_rate_clock |-- osc24M_clk clk 2 [ + ] fixed_rate_clock |-- osc32k_clk clk 3 [ ] fixed_rate_clock `-- internal-osc-clk =>

Hi Guys, today I've Updated from "Armbian_5.67_Nanopiduo_Debian_stretch_next_4.14.90" to Armbian_5.69_Nanopiduo_Debian_stretch_next_4.19.13" now I've the follwing problem on my nanopi duo. It has Wifi onboard (XR819), but after an Update to Kernel 4.19.13-sunxi. my wifi device was lost. Before the Update the wifi device was listet as wlan0. to avoid configuration errors i also reinstalled the system. It does not work with debian or ubuntu. If i roleback to an older kernel everything works great. uname -a Linux nanopiduo 4.19.13-sunxi #5.69 SMP Wed Jan 9 16:26:48 CET 2019 armv7l armv7l armv7l GNU/Linux ifconfig -a dummy0: flags=130<BROADCAST,NOARP> mtu 1500 ether fa:76:fc:15:3e:84 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 02:42:0f:94:b1:fc txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 37 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled Module Size Used by zstd 16384 4 evdev 20480 1 sun8i_codec_analog 24576 0 sun8i_adda_pr_regmap 16384 1 sun8i_codec_analog snd_soc_simple_card 16384 0 snd_soc_simple_card_utils 16384 1 snd_soc_simple_card sun4i_i2s 20480 0 snd_soc_core 106496 4 sun4i_i2s,sun8i_codec_analog,snd_soc_simple_card_utils,snd_soc_simple_card snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core sun4i_gpadc_iio 16384 0 snd_timer 24576 1 snd_pcm industrialio 49152 1 sun4i_gpadc_iio snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun8i_ths 16384 0 zram 20480 5 cpufreq_dt 16384 0 uio_pdrv_genirq 16384 0 gpio_keys 20480 0 thermal_sys 57344 3 cpufreq_dt,sun8i_ths,sun4i_gpadc_iio uio 16384 1 uio_pdrv_genirq sch_fq_codel 20480 2 usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1 lima 40960 0 gpu_sched 20480 1 lima ttm 57344 1 lima dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.19.13-sunxi (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.69 SMP Wed Jan 9 16:26:48 CET 2019 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: FriendlyARM NanoPi DUO [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0x57c00000 [ 0.000000] On node 0 totalpages: 131072 [ 0.000000] Normal zone: 1152 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 131072 pages, LIFO batch:31 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: Using PSCI v0.1 Function IDs from DT [ 0.000000] random: get_random_bytes called from start_kernel+0x8d/0x3c2 with crng_init=0 [ 0.000000] percpu: Embedded 18 pages/cpu @(ptrval) s41484 r8192 d24052 u73728 [ 0.000000] pcpu-alloc: s41484 r8192 d24052 u73728 alloc=18*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129920 [ 0.000000] Kernel command line: root=UUID=4184603d-f069-41c2-95e2-68f03fbdbdcc rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ab235005-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] allocated 524288 bytes of page_ext [ 0.000000] Memory: 365120K/524288K available (8192K kernel code, 896K rwdata, 2420K rodata, 1024K init, 316K bss, 28096K reserved, 131072K cma-reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xe0800000 - 0xff800000 ( 496 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf800000 - 0xbfe00000 ( 6 MB) .text : 0x(ptrval) - 0x(ptrval) (9184 kB) .init : 0x(ptrval) - 0x(ptrval) (1024 kB) .data : 0x(ptrval) - 0x(ptrval) ( 897 kB) .bss : 0x(ptrval) - 0x(ptrval) ( 317 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 36585 entries in 72 pages [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000011] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000026] Switching to timer-based delay loop, resolution 41ns [ 0.000347] Console: colour dummy device 80x30 [ 0.000434] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.000455] pid_max: default: 32768 minimum: 301 [ 0.000919] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000935] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.002452] CPU: Testing write buffer coherency: ok [ 0.003214] CPU0: update cpu_capacity 1024 [ 0.003227] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.004266] Setting up static identity map for 0x40100000 - 0x40100054 [ 0.004548] rcu: Hierarchical SRCU implementation. [ 0.005946] smp: Bringing up secondary CPUs ... [ 0.017179] CPU1: update cpu_capacity 1024 [ 0.017192] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.028574] CPU2: update cpu_capacity 1024 [ 0.028585] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.039866] CPU3: update cpu_capacity 1024 [ 0.039877] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.040049] smp: Brought up 1 node, 4 CPUs [ 0.040063] SMP: Total of 4 processors activated (192.00 BogoMIPS). [ 0.040071] CPU: All CPU(s) started in HYP mode. [ 0.040076] CPU: Virtualization extensions available. [ 0.042073] devtmpfs: initialized [ 0.054859] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 [ 0.055247] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.055276] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.064378] xor: measuring software checksum speed [ 0.103945] arm4regs : 598.000 MB/sec [ 0.144054] 8regs : 356.000 MB/sec [ 0.184188] 32regs : 365.000 MB/sec [ 0.224308] neon : 605.000 MB/sec [ 0.224316] xor: using function: neon (605.000 MB/sec) [ 0.224430] pinctrl core: initialized pinctrl subsystem [ 0.226227] NET: Registered protocol family 16 [ 0.230623] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.231531] audit: initializing netlink subsys (disabled) [ 0.231895] audit: type=2000 audit(0.204:1): state=initialized audit_enabled=0 res=1 [ 0.232704] cpuidle: using governor ladder [ 0.232763] cpuidle: using governor menu [ 0.233766] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.233776] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.328896] raid6: int32x1 gen() 89 MB/s [ 0.397151] raid6: int32x1 xor() 76 MB/s [ 0.465276] raid6: int32x2 gen() 122 MB/s [ 0.533403] raid6: int32x2 xor() 94 MB/s [ 0.601559] raid6: int32x4 gen() 123 MB/s [ 0.670046] raid6: int32x4 xor() 92 MB/s [ 0.738275] raid6: int32x8 gen() 118 MB/s [ 0.806317] raid6: int32x8 xor() 82 MB/s [ 0.874403] raid6: neonx1 gen() 235 MB/s [ 0.942731] raid6: neonx1 xor() 219 MB/s [ 1.010959] raid6: neonx2 gen() 316 MB/s [ 1.079151] raid6: neonx2 xor() 283 MB/s [ 1.147283] raid6: neonx4 gen() 379 MB/s [ 1.215543] raid6: neonx4 xor() 318 MB/s [ 1.283811] raid6: neonx8 gen() 341 MB/s [ 1.351973] raid6: neonx8 xor() 288 MB/s [ 1.351981] raid6: using algorithm neonx4 gen() 379 MB/s [ 1.351987] raid6: .... xor() 318 MB/s, rmw enabled [ 1.351994] raid6: using neon recovery algorithm [ 1.354701] SCSI subsystem initialized [ 1.355059] libata version 3.00 loaded. [ 1.355427] usbcore: registered new interface driver usbfs [ 1.355505] usbcore: registered new interface driver hub [ 1.355622] usbcore: registered new device driver usb [ 1.355930] media: Linux media interface: v0.10 [ 1.356000] videodev: Linux video capture interface: v2.00 [ 1.356282] pps_core: LinuxPPS API ver. 1 registered [ 1.356291] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.356336] PTP clock support registered [ 1.358912] clocksource: Switched to clocksource arch_sys_counter [ 1.530605] VFS: Disk quotas dquot_6.6.0 [ 1.530771] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.546050] NET: Registered protocol family 2 [ 1.547394] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes) [ 1.547445] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 1.547542] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 1.547663] TCP: Hash tables configured (established 4096 bind 4096) [ 1.547852] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 1.547912] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 1.548244] NET: Registered protocol family 1 [ 1.549147] RPC: Registered named UNIX socket transport module. [ 1.549155] RPC: Registered udp transport module. [ 1.549162] RPC: Registered tcp transport module. [ 1.549169] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.549600] Trying to unpack rootfs image as initramfs... [ 2.486968] Freeing initrd memory: 7936K [ 2.490248] Initialise system trusted keyrings [ 2.490659] workingset: timestamp_bits=14 max_order=17 bucket_order=3 [ 2.502065] zbud: loaded [ 2.506251] NFS: Registering the id_resolver key type [ 2.506300] Key type id_resolver registered [ 2.506309] Key type id_legacy registered [ 2.506332] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.506340] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 2.508527] JFS: nTxBlock = 3938, nTxLock = 31508 [ 2.529389] Key type asymmetric registered [ 2.529406] Asymmetric key parser 'x509' registered [ 2.529551] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 2.529821] io scheduler noop registered [ 2.529830] io scheduler deadline registered [ 2.530169] io scheduler cfq registered (default) [ 2.530179] io scheduler mq-deadline registered [ 2.530187] io scheduler kyber registered [ 2.530448] io scheduler bfq registered [ 2.532647] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO [ 2.540272] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver [ 2.543274] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [ 2.640693] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [ 2.645020] console [ttyS0] disabled [ 2.665272] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 40, base_baud = 1500000) is a U6_16550A [ 2.665368] console [ttyS0] enabled [ 2.675671] brd: module loaded [ 2.686214] loop: module loaded [ 2.690382] libphy: Fixed MDIO Bus: probed [ 2.691425] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 2.691495] dwmac-sun8i 1c30000.ethernet: No regulator found [ 2.692119] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 2.692133] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 2.692146] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 2.692157] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 2.692169] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 2.692181] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 2.692434] libphy: stmmac: probed [ 2.693278] dwmac-sun8i 1c30000.ethernet: Found internal PHY node [ 2.693450] libphy: mdio_mux: probed [ 2.693486] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY [ 2.693501] dwmac-sun8i 1c30000.ethernet: Powering internal PHY [ 2.703199] libphy: mdio_mux: probed [ 2.704792] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.704802] ehci-platform: EHCI generic platform driver [ 2.705129] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.705180] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.706648] ehci-platform 1c1a000.usb: irq 27, io mem 0x01c1a000 [ 2.718931] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.719433] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.719449] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.719461] usb usb1: Product: EHCI Host Controller [ 2.719472] usb usb1: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.719483] usb usb1: SerialNumber: 1c1a000.usb [ 2.720468] hub 1-0:1.0: USB hub found [ 2.720554] hub 1-0:1.0: 1 port detected [ 2.721962] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.722003] ohci-platform: OHCI generic platform driver [ 2.722294] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.722349] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.722767] ohci-platform 1c1a400.usb: irq 28, io mem 0x01c1a400 [ 2.783385] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 2.783400] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.783412] usb usb2: Product: Generic Platform OHCI controller [ 2.783423] usb usb2: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 2.783434] usb usb2: SerialNumber: 1c1a400.usb [ 2.784329] hub 2-0:1.0: USB hub found [ 2.784416] hub 2-0:1.0: 1 port detected [ 2.786447] usbcore: registered new interface driver usb-storage [ 2.787803] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0 [ 2.787816] sun6i-rtc 1f00000.rtc: RTC enabled [ 2.788172] i2c /dev entries driver [ 2.790642] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0) [ 2.792091] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2 [ 2.793084] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.793531] ledtrig-cpu: registered to indicate activity on CPUs [ 2.793659] hidraw: raw HID events driver (C) Jiri Kosina [ 2.793865] usbcore: registered new interface driver usbhid [ 2.793871] usbhid: USB HID core driver [ 2.801500] Initializing XFRM netlink socket [ 2.802745] NET: Registered protocol family 10 [ 2.818694] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB [ 2.819496] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 2.819627] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 2.837401] Segment Routing with IPv6 [ 2.837586] NET: Registered protocol family 17 [ 2.837629] NET: Registered protocol family 15 [ 2.837729] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 2.837814] 8021q: 802.1Q VLAN Support v1.8 [ 2.837905] Key type dns_resolver registered [ 2.838710] Registering SWP/SWPB emulation handler [ 2.839859] registered taskstats version 1 [ 2.839868] Loading compiled-in X.509 certificates [ 2.840009] zswap: loaded using pool lzo/zbud [ 2.843651] Btrfs loaded, crc32c=crc32c-generic [ 2.855309] mmc0: host does not support reading read-only switch, assuming write-enable [ 2.858476] mmc0: new high speed SDHC card at address aaaa [ 2.859539] Key type encrypted registered [ 2.860784] mmcblk0: mmc0:aaaa SB32G 29.7 GiB [ 2.864517] mmcblk0: p1 [ 2.878655] ehci-platform 1c1c000.usb: EHCI Host Controller [ 2.878710] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 3 [ 2.879720] ehci-platform 1c1c000.usb: irq 29, io mem 0x01c1c000 [ 2.894919] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00 [ 2.895298] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.895313] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.895324] usb usb3: Product: EHCI Host Controller [ 2.895335] usb usb3: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.895346] usb usb3: SerialNumber: 1c1c000.usb [ 2.896329] hub 3-0:1.0: USB hub found [ 2.896406] hub 3-0:1.0: 1 port detected [ 2.897870] ehci-platform 1c1d000.usb: EHCI Host Controller [ 2.897917] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 4 [ 2.898375] ehci-platform 1c1d000.usb: irq 31, io mem 0x01c1d000 [ 2.910946] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00 [ 2.911294] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.911309] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.911320] usb usb4: Product: EHCI Host Controller [ 2.911332] usb usb4: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.911343] usb usb4: SerialNumber: 1c1d000.usb [ 2.912218] hub 4-0:1.0: USB hub found [ 2.912285] hub 4-0:1.0: 1 port detected [ 2.913620] ohci-platform 1c1c400.usb: Generic Platform OHCI controller [ 2.913676] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 5 [ 2.914052] ohci-platform 1c1c400.usb: irq 30, io mem 0x01c1c400 [ 2.975278] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 2.975293] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.975305] usb usb5: Product: Generic Platform OHCI controller [ 2.975316] usb usb5: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 2.975327] usb usb5: SerialNumber: 1c1c400.usb [ 2.976157] hub 5-0:1.0: USB hub found [ 2.976224] hub 5-0:1.0: 1 port detected [ 2.977540] ohci-platform 1c1d400.usb: Generic Platform OHCI controller [ 2.977582] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 6 [ 2.977963] ohci-platform 1c1d400.usb: irq 32, io mem 0x01c1d400 [ 3.039259] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 3.039274] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.039286] usb usb6: Product: Generic Platform OHCI controller [ 3.039297] usb usb6: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 3.039308] usb usb6: SerialNumber: 1c1d400.usb [ 3.040168] hub 6-0:1.0: USB hub found [ 3.040259] hub 6-0:1.0: 1 port detected [ 3.041681] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 3.041816] usb_phy_generic usb_phy_generic.0.auto: Linked as a consumer to regulator.0 [ 3.044310] of_cfs_init [ 3.044466] of_cfs_init: OK [ 3.044576] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 3.044677] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 3.044734] vcc3v0: disabling [ 3.044745] vcc5v0: disabling [ 3.044752] vcc-wifi: disabling [ 3.046216] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.4 [ 3.046327] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 3.055199] Freeing unused kernel memory: 1024K [ 3.067304] Run /init as init process [ 4.284456] lima 1c40000.gpu: bus rate = 200000000 [ 4.284475] lima 1c40000.gpu: mod rate = 384000000 [ 4.284965] [TTM] Zone kernel: Available graphics memory: 252576 kiB [ 4.284973] [TTM] Initializing pool allocator [ 4.286577] lima 1c40000.gpu: gp - mali400 version major 1 minor 1 [ 4.286705] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1 [ 4.286809] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1 [ 4.287015] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus [ 4.289174] [drm] Initialized lima 1.0.0 20170325 for 1c40000.gpu on minor 0 [ 4.292444] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 4.292654] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 4.295874] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.4 [ 4.296016] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 4.300760] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 4.300881] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 4.306747] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 4.471019] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB [ 4.484820] sunxi-mmc 1c10000.mmc: no support for card's volts [ 4.484839] mmc1: error -22 whilst initialising SDIO card [ 4.486595] sunxi-mmc 1c10000.mmc: no support for card's volts [ 4.486608] mmc1: error -22 whilst initialising MMC card [ 5.242439] random: fast init done [ 5.273173] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 5.945405] systemd[1]: System time before build time, advancing clock. [ 5.997248] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 5.998075] systemd[1]: Detected architecture arm. [ 6.038122] systemd[1]: Set hostname to <nanopiduo>. [ 6.734729] random: systemd: uninitialized urandom read (16 bytes read) [ 6.735374] systemd[1]: Started ntp-systemd-netif.path. [ 6.747246] random: systemd: uninitialized urandom read (16 bytes read) [ 6.747686] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 6.767131] random: systemd: uninitialized urandom read (16 bytes read) [ 6.768868] systemd[1]: Created slice User and Session Slice. [ 6.784709] systemd[1]: Created slice System Slice. [ 6.800025] systemd[1]: Listening on Journal Socket (/dev/log). [ 6.811597] systemd[1]: Listening on Syslog Socket. [ 6.823672] systemd[1]: Listening on udev Control Socket. [ 7.020660] g_serial gadget: Gadget Serial v2.4 [ 7.020679] g_serial gadget: g_serial ready [ 7.030098] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 7.717854] systemd-journald[247]: Received request to flush runtime journal from PID 1 [ 8.532121] zram: Added device: zram0 [ 8.536882] zram: Added device: zram1 [ 8.541498] zram: Added device: zram2 [ 8.542765] zram: Added device: zram3 [ 8.547628] zram: Added device: zram4 [ 8.551948] zram: Added device: zram5 [ 8.591819] cpu cpu0: Linked as a consumer to regulator.5 [ 8.591980] cpu cpu0: Dropping the link to regulator.5 [ 8.592404] cpu cpu0: Linked as a consumer to regulator.5 [ 8.594027] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594053] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000) [ 8.594221] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594235] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 8.594440] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594455] cpu cpu0: _opp_add: OPP not supported by regulators (1152000000) [ 8.594638] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594653] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 8.594801] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.594816] cpu cpu0: _opp_add: OPP not supported by regulators (1224000000) [ 8.595133] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.595152] cpu cpu0: _opp_add: OPP not supported by regulators (1248000000) [ 8.595310] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.595323] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 8.595519] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.595533] cpu cpu0: _opp_add: OPP not supported by regulators (1344000000) [ 8.595715] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.595728] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 8.660881] input: r_gpio_keys as /devices/platform/r_gpio_keys/input/input0 [ 8.686443] zram1: detected capacity change from 0 to 64659456 [ 8.893417] sun8i_ths 1c25000.thermal-sensor: no memory resources defined [ 8.893462] sun8i_ths: probe of 1c25000.thermal-sensor failed with error -22 [ 8.944511] thermal thermal_zone0: failed to read out thermal zone (-110) [ 9.795151] Adding 63140k swap on /dev/zram1. Priority:5 extents:1 across:63140k SSFS [ 9.809915] zram2: detected capacity change from 0 to 64659456 [ 10.853228] Adding 63140k swap on /dev/zram2. Priority:5 extents:1 across:63140k SSFS [ 10.856888] zram3: detected capacity change from 0 to 64659456 [ 11.153417] random: crng init done [ 11.153437] random: 7 urandom warning(s) missed due to ratelimiting [ 11.262534] Adding 63140k swap on /dev/zram3. Priority:5 extents:1 across:63140k SSFS [ 11.266098] zram4: detected capacity change from 0 to 64659456 [ 11.296137] Adding 63140k swap on /dev/zram4. Priority:5 extents:1 across:63140k SSFS [ 11.421362] zram0: detected capacity change from 0 to 52428800 [ 11.795961] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [ 14.546107] EXT4-fs (mmcblk0p1): resizing filesystem from 226304 to 7712800 blocks [ 26.674028] EXT4-fs (mmcblk0p1): resized to 3145728 blocks [ 37.360914] EXT4-fs (mmcblk0p1): resized to 5767168 blocks [ 45.342118] EXT4-fs (mmcblk0p1): resized filesystem to 7712800 [ 49.293013] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 49.297171] Generic PHY 0.1:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0.1:01, irq=POLL) [ 49.303114] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 49.303138] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 49.303151] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 49.304029] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

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

These solutions haven´t been working for me and I am getting increasingly more frustrated. Running an Orange Pi Zero with a MT7601U USB wireless adapter with device code 148f:760b and a Kingston 32GB sd card. In my attempts I have tried the following: - All four available distros available of Armbian; Xenial, Jessie, Bionic, and Stretch. With the older distros the MT7601U driver needs to be installed manually which creates all sorts of issues of its own. Wifi works out of the box with the latest distros, but also no internet. - All sorts of variations of /etc/resolv.conf, /etc/network/interfaces, setting nmtui manually, /etc/wpa_supplicant/wpa_supplicant.conf, proxy, and setting daily kernel updates were unsuccessful. Using the device now for Shairport-sync which works without the internet, but it seems a bit of a waste. Beating myself up for spending so much tome on a cheap device and network card although I really want to get it to work the way I intended to. I really do think that the issue is the network card as internet works using the xr819. Am I missing something?

which Parts are too different? it’s mainline-Kernel, i’ve added features by merges, which you can also use to integrate in your Kernel… from the BPi forum here: http://forum.banana-pi.org/t/bpi-r2-new-image-armbian-with-kernel-4-19-y-2018-11-5-support-by-armbian/7193/17 I won't respond in the BPi Forum. My time is currently very limited and don't follow all forums related to the SBCs I use. Yes we could patch in all the nice stuff you did, or even use your kernel tree for the BPi R2. But either we rely on an out of tree kernel (yours) or we've to heavily patch mainline with all the patches you applied. The first could be an option but during development I decided to not go that way. The second would mean that we've to adjust this patches everytime they break during kernel bump to newer versions, something I'm not willing to to. Keep in mind, Armbian support for the R2 was quite a long time a one man show.. Nobody was interested in contribution therefore I could do whatever I thought would fit best.. Since my interest in HDMI is somehow non-existing at the moment.. I simply don't care if it works.. Similar to nand-sata install.. It wasn't of interest for me for a long time.. I recently thought let's give it a try and I 'wasted' the whole Sunday afternoon to get it working with a minimal adjustment to ensure it doesn't harm the >50 other boards Armbian supports (means for me - reading into how nand-sata-install basically works.. try a bunch of time to get it working, write a PR, just a side-note: without some hints I got back in may from Wolfgang and your wiki, this wouldn't ever happen. Collecting all the missing bits to get such stuff up is just painful thanks to both of you, things were a way easier... ). To keep my workload for the board in an acceptable range I tend to go for pure mainline. If mainline supports feature X, no problem to support it in Armbian (for the mt7623) as well. If mainline doesn't support it.. Well I wont spend much time trying to bring it up. Maintaining patches over time is time intensive.. @Igor and others do a lot of work for other SoCs to have features supported before they reach mainline.. For the R2 this wont happen. It's only one board in the MT7623 family.. So we (as Armbian) have to keep the support costs as low as possible, means everything which probably opens Pandora's box should be avoided. People tend to not understand that Mali != video acceleration. If HDMI and Mali is there people want KODI running.. I'm not willing to deal with questions like "why's KODI not working smooth on Armbian on the R2". Simply not. If people want KODI on it they should ask the KODI people. If people want HDMI on it, they should use your image or prepare a sane patch based on mainline for it. I won't do it. Similar for the onboard wifi.. I never touched it cause I personally didn't see an use-case for it. It just bloats more support questions in case this chip doesn't work reliable. We as Armbian don't have experience with the one soldered on this board. Igor packed it now but disabled it by default which is okay for me (at the moment), but in case support questions for it are overwhelming I'll take care that it gets wiped out from the buildscript cause I don't want to have a second XR819. The only chance I see to bring this board from csc to wip or fully supported in the future is to keep the maintenance costs as low as possible. So stick it to 'as clean as possible' vanilla LTS kernels which should not break and when time allows it I'll maintain a next branch with mainline (4.20 --> 5.0 etc.)... We try to reduce the workload for all the boards we support (see here: https://forum.armbian.com/topic/6281-board-support-general-discussion-project-aims/?do=findComment&amp;comment=63170 and follow ups). For a one board SoC I clearly prefer a mainline only approach to keep it maintainable. The main features are supported, and for the rest.. It's up to the user-base of this board to bring it up and test it. My 'job' is 'done' as soon as I can stick it to a proper upstream u-boot and the bootscript is fixed so that people can put their rootfs on something else than ext4 with nand-sata-install (which is currently broken for btrfs - at least when I tested it). The second gmac up would be a 'nice to have' a sane network config (everything under one bridge is probably not preferred by everyone) would be nice as well but not of high priority to me. I do in chemistry not computer science.. bringing up such stuff an testing it took me nuts and a bunch of reading/testing every-time.. For me this is definitively not a 'beginners SBC' so people using it with Armbian should either be experienced with such stuff so that they can fix things on their own or at least willing to learn (as I had to as well)... I wont write any step by step procedure do get things running for it.. If *joe random* needs such step by step procedures I suggest you go for a board which has a bigger community or use another Image where the creator is willing to give you such step-by-step procedures. My offer is a 'pure' vanilla kernel and an Armbian rootfs which supports most of the features provided for this board and thanks to Armbians buildscript you can create all needed updates on your own, so in the end you get a set of nice *.deb packages which allow to update your board(s) with dpkg -i *.deb and in case the board ever enters wip or supported you'll get those packages even on armbians apt server so that an apt update && apt upgrade will work. Kernel-support is quite mature but for whatever reason no other board-maker picked up the SoC. I think that's not a bad offer for a board which ended in a closed thread the first time it was discussed cause involved people were more focused on personal insults. Is it perfect? Indeed not.. It's no up to all users to make it better. You now get an Image which boots out of the box from SD-Card and also works on eMMC with a simple nand-sata-install call packed with a 'near to upstream' u-boot.. working armbianEnv.txt with working mPCI, USB and SATA and all blobs needed for it are prepacked with the Image. If you really need decent wifi, go for an mPCI based one (@Igor tested a few). If you need for whatever reason a display, IMO there are better boards for such use-cases. If you want to contribute: provide some real-world numbers what the network is capable to deliver. I simply don't have time and enough equipment to test it at the moment. Encrypted and not encrypted would be nice.. Or find a more sane approach for the overall network configuration: https://github.com/chwe17/build/tree/46665fc32f1ec0a4981a743fc259173c07383c04/packages/bsp/mt7623 there's your starting point..

XR819 is only found on OPiZero, not OPiPC which doesn't have any WiFi on board, unlike OPiPC+. I would rather suggest some cheap WiFi USB dongle which is already supported out-of-the-box, like RTL8188 or MT7601.

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.

for XR819? no idea, never used them.. with my el cheapo usb-wifi (2$ each from aliexpress - look for a chipset which is properly supported by linux) it doesn't really matter - only thing I get is sluggish shell when the link quality is bad (I normally don't ssh that often into those boards). Disable powersafe options sometimes help. For the XR819, just use search function from the board, there are some threads where people who dealt with the driver code explain in detail what's wrong with it.

others would just call it crap.. All my OPis have wifi over USB if I want that they work reliable.. it's likely that they crash over time.. Some have no issues (maybe router related no idea). Others like me just don't use XR819. That's why this sentence is present on the downloadpage: https://www.armbian.com/orange-pi-zero/

I think I read about problems with AP6212 too, isn't it? bluetooth is messes up, but people mostly don't care.. compared to xr819 it's a great enhancement. obviously you can't run at highest clockrates with such an hat, but quick and dirty prototyping is a way easier., and that's where this little guy shines, you don't need to cover the board if you plan to build a custom prototype? See why people like it? I know, I've all different sorts of ESP32s laying around.. some with lora, some with sdcards displays battery holder.. it saves you one node.. simple as that.. My orange pi in the lab is attached to the balance.. which has a crappy serial protocol which can easiest be handled with linux (indeed you could write a 'driver' for it micro-python as well, but why when somebody already did it for linux? and besides handling my balance it also collects all the data from my ESPs here and there.. I want a web-interface for my data.. and logs as well.. such stuff is a way easier with linux than with any ESP framework. Besides one syringe-pump, all those devices are 'passive' (I don't do any PID stuff cause I don't trust my programming skills to make such stuff failsave.. for PID I would probably go for a micro-controller with C++ again to ensure it doesn't hang at the wrong moment). So no, those two use-cases are not fully independent. Normally they came together. Data without visualization is garbage.. The reason I collect data is to visualize them (in 'real-time').. So that I can spend my time with doing something else and monitoring them from my computer instead of sitting next to my reactions and look the whole time to a boring thermometer. did you ever wrote logs to this SPI? I tried it, before I decided it's not worth my time dealing with it.. For sure my ESPs could do a way more that simple dumping data via mqtt, but it's a way more convenient to do it on linux. with a slightly difference that for most stuff I need, somebody wrote a python or c/c++ driver for linux.. so.. guess why I don't have the balance on an ESP? Somebody wrote a nice python interface for it.. Porting it to micro-python may be possible.. but why should I waste my time? the goal is to use it ASAP not to have the most lightweight solution which is able to do the job (whenever possible, but I'm pragmatic here.. it's not worth my time to port this module as long as I've solution which works out of the box). Monitoring interface for ESPs are possible.. but something like node-red just gives me what I want without even understanding how the whole framework works. Ideas where such a board could be cool: CAN bus on cars some archaic old lab analysis devices where you've a combination of RS232 and 0-12V analog output for controlling and the signal (back in those days you had to buy an 'integrator' which mostly was to expensive so people had plotters cut out the signals and weight the mass of the paper compared to the other signals - and that's not a joke I did this more than once for an crappy old device nobody had software for anymore... But you need RS232 for starting the measurement as well some sorts of fish-tank computers, you want data and visualization (and maybe also some sort of a warning system over mail, phone, messenger in case you can afford a dissolved oxygen probe) some sort of security camera with some relays to turn on lights or whatever.. with the right drivers probably a 3d printer as well? Maybe you've to tweak it to be RT but well.. why not?

if you go higher than 60$ anyway, then I would have a look into the RK3399 based ones. Towards 'evil inside'.. it depends on your needs, I assume once HW acceleration on RK3399 works properly they may even beat the Atoms on desktop.. For me desktop means >30 tabs in browser.. No 2GB ram desktop can deal with that.. 4GB ones maybe.. For my work I just had to deal with windows 7 again.. Seems they've a crappy OOM handling there.. The preview picture from the RPi thread @Igor posted is an 'industrial grade' board (or at least near to industrial grade). Question here.. do you need it? This guy sent a Odroid C2 2600m deep.. For sure not an 'industrial grade' board: an OPi Zero (with USB wifi, cause XR819 is crappy) together with a few ESPs currently manage a lot of monitoring stuff in my Lab - for sure not industrial grade, but they do what they're supposed to do. So, even a 10$ toy can do serious work.. RK3288/tinker is IMO outdated, performs probably not that bad for desktop scenarios due to 32bit with 2GB ram may be ok-ish. If desktop means some web-surfing and watching youtube.. I assume an android driven one may fit better, normally those SoCs are supposed to run android and hardware acceleration works there a way earlier than in Ubuntu/Debian.

doesn't need FEL, bootorder for H3 is SD-->NAND-->SPI if I've it right in mind.. The print-screens from the opi-zero image show clearly that he's booting armbians 2018 u-boot.. But without the 16GB 'ROM' the most interesting part of this board IMO disappears.. A 16GB eMMC 2GB RAM box with an acceptable wifi chips for 30 bucks in an nice looking case could be interesting. NAND and XR819 makes it rather uninteresting (at least for me)..

Gah - they did go with naked NAND - unexpected, but not surprised - Android AOSP can live with this... but getting to something beyond the ASOP is going to be a challenge - something tells me that this is an android box, straight up, and that's what it is going to run... At least with the NAND it's good flash - SpecTek is Micron... RAM - Lot of RAM chips there - which makes uBoot a bit interesting - 2Gbit*8 is 2GB... is Samsung running a special sale on them these days? WiFi - XR819 - boring to some, weird to others - nothing exciting.... BTW note the really neat Inverted-F antenna - STB boards do leave a bit of room to be inventive there - although this isn't too terribly clever - but it is cheap, and gives decent enough gain there - maybe unity even. FWIW, Wifi front end is a bit of a mess, so some loss there - more that most... Looking at the board power - LDO's actually look ok - cheap and good enough - I wouldn't expect more at this price point... UART - 3.3 is likely good there - follow the pins, and consider this is one of many boards, so everything should align there/// Thermal Solution - with more recent H3's, and community understanding with Android - it's likely good - older H3 boards and distros - Allwinner got a bit of a bad reputation... but is cost is an issue, they could have done like Beelink with the X2, and put a big check of iron there - but who knows, extruded heatsinks like this are probably cheap enough these days in Shenzen. Anyways - like I mentioned earlier - this is a hyper optimized board for cost, and sensitive to the current supply chain (note the RAM, they wouldn't do this unless it was cost-efficient) BTW - @chwe - it's an H3 - H2+ is H3 with the GPU/VPU disabled if I trust what I read - I'm not a native Chinese speaker... Anyways - it's up to others whether to support this board in Armbian - it's going to be specific work, and time/resources are tight.

aaaand.. you're likely wrong.. cause eMMC is normally packed BGA whereas NAND not.. the eMMC 'socket' is there. but they went for NAND.. Have fun find a u-boot which supports NAND and linux mainline also doesn't support it as far as I know.. Wifi is a boring XR819 which 'nobody really wants' RAM seems to be okay but bootscript somehow messes up.. Well dig into it and you'll find out what's wrong you see the 4 pins next IR? they're labeled GND, UTX, URX and 3V... likely that it's 3.3V check with a voltmeter and likely do be UART0... Then someone can have a look into a 'proper' bootlog.. not print-screens.. It's just easier to read..

OPi0's wifi chip XR819 is known to be crappy see: and also mentioned on the DL page.. I think a 'somehow' proper solution would be similar to this one: https://github.com/armbian/build/blob/b554f3d003dcad862ac27bd0eb74ee4381a6366b/lib/distributions.sh#L253-L259 e.g. tell NM that eth0 isn't his business anymore.. I'm not sure if it survives an upgrade. For bionic: just tell them that NM isn't your renderer anymore: https://github.com/armbian/build/blob/b554f3d003dcad862ac27bd0eb74ee4381a6366b/lib/distributions.sh#L334-L337 These are both workarounds not really solutions. Well, if you don't like NM, there's still networkd left for you..

That was the first thing to check. Now next thing to check if the DT is correctly including the xradio node : under the "mmc@1c10000"node, you should have something like : sdio_wifi@1 { reg = <0x1>; compatible = "xradio,xr819"; interrupt-parent = <0xc>; interrupts = <0x6 0xa 0x1>; interrupt-names = "host-wake"; phandle = <0x37>; }; Check also the presence of "wifi_pwrseq" node : wifi_pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <0x2e 0x0 0x7 0x1>; post-power-on-delay-ms = <0xc8>; phandle = <0xf>; }; (Note : the above values are from my OPiZero board, so on your NanoPiDuo it could be a bit different...) Check "dmesg | grep mmc" to see if something went wrong during power up of the wifi. Do you see some with "dmesg | grep -i SDIO" ? Does "cat /proc/device-tree/soc/mmc@1c10000/status" reports "okay" ?

@martinayotte OK, I have static eth0 config working with the Mini Shield and no more dynamically creating adapters on reboot. I still have the original issue of no wifi device. I assume I need to get the XR819 device working. It used to work fine in beta Linux nanopiduo 4.17.3-sunxi #28 SMP Sat Jun 30 21:45:31 UTC 2018 armv7l armv7l armv7l GNU/Linux which has xradio_wlan. Seems to be missing from stable mainline release (only /lib/modules/4.14.65-sunxi/kernel/drivers/net/wireless/xradio/xradio_wlan.ko is present). uname -a Linux nanopiduo 4.14.65-sunxi #12 SMP Tue Aug 21 10:46:54 CEST 2018 armv7l armv7l armv7l GNU/Linux lsmod Module Size Used by lz4 16384 20 lz4_compress 53248 1 lz4 zram 24576 5 sun8i_codec_analog 24576 0 snd_soc_core 118784 1 sun8i_codec_analog snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 2 snd_pcm_dmaengine,snd_soc_core snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun4i_gpadc_iio 16384 0 uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq sch_fq_codel 20480 2 usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1 uas 20480 0 sudo lshw -C network *-network description: Ethernet interface physical id: 7 logical name: eth0 serial: ee:ee:ee:ee:ee:ee size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=st_mac100 driverversion=Jan_2016 duplex=full ip=192.168.1.69 link=yes multicast=yes port=MII speed=100Mbit/s nano /etc/network/interfaces auto eth0 iface eth0 inet static address 192.168.1.69 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 Remove netplan, etc. systemctl stop networkd-dispatcher systemctl disable networkd-dispatcher systemctl mask networkd-dispatcher apt-get purge nplan netplan.io

Looking at your "dmesg" again, it seem to fail trying to access mmc1 SDIO, therefore the XR819 chip. I don't have a nano-duo, so, I can't verify if DT is in proper shape in 4.14.65-sunxi.

By comparing https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi-duo2.dts and https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h2-plus-nanopi-duo.dts the only real difference is replacing the crappy XR819 Wi-Fi with RTL8189 (the other change being H2+ being replaced by H3) NanoPi Hero also features RTL8189 Wi-Fi, is limited to Fast Ethernet and has an I2C accessible voltage regulator allowing the board to clock at up to 1368 MHz (at 1.4V VDD_CPUX): https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi-hero.dts Maybe @mindee is so kind to provide an early picture of the latter?

Xunlong seems to have learn from the XR819 mistake of OPiZero, so most other OPis have better WiFi. So, cheapest ? Take a look at all OPis on AliExpress ...

No ! OPiLite is using RTL8189 while OPiZero is using the crappy XR819 for which the driver probably won't support any mesh.