Search the Community

After de-compiling latest sun50i-h6-tanix-tx6.dtb it seems that entire wifi device at mmc@4021000 is removed/disabled in latest build. The wifi configuration was present in the device tree from old builds that works. Simply copying old dtb does not improve the situation and XR819 is still not detected.

hm... that's unexpected. I assumed XR819 comes only with lower specs TX6 (2G version).

There are 3 possibilities regarding wifi on TX6: - XR819 - wifi only - TX6 mini - RTL8822BS - presumably older TX6 - RTL8822CS - presumably newer TX6

The wifi on the TX6 equipped with the XRadio XR819 chipset is working fine with the (pretty old ;-) image Armbian_20.10_Arm-64_buster_current_5.9.0.img, but no longer with the recent image Armbian_21.11.0-trunk_Aw-h6-tv_bullseye_current_5.10.68.img. I tried to add the drivers to the new image but they are not taken into account (but I'm a newbie). I wonder if the problem is not simply in the dtb.

@balbes150thanks for your great work on the TV boxes and for sharing. I’m playing with different images you provided and TV boxes (for a project I’m working on). According to your advice I’m now testing your new images on the H6 TX6. It works well however with an old image the Wifi was working (XRadio XR819 chipset) but no longer with the new builds ? Do you know why ? And is there a way to overclock a bit those boxes (as a bit slower than the Amlogic based X96 Air or Max) ? I tried though the dtb but the change is ignored.

I recently received an MXQ H3 Android box running android 7.1. I want to install Armbian linux on it. Can someone please help me on installing armbian linux on it. CPU : AllWinner H3 Hardware : sun8iw7p1 Wifi : XR819 RAM : 1 GB ROM : 8 GB Photos https://drive.google.com/drive/folders/1BgkxY9rz-UrokI_1EQjW6bdIRjtczBUK?usp=sharing

Same issue here with MX10 Pro model B and the official latest Armbian TVBox image, only one usb working. Try with this image and all the four usb port work fine, even if XR819 internal wifi will not work anyway: https://yadi.sk/d/zaTis6kklxUhug

Here is early work for proper XR819 mainline support. Tests reports are welcome, to see if it is actually any better than vendor driver. I got reasonable speed using it and only problem I can see is that suspend doesn't work. Of course, developer tests rarely last more than a few minutes, so long term stability isn't known. Note, I extracted pretty recent FW binaries from H616 Android box, which should be better than old ones, in theory.

I've checked on my second OPi0 where I didn't upgrade firmware, so still previous version, and the issue is also present : [ 14.824376] xradio: XR819 device discovered [ 15.056442] xradio: hardware vers. 7.9 [ 15.056457] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003 [ 15.056460] xradio: Config USE_EXTENSIONS [ 40.809788] xradio TXRX-WRN: received frame has no key status [ 40.809802] xradio TXRX-WRN: dropped received frame [ 3653.654011] xradio WRN: BH: missed 4 consecutive interrupts! [ 5423.670767] xradio WRN: BH: missed 5 consecutive interrupts! [ 7584.760350] xradio WRN: BH: missed 6 consecutive interrupts! [ 9724.478792] xradio WRN: BH: missed 7 consecutive interrupts! [10080.291066] xradio WRN: BH: missed 8 consecutive interrupts! [10777.751448] xradio WRN: BH: missed 9 consecutive interrupts! [13480.647858] xradio WRN: BH: missed 10 consecutive interrupts! [18367.827745] xradio WRN: BH: missed 11 consecutive interrupts! [19237.530227] xradio WRN: BH: missed 12 consecutive interrupts! [20461.024844] xradio WRN: BH: missed 13 consecutive interrupts!

As far as I can tell nothing much changed - nothing negative and nothing positive (still 200ms ping). Did I actually install the new version or am I just an idiot? [ 10.021886] xradio: XR819 device discovered [ 10.181980] cfg80211: failed to load regulatory.db [ 10.257067] xradio: hardware vers. 7.9 [ 10.257082] xradio: firmware vers. 8 (WSM), build 5258, api 1060, cap 0x0003 [ 10.257086] xradio: Config USE_EXTENSIONS

If somebody has a chance to test new firmware blob for XR819 feedback would be appreciated Simply grab the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } fw_xr819.bin from the PR below, replace your current one and reboot. Check if Wi-Fi still works as expected or ideally even better. The file is located here: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } /usr/lib/firmware/xr819/ https://github.com/armbian/firmware/commit/aff348fa9eef0fcc97d4f2bb7304f0862baffc20 If in doubt create a backup of your current firmware bin.

For what its worth, I've been streaming a 320kbps internet radio station continuously on an Orange Pi Zero running Armbian Buster (kernel 5.8.5) for about a month and it literally never misses a beat. So my personal experience is that neither the XR819 hardware nor the driver version that Armbian is currently using in 5.8.5 are intrinsically flawed. It is for this reason I'd love to see support for the XR819 finally make it into mainline. I am planning to use Orange Pi Zero in a significant project, and the somewhat unresolved formal status of the XR819 driver is the only fly in what is otherwise the very satisfactory ointment that is the OPi0 platform. Peter

Congratulations and thanks to dbeinder (yoq) and fifteenhex for their patience and good work on the XR819 driver. What do we need to do to get the XR819 driver finally adopted into the mainline kernel? Excuse my ignorance, and if this is a naive question! I'm keen on using the Orange Pi Zero for a fairly substantial project. I had this from Xunlong about an alternative wifi chip with the same footprint: "We dont have plan to use alternative wifi chip for this model and have no idea on this. BR. Steven" I'd love to see the XR819 driver in mainline, to reward all this fantastic effort, and to improve confidence in the OPi0 LTS for our project. Any thoughts? Peter

Update of firmware package fixe the issue. Thanks dmesg log is OK iwlist show expectd API list [ 10.549012] xradio: XR819 device discovered [ 10.649993] cfg80211: failed to load regulatory.db [ 10.772539] xradio: hardware vers. 7.9 [ 10.772557] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003 [ 10.772560] xradio: Config USE_EXTENSIONS [ 10.781416] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

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 ]

armbian-firmware_20.08.14_all.deb 20-Oct-2020 22:04 6917020 armbian-firmware_20.08.15_all.deb 24-Oct-2020 21:01 1120 armbian-firmware_20.08.16_all.deb 24-Oct-2020 22:12 1120 https://armbian.systemonachip.net/apt/pool/main/a/armbian-firmware/ $ sudo dpkg -L armbian-firmware-full /. /lib /lib/firmware /lib/firmware/3com /lib/firmware/RTL8192E /lib/firmware/RTL8192SU /lib/firmware/acenic /lib/firmware/adaptec /lib/firmware/advansys /lib/firmware/amd /lib/firmware/ap6210 /lib/firmware/ap6212 /lib/firmware/ar3k /lib/firmware/ar3k/1020200 /lib/firmware/ar3k/1020201 /lib/firmware/ar3k/1020201coex /lib/firmware/ar3k/30000 /lib/firmware/ar3k/30101 /lib/firmware/ar3k/30101coex /lib/firmware/ath10k /lib/firmware/ath10k/QCA4019 /lib/firmware/ath10k/QCA4019/hw1.0 /lib/firmware/ath10k/QCA6174 /lib/firmware/ath10k/QCA6174/hw2.1 /lib/firmware/ath10k/QCA6174/hw3.0 /lib/firmware/ath10k/QCA9377 /lib/firmware/ath10k/QCA9377/hw1.0 /lib/firmware/ath10k/QCA9887 /lib/firmware/ath10k/QCA9887/hw1.0 /lib/firmware/ath10k/QCA9888 /lib/firmware/ath10k/QCA9888/hw2.0 /lib/firmware/ath10k/QCA988X /lib/firmware/ath10k/QCA988X/hw2.0 /lib/firmware/ath10k/QCA9984 /lib/firmware/ath10k/QCA9984/hw1.0 /lib/firmware/ath10k/QCA99X0 /lib/firmware/ath10k/QCA99X0/hw2.0 /lib/firmware/ath10k/WCN3990 /lib/firmware/ath10k/WCN3990/hw1.0 /lib/firmware/ath6k /lib/firmware/ath6k/AR6002 /lib/firmware/ath6k/AR6003 /lib/firmware/ath6k/AR6003/hw1.0 /lib/firmware/ath6k/AR6003/hw2.0 /lib/firmware/ath6k/AR6003/hw2.1.1 /lib/firmware/ath6k/AR6003.1 /lib/firmware/ath6k/AR6003.1/hw2.1.1 /lib/firmware/ath6k/AR6004 /lib/firmware/ath6k/AR6004/hw1.2 /lib/firmware/ath6k/AR6004/hw1.3 /lib/firmware/ath9k_htc /lib/firmware/atmel /lib/firmware/atusb /lib/firmware/av7110 /lib/firmware/bnx2 /lib/firmware/bnx2x /lib/firmware/brcm /lib/firmware/cadence /lib/firmware/carl9170fw /lib/firmware/carl9170fw/carlfw /lib/firmware/carl9170fw/carlfw/include /lib/firmware/carl9170fw/carlfw/src /lib/firmware/carl9170fw/carlfw/usb /lib/firmware/carl9170fw/config /lib/firmware/carl9170fw/extra /lib/firmware/carl9170fw/include /lib/firmware/carl9170fw/include/linux /lib/firmware/carl9170fw/include/shared /lib/firmware/carl9170fw/minifw /lib/firmware/carl9170fw/toolchain /lib/firmware/carl9170fw/tools /lib/firmware/carl9170fw/tools/carlu /lib/firmware/carl9170fw/tools/carlu/src /lib/firmware/carl9170fw/tools/include /lib/firmware/carl9170fw/tools/lib /lib/firmware/carl9170fw/tools/src /lib/firmware/cavium /lib/firmware/cis /lib/firmware/cis/src /lib/firmware/cpia2 /lib/firmware/cxgb3 /lib/firmware/cxgb4 /lib/firmware/cxgb4/configs /lib/firmware/cypress /lib/firmware/dabusb /lib/firmware/dpaa2 /lib/firmware/dpaa2/mc /lib/firmware/dsp56k /lib/firmware/e100 /lib/firmware/edgeport /lib/firmware/edid /lib/firmware/emi26 /lib/firmware/emi62 /lib/firmware/ene-ub6250 /lib/firmware/ess /lib/firmware/go7007 /lib/firmware/i915 /lib/firmware/imx /lib/firmware/imx/sdma /lib/firmware/imx/vpu /lib/firmware/inside-secure /lib/firmware/inside-secure/eip197_minifw /lib/firmware/intel /lib/firmware/intel/ice /lib/firmware/intel/ice/ddp /lib/firmware/intel/ice/ddp-comms /lib/firmware/isci /lib/firmware/kaweth /lib/firmware/keyspan /lib/firmware/keyspan_pda /lib/firmware/korg /lib/firmware/libertas /lib/firmware/liquidio /lib/firmware/mediatek /lib/firmware/mediatek/mt8173 /lib/firmware/mediatek/mt8183 /lib/firmware/mediatek/nvram /lib/firmware/mellanox /lib/firmware/meson /lib/firmware/meson/gx /lib/firmware/meson/gxbb /lib/firmware/meson/gxl /lib/firmware/meson/gxm /lib/firmware/meson/m8 /lib/firmware/meson/vdec /lib/firmware/microchip /lib/firmware/moxa /lib/firmware/mrvl /lib/firmware/mrvl/prestera /lib/firmware/mwl8k /lib/firmware/mwlwifi /lib/firmware/myricom /lib/firmware/netronome /lib/firmware/netronome/bpf /lib/firmware/netronome/flower /lib/firmware/netronome/nic /lib/firmware/netronome/nic-sriov /lib/firmware/ositech /lib/firmware/qca /lib/firmware/qcom /lib/firmware/qcom/sdm845 /lib/firmware/qcom/venus-1.8 /lib/firmware/qcom/venus-4.2 /lib/firmware/qcom/venus-5.2 /lib/firmware/qcom/venus-5.4 /lib/firmware/qed /lib/firmware/qlogic /lib/firmware/r128 /lib/firmware/rkwifi /lib/firmware/rkwifi/bcmdhd /lib/firmware/rockchip /lib/firmware/rsi /lib/firmware/rtl_bt /lib/firmware/rtl_nic /lib/firmware/rtlbt /lib/firmware/rtlwifi /lib/firmware/rtw88 /lib/firmware/sb16 /lib/firmware/sdma /lib/firmware/slicoss /lib/firmware/sun /lib/firmware/sxg /lib/firmware/tehuti /lib/firmware/ti-connectivity /lib/firmware/ti-keystone /lib/firmware/tigon /lib/firmware/ttusb-budget /lib/firmware/ueagle-atm /lib/firmware/usbdux /lib/firmware/vicam /lib/firmware/vpu /lib/firmware/vxge /lib/firmware/xr819 /lib/firmware/yam /lib/firmware/yamaha

Thanks for answer Igor .. I'm wrote my own script in python, moved to OPi Zero with poor XR819 .. Better OPi Zero Plus H5 with RTL8189FTV wifi module was burned ... and H5 board does notwork properly with WiringPO library at this moment .. see:

Hello Guys, I bought this box 2 years ago and practicaly never used. After home cleaning found it and fought "if it run Android, it can run any Linux". I alredy have RBpi B3+ and with this TV Box now I could have a small open source data center and practice with ngnx, MariaDB, Postgree, MySQL, NodeJS, PHP, Python etc. After research I found this web, and liked Armbian idea. Issues: 1. This box looks identical to MXQ-4K, however the image did not work. When I opened it, the procesor was Allwinner H3, PCB is AK-H3-MXQ4K-V1.1 (https://wikidevi.wi-cat.ru/GUANZHI_Android_TV_BOX_H3) 2. I have many SD/microSD (brand and non brand), however only Lexmark 8Gb SD worked, even same brand but with 16Gb did not worked. 3. I try many armbian images for Allwinner H2/H3, but only worked Orange pi PC image 4. WiFi does not work, it is XR819 chip. It is not important at this stage, since LAN work 5. Not possible to copy and boot from internal NAND/eMMC, only from SD card Everything else looks to be OK (LAN, HDMI, USBs) If some body can advise how to copy armbian to internal flash, will be good, since armbian-config does not show option. I guess there is some copy block and need to use UART port. Regards,

Hi, I'm having some instability issues with WiFi driver on Orange Pi Zero Plus, it uses RTL8189FTV instead of buggy XR819 chip. Some times it just works fine, but that's not always the case, some times when I turn on the board the driver is not able to turn on the WiFi chip, and it keeps stuck in a limbo state... The kernel identify the network device as (wlan0), but it's impossible to turn on or connect to any network. sudo dmesg | grep -Ei '(8192eu|rtl|wl|realtek)' [ 236.057560] RTL871X: Failed to init Power On! [ 236.057567] RTL871X: rtw_hal_init: hal__init fail [ 236.057573] RTL871X: -ips_netdrv_open - drv_open failure, bup=1 [ 236.057579] RTL871X: <=== rtw_ips_pwr_up.............. in 4ms [ 236.057583] RTL871X: nolinked power save leave [ 236.057590] RTL871X: ==> ips_leave.....LED(0x00000000)... [ 236.057596] RTL871X: ======> ips_leave fail............. [ 299.062037] RTL871X: cfg80211_rtw_scan(wlan0) [ 299.062058] RTL871X: LeaveAllPowerSaveMode(wlan0): bSurpriseRemoved=_TRUE Skip! [ 299.062066] RTL871X: _rtw_pwr_wakeup call ips_leave.... [ 299.062076] RTL871X: ==>ips_leave cnts:7 [ 299.062080] RTL871X: ===> rtw_ips_pwr_up.............. [ 299.062099] RTL871X: ===> ips_netdrv_open......... [ 299.062111] RTL871X: FW does not exist before power on!! [ 299.062122] RTL871X: rtw_fw_ps_state: bSurpriseRemoved=True , hw_init_completed=0, bDriverStopped=False [ 299.062126] RTL871X: check fw_ps_state fail before PowerOn! [ 299.062145] RTL871X: PowerOnCheck: val_mix:0x00000000, res:0x00000000 [ 299.062150] RTL871X: PowerOnCheck: 0x100 the result of cmd52 and cmd53 is the same. [ 299.062159] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 1). [ 299.062165] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 2). [ 299.062171] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 3). [ 299.062177] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 4). [ 299.062183] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 5). [ 299.062189] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 6). [ 299.062195] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 7). [ 299.062201] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 8). [ 299.062207] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 9). [ 299.062214] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 10). [ 299.062221] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 11). [ 299.062227] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 12). [ 299.062233] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 13). [ 299.062240] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 14). [ 299.062246] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 15). [ 299.062252] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 16). [ 299.062259] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 17). [ 299.062265] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 18). [ 299.062271] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 19). [ 299.062277] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 20). [ 299.062283] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 21). [ 299.062290] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 22). [ 299.062296] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 23). [ 299.062302] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 24). [ 299.062309] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 25). [ 299.062315] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 26). [ 299.062321] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 27). [ 299.062327] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 28). [ 299.062333] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 29). [ 299.062339] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 30). [ 299.062346] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 31). [ 299.062352] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 32). [ 299.062358] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 33). [ 299.062365] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 34). [ 299.062371] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 35). [ 299.062377] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 36). [ 299.062383] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 37). [ 299.062390] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 38). [ 299.062396] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 39). [ 299.062402] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 40). [ 299.062409] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 41). [ 299.062415] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 42). [ 299.062421] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 43). [ 299.062427] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 44). [ 299.062433] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 45). [ 299.062440] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 46). [ 299.062446] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 47). [ 299.062452] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 48). [ 299.062458] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 49). [ 299.062465] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 50). [ 299.062471] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 51). [ 299.062477] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 52). [ 299.062483] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 53). [ 299.062490] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 54). [ 299.062496] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 55). [ 299.062502] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 56). [ 299.062508] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 57). [ 299.062515] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 58). [ 299.062521] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 59). [ 299.062527] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 60). [ 299.062533] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 61). [ 299.062539] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 62). [ 299.062546] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 63). [ 299.062552] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 64). [ 299.062558] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 65). [ 299.062564] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 66). [ 299.062571] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 67). [ 299.062576] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 68). [ 299.062582] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 69). [ 299.062588] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 70). [ 299.062595] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 71). [ 299.062601] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 72). [ 299.062607] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 73). [ 299.062613] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 74). [ 299.062620] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 75). [ 299.062626] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 76). [ 299.062632] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 77). [ 299.062638] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 78). [ 299.062644] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 79). [ 299.062651] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 80). [ 299.062657] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 81). [ 299.062663] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 82). [ 299.062669] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 83). [ 299.062675] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 84). [ 299.062681] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 85). [ 299.062687] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 86). [ 299.062693] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 87). [ 299.062699] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 88). [ 299.062705] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 89). [ 299.062711] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 90). [ 299.062717] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 91). [ 299.062723] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 92). [ 299.062729] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 93). [ 299.062735] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 94). [ 299.062741] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 95). [ 299.062748] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 96). [ 299.062754] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 97). [ 299.062760] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 98). [ 299.062766] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 99). [ 299.062773] RTL871X: PowerOnCheck: 0x1B8 test Fail(index: 100). [ 299.062778] RTL871X: ERROR Dump MAC Page0 register: [ 299.063907] RTL871X: Power on Fail! do it again [ 299.063916] RTL871X: PowerOnCheck: val_mix:0x00000000, res:0x00000000 [ 299.063921] RTL871X: PowerOnCheck: 0x100 the result of cmd52 and cmd53 is the same. And it keep repeating those messages like forever on dmegs... Any clue of what is really going on here? If the problem is just the drivers, there are any alternative driver that simply works reliable ?

There's not a lot of them to choose from, to be honest. Dumping from live Android failed as there's no /dev/dtb. Tried dumping from Android recovery partition, but it didn't work. Extracted from Tanix official firmware didn't boot either. These two were much larger in size so extract-dtb script is probably not working exactly correct. One from LE booted but no wifi and no sound. I've updated the linux-sunxi page with bits of info on different version. The one you've linked is the older PCV v1.0, and it seems that most users should have v2.3, which can be populated with either XR819 or RTL8822.

I've updated the previous post with the back side photo. Eh, https://linux-sunxi.org/Tanix_TX6 doesn't mention AR6330. Mine, however, has XR819 which is listed on linux-sunxi as a chip for 3 and 2 GiB models, although mine is 4GiB Android info: Model TX6 Version 9 Kernel: 4.9.118 Build: p281-userdebug PPR1.181005.003 20190722-184354. Looks like Alice UX.

Your happiness is maybe because of his work: @yoq https://forum.armbian.com/topic/13807-improved-xr819-driver/

I think we do not have enough feedback yet if the XR819 with the new drivers is good enough to be considered stable. Needs to be watched over a longer period of time to see if it stays connected. /Offtopic: If you plan to play with Bullseye or Focal make sure to download a 20.05.2 image as the .1 images on ARMHF most likely broken due to initramfs issues.

I have some 20 Orange Pi Zero's around and I tried quite a few images, the last one was Devuan. I installed it two days ago and this morning I found it crashed. Anyway, I fear the the hardware is definitly unstable. I tried to limit the CPU freq, but no way. A reboot does not solve the issue, you really have to give it a power cycle (!) Some boards can run for months, other will crash after a few hours. I ordered some Raspberry Pi Zero-W now and I will replace these boards. And I have two Orange Pi PC boards (H3): same issue. Switching on the WiFi reduces the uptime a lot so I blacklisted the xr819 module on all boards. I just installed Armbian buster, just to see what happens before they end up in the trash bin. I definitively lost confiance in these boards. I have lost too much time with this crap. Sorry boys.

Armbian ships a different driver for XR819 since quite a while. No idea though how much this increases the stability of WiFi since I never used it. https://github.com/armbian/build/blob/5e7199f567c1fe9c5d9908968fd1614cbf294ee2/lib/compilation-prepare.sh#L252