XTL

I have several options for S905X2. Video in MPV up to 1080p works with SW normally. There are small artifacts in the browser at 1080p. Is no support for audio via HDMI (expected within the next month), you need to use a USB sound card. And no support built-in WiFi and BT (need to use USB). If you take, the version with 4 GB of RAM and 1000 LAN port (and I recommend proven models for which there will be support). If there is no hurry, you can wait until the fall, then go new RK, it is more interesting models.

Starting from version 19.11.4, armbian TV supports Tanix TX6 with Allwinner H6 processor, 3Gb RAM, USB 3.0, LAN 100Mb, mali T720.
Given that Panfrost has added support for the mali T720 (which is used in this model), it is a promising enough model to use.
There are already Libreelec and Armbian for this TV box model.  
 
+ Eachlink H6 (Allwinner H6)   Hurry up to buy these models before the sellers learned about this possibility and raised the price ....    
 
 
 

H96 Max X2 (with S905X2 cpu) 4GB Ram ad 32GB Emmc
 
I purchased this box thinking I was getting an X96 Max (the naming of all these different boxes is very confusing).  But it turns out that it works well with current builds of balbes150's Armbian.  It works with the meson-g12a-x96-max-rmii.dtb.  It works well installed to eMMC.  The wifi does not work, and I haven't tried bluetooth or hdmi audio.

Old Sunvell R69 just boot with proper microSD card (in my case boot directly with Toshiba Exceria but not but with Samsung or Sandisk).
I'm using images shared in Google Drive from this post 
Sunvell R69 with Allwinner H2+
Running ARMBIAN 5.67 with kernel 4.14.81 
from internal eMMC
HDMI at 1080p 24fps
Wi-Fi OK,
Ethernet OK
 

You are right. I extracted image on SD card and system booted normally (see photo below). Thank you.
Next problem is wired network (wifi works good).
There is log of errors:
Dec 09 10:45:37 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found Dec 09 10:45:37 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found Dec 09 10:45:37 rk3399 kernel: dwc3 ff500000.usb: Failed to get clk 'ref': -2 Dec 09 10:45:37 rk3399 kernel: gpio-keys gpio-keys: Unable to get irq number for GPIO 0, error -6 Dec 09 10:45:37 rk3399 kernel: debugfs: Directory 'ff800280.cec' with parent 'regmap' already present! Dec 09 10:45:38 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Dec 09 10:45:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1 Dec 09 10:45:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Dec 09 10:45:39 rk3399 dhclient[655]: send_packet: Network is down Dec 09 10:45:39 rk3399 dhclient[655]: dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface. Dec 09 10:45:39 rk3399 dhclient[655]: receive_packet failed on eth0: Network is down Dec 09 10:45:40 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Dec 09 10:45:41 rk3399 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 Dec 09 10:45:47 rk3399 dhclient[655]: send_packet: Network is down Dec 09 10:45:47 rk3399 dhclient[655]: dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface. Dec 09 10:45:49 rk3399 bluetoothd[829]: Sap driver initialization failed. Dec 09 10:45:49 rk3399 bluetoothd[829]: sap-server: Operation not permitted (1) Dec 09 10:45:50 rk3399 NetworkManager[846]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed Dec 09 10:45:50 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1 Dec 09 10:45:50 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)  

You can "thank" AML for this.

They broke the u-boot. They put a bunch of crap in it that works exclusively with their old and crappy 4.9 core. For the color to work correctly with the 5.4 kernel, you either need the old u-boot-2015 (from the firmware, before AML broke it) or use u-boot-2019 (removing u-boot-2015 completely).
 
 
Offtopic. The behavior of AML lately has been increasingly frustrating for me. They do not pay any attention to the development of support for their chips in the main core (this work is done by third-party developers). Instead of helping, their new patches create a bunch of problems for the main kernel. I am waiting for the release of new Rockchip chips (or other platform options other than AML), and I hope to completely switch to using them for my development (minimizing support for AML, limiting myself to the chip models I already have).

Did you try different dtb files?

Try this thread for more info.
 

I sometimes think that there should be some ... more obvious centralized ressource pointing to the various architectures, platforms and such.
Like a directory "images", and each architecture gets its own subthread ( allwinner A33 ; s905W ) there, and whenever an new installation directory is created ( like somebody swapping from yadisk to google drive, or somebody posting a new image on baidu ) a new posting is made. 
 
I admit I suck at using the search, for when I look for "s905w  .img" I get dozens of results, just none pointing to images for the s905w chipset.

For some usage, doing "cat /sys/kernel/debug/gpio" will reveal if pin is in use by kernel driver.
But for some other usage such as I2C/SPI, you need to inspect Legacy FEX or Mainline DT.
 

Latest kernels include experimental fbttf modules. I connect cheapest oled screen(128x64px) via SPI to orange pi pc.
Connections:
data - spi0 mosi (PC0 pin 19) clk - spi0 clk (PC2 pin 23) cs - spi0 cs (PC3 pin 24) d/c - PC7 (pin 18) vcc - 3.3v (pin 1) gnd - gnd (pin 6) dts overlay:
/* * adafruit13m-overlay.dts * * based on overlay for RPi https://github.com/kenrestivo/linux/blob/3d61a22b05cbf7ac2f6b620dcd45c2fb49fb9442/arch/arm/boot/dts/overlays/adafruit13m-overlay.dts */ /dts-v1/ /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/aliases"; __overlay__ { spi0 = "/soc/spi@01c68000"; }; }; fragment@1 { target = <&pio>; __overlay__ { adafruit13m_pins: adafruit13m_pins { allwinner,pins = "PC7"; allwinner,function = "gpio_out"; }; }; }; fragment@2 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status = "okay"; adafruit13m: adafruit13m@0{ compatible = "solomon,ssd1306"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&adafruit13m_pins>; spi-max-frequency = <6000000>; buswidth = <8>; fps = <20>; dc-gpios = <&pio 2 7 0>; #debug = <3>; rotate = <0>; }; }; }; __overrides__ { #speed = <&adafruit13m>,"spi-max-frequency:0"; #rotate = <&adafruit13m>,"rotate:0"; fps = <&adafruit13m>,"fps:0"; #debug = <&adafruit13m>,"debug:0"; }; }; build:
/usr/src/linux-headers-4.10.0-sun8i/scripts/dtc/dtc -@ -I dts -O dtb -o /boot/dtb-4.10.0-sun8i/overlay/adafruit13m-overlay.dtbo adafruit13m-overlay.dts
added to /boot/armbianEnv.txt:
overlays=adafruit13m-overlay #overlay loading extraargs=fbcon=map:1 #remove fbcon attachement 
after reboot new framebuffer device found (/dev/fb0 on my headless configuration)

Don't worry, mali driver is built as a module, so unless you load it, it won't eat any resources, except a bit of a SD card storage.

after some week of uninterrupted working i can say that 3 opizero are working perfectly! And for now is my favorite board  I'm just start to use it instead of the orangepiPC and raspberry  

This 300Mb/s vs. 150Mb/s is a marketing bullshit. All of these dongles are 802.11 b/g/n capable and actual efficiency depends only on chip used, in theory 802.11n data rates may go up to 600Mb/s. 8192eu may not be the worst one, but hey, it's 2016, no one should be forced to build kernel driver for a network card.

BTW: Had a short laugh: http://vpneveryone.ddns.net/vpn.blackbox/opi-ipsec-vpn-server.htm

It worked. It took some trial and error because I was missing something btrfs related, but here is a cleaned up version of my steps:


# If the kernel has btrfs as external module (turns out I did not need this step):
  #Insert a line to /etc/initramfs-tools/modules containing:  "btrfs"

  #make new uInitrd with btrfs module:
  mkinitramfs -c gzip -o ./initrd `uname -r`
  mkimage -C none -A arm -O linux -T ramdisk  -a 0 -e 0 -n initramfs -d ./initrd uInitrd
  rm -f ./initrd

# now insert SD into another device like a PC

# create a new btrfs partition for root

#create subvolume for root
  btrfs sub create @

#move everything in "/"  to @ except for /boot which remains ext4

# mkdir /boot on the NEW btrfs  root filesystem

# move everything from originalext4fs/boot on the OLD ext4 filesystem up one level to originalext4fs/

# from the root of the OLD ext4 ( originalext4fs/ )
  ln -s . boot

# use "btrfs filesystem show" or whatever to find the new uuid

# edit/update /boot/boot.cmd
  #change root=??? to root=UUID=YourNewBtrfsUUID
  #change to rootfstype=btrfs
  #add rootflags=subvol=@

# generate new boot.scr:
  apt-get install u-boot-tools  # if not installed already
  mkimage -C none -A arm -T script -d ./boot.cmd ./boot.scr

# edit fstab to look something like this:

  #old ext4 now /boot:
  /dev/mmcblk0p1 /boot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
  #new btrfs root :
  UUID=newuuid-for-btrfs / btrfs subvol=@,defaults,noatime,nodiratime 0 1
  # no change:
  tmpfs /tmp tmpfs defaults,nosuid 0 0
  /var/swap none swap sw 0 0


#reboot and see if you can do the happy dance like me!
 

[Ended]   Be active, creative, helpful and you can get a powerful board in return. First give away batch is starting 11.6.2016  
It's not often that you can work on a software project that actually brings joy and helps people. Armbian is one of those project. It is a system that helps one build a kernel or boot images for several ARM development boards. 
 
It's in common interest that we improve level of support and to relieve most active people. Our crew needs an upgrade:
we need more coders, kernel hackers, UX designers to find and solve problems. If you are one of them, join our forum, join project at Github. we need properly built, packed and supported desktop with major functions: video acceleration/fbturbo, libump, mali, etc. we need to put together much better documentation. We need to fine tune MkDocs documentation tools For those who are willing to claim a task or help others to understand "how do I do this in Armbian" we prepared a dozen of boards as a small reward. It's a Xunlong Orange PI+ 2E, which design was improved based on requests from our community. It's H3 based quad core with 2G RAM, 16G eMMC, Gigabit LAN, WIFI and 3x USB.     There might be just enough boards for everyone who are willing to do some public service work. Claim your projects at this topic and each weekend we will discuss and select up to 15 people who will get the board, starting with 11.6., ... until we run out of boards. One will be notified by email and expect an answer within 48 hours, if not, board goes to somebody else.   Boards were donated and will be sent directly from Xunlong Co., Shenzhen, China.     1st batch is going to: Kriston, lanefu, vlad59, martinayotte, jeanrhum, Gravelrash, xcasex, naibmra, Xer0, madilabs, wha, @lex, WereCatf   naibmra - Bulgaria - kernel testing, try hooking to kernelci.org, docs - mid July wha - USA - 50unattended-upgrades, issue #337 - June Kriston - USA - documentation rework - July, August Xer0 - Germany - media build - July, August lanefu - USA - issue tracking improvements between forum and github - 22 June, July madilabs - Martinique - Packaging for desktop video acceleration - June xcasex - Sweden - desktop packaging - July, August jeanrhum - France - documentation and debian packaging - July martinayotte - Canada - maintain/fix DTS entries for some devices such I2C/SPI/W1 - ASAP vlad59 - France - Nanopi M1 testing and documentation Gravelrash - UK - Prepare HOWTO's & package "armbian-gc2035-fswebcam package" - June   2nd batch is going to: dimag0g, R2D2_C3PO, miked, 0x0, sysitos, jmcneill    dimag0g - France -  Packaging of OpenGL wrapper library - end of July R2D2_C3PO - Germany - Improved SD-Card partitioning - end of August miked - Canada - build system recension - end of August 0x0 - Russian Federation - Redesign site and documentation WIP + add some changes to graphics in distro. - end of July sysitos - Germany - replace/rework ramlog for systemd - end of August jmcneill - Canada - (Armbian is helping porting Freebsd)    Users were notified and were requested to provide: project name, due date and their shipping address

I know this way is a bit odd for such simple case but yes.
 
1. When you click edit the whole source is forked to your account automatically
2. Now it's your copy which you can edit
3. When you are satisfied you can send a modified code back to me (create pull request) and I decide to merge it, propose changes, reject, ...
 
This is Github way. It's meant for code and then those steps become logical. 

Mastering Github is useful