Christos

The monitor as I said, has three inputs, HDMI, DVI-D and plain VGA. So I went and got a HDMI to DVI-D cable this morning and wanted to perform some tests. 1. First test, HDMI to DVI-D cable used, HDMI OPiONE output to monitor's DVI-D input, U-Boot SPL 2016.09.01-armbian (Nov 11 2016 - 16:59:49) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2016.09.01-armbian (Nov 11 2016 - 16:59:49 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 dvi console (overscan 0x0) dotclock: 148500kHz = 148500kHz: (24MHz * 99) / 8 / 2 HDMI PHY divider: 2 pixel_clk: 148500000 pixel_repeat: false x_res: 1920 y_res: 1080 hor_back_porch: 148 hor_front_porch: 88 hor_sync_time: 44 ver_back_porch: 36 ver_front_porch: 4 ver_sync_time: 5 hor_sync_polarity: true ver_sync_polarity: true b_interlace: false hdmi enabled In: serial Out: vga Err: vga Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 => => => Monitor does not complain about resolution in u-boot. After boot though, screen reports "DVI out of range" in any/all 1080 h3disp settings tested. 2. Second test, direct connection with HDMI to HDMI cable, the system cannot properly identify the monitor, yet it comes up, even at a non-prefered resolution so the monitor complains at u-boot (attachment DSC01463) After u-boot, in no h3disp setting managed to have any display output at all. the tty/uart gives U-Boot SPL 2016.09.01-armbian (Nov 11 2016 - 16:59:49) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2016.09.01-armbian (Nov 11 2016 - 16:59:49 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1024x768 dvi console (overscan 0x0) dotclock: 65000kHz = 65000kHz: (24MHz * 65) / 6 / 4 HDMI PHY divider: 4 pixel_clk: 65000000 pixel_repeat: false x_res: 1024 y_res: 768 hor_back_porch: 160 hor_front_porch: 24 hor_sync_time: 136 ver_back_porch: 29 ver_front_porch: 3 ver_sync_time: 6 hor_sync_polarity: false ver_sync_polarity: false b_interlace: false hdmi enabled In: serial Out: vga Err: vga Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 => => So, with HDMI to DVI-D conversion, the monitor got identified by u-boot and started at the prefered (max) resolution, no monitor complains. after u-boot, no 1080 setting from h3disp was succesfull, monitor in all reported 'out of range' used h3disp setting -m 36 and got a bit partial screen (attachment DSC01461) with HDMI to HDMI direct cable, the monitor could not be identified correctly by the u-boot, yet the monitor got started at a non-prefered resolution (attachment DSC01463) all h3disp settings used but in none got any output The results are strange at least.. @jernej If you would like me to have some testing here pls let me know.

@jernej Forgot to mention, that by testing it with an Armbian image 5.24 dated from 27/Oct the u-boot is not showin up and the screen remains blank during the whole boot process since power up. It does show up though with again an Armbian labeled 5.24 but done yesterday 10/Nov, whereas during only u-boot the screen comes alive.

@jernej is doing a great job no doubt about it. I am asking because this is a newly bought monitor (yesterday) and scratching my head if it is an issue with the monitor itself. Yet the screen comes alive at u-boot so it looks it works, (trying to eliminate possible causes).

@jernej Just now seen that the log mention a 'dvi' somewhere.. HDMI connected: Setting up a 1024x768 dvi console (overscan 0x0) Do you mean that the system 'thinks' I use a dvi converter? Because I dont!! lol

@jernej The monitor has three connection ports, HDMI, DVI and plain VGA, I use the HDMI with a cable directly, no converters. (I was about to go out today and see if I could get a HDMI <-> DVI converter and test if that works using the DVI port.. desperate move..) @Igor Now as I understand from your saying it is more likely that this is a bug right?

Ok, It seems that the problem is with HDMI monitor resolution. Is fixed 1920 x 1080, at 60 Hz Model, LG 22MP58VQ Probably not included in the h3disp utility. Tested all the 1080 resolutions but without result. So, it seems that I have to find a way to add this.. Now I do need some help here guys.. Based on this post here -> https://forum.armbian.com/index.php/topic/752-tutorial-h3disp-change-display-settings-on-h3-devices/?p=17751 I have to do some calcs and generate a patch. @Igor , just a bit more info on what exactly I need to do and what those numbers mean? (its not so clear at first read, I do know how to make a patch and add it to the build, done it already, but need to understand better the numbers involved here ) ?? --- a/drivers/video/sunxi/disp2/hdmi/aw/hdmi_bsp_sun8iw7.c +++ b/drivers/video/sunxi/disp2/hdmi/aw/hdmi_bsp_sun8iw7.c @@ -46,6 +46,31 @@ static struct para_tab ptbl[] = {{257 , 1 , 0, 96, 15, 10, 8, 2, 8, 0, 0, 0, 48, 176, 88, 112, 90, 1, 1 }}, {{258 , 1 , 0, 96, 15, 10, 8, 5, 8, 4, 0, 0, 160, 32, 88, 112, 90, 1, 1 }}, {{35 , 11 , 0, 0, 1, 3, 3, 0, 13, 0, 0, 208, 228, 80, 60, 208, 45, 0, 0 }}, + // vic dclk int mx vst my mhbw vfp mhfp +x hbw hfp hst +y vbw h polarity v polarity + {{6 , 1 , 1, 1, 5, 3, 0, 1, 4, 0, 0, 160, 20, 38, 124, 240, 22, 0, 0 }}, + {{21 , 11 , 1, 1, 5, 3, 1, 1, 2, 0, 0, 160, 32, 24, 126, 32, 24, 0, 0 }}, + {{2 , 11 , 0, 0, 2, 6, 1, 0, 9, 0, 0, 208, 138, 16, 62, 224, 45, 0, 0 }}, + {{17 , 11 , 0, 0, 2, 5, 2, 0, 5, 0, 0, 208, 144, 12, 64, 64, 49, 0, 0 }}, + {{19 , 4 , 0, 96, 5, 5, 2, 2, 5, 1, 0, 0, 188, 184, 40, 208, 30, 1, 1 }}, + {{4 , 4 , 0, 96, 5, 5, 2, 1, 5, 0, 0, 0, 114, 110, 40, 208, 30, 1, 1 }}, + {{20 , 4 , 0, 97, 7, 5, 4, 2, 2, 2, 0, 128, 208, 16, 44, 56, 22, 1, 1 }}, + {{5 , 4 , 0, 97, 7, 5, 4, 1, 2, 0, 0, 128, 24, 88, 44, 56, 22, 1, 1 }}, + {{31 , 2 , 0, 96, 7, 5, 4, 2, 4, 2, 0, 128, 208, 16, 44, 56, 45, 1, 1 }}, + {{16 , 2 , 0, 96, 7, 5, 4, 1, 4, 0, 0, 128, 24, 88, 44, 56, 45, 1, 1 }}, + {{32 , 4 , 0, 96, 7, 5, 4, 3, 4, 2, 0, 128, 62, 126, 44, 56, 45, 1, 1 }}, + {{33 , 4 , 0, 0, 7, 5, 4, 2, 4, 2, 0, 128, 208, 16, 44, 56, 45, 1, 1 }}, + {{34 , 4 , 0, 0, 7, 5, 4, 1, 4, 0, 0, 128, 24, 88, 44, 56, 45, 1, 1 }}, + {{160 , 2 , 0, 96, 7, 5, 8, 3, 4, 2, 0, 128, 62, 126, 44, 157, 45, 1, 1 }}, + {{147 , 2 , 0, 96, 5, 5, 5, 2, 5, 1, 0, 0, 188, 184, 40, 190, 30, 1, 1 }}, + {{132 , 2 , 0, 96, 5, 5, 5, 1, 5, 0, 0, 0, 114, 110, 40, 160, 30, 1, 1 }}, + {{257 , 1 , 0, 96, 15, 10, 8, 2, 8, 0, 0, 0, 48, 176, 88, 112, 90, 1, 1 }}, + {{258 , 1 , 0, 96, 15, 10, 8, 5, 8, 4, 0, 0, 160, 32, 88, 112, 90, 1, 1 }}, + {{35 , 11 , 0, 0, 1, 3, 3, 0, 13, 0, 0, 208, 228, 80, 60, 208, 45, 0, 0 }}, + {{36 , 4 , 0, 96, 4, 6, 3, 1, 3, 0, 0, 0, 64, 24, 136, 0, 32, 1, 1 }}, + {{37 , 4 , 0, 96, 5, 3, 4, 1, 1, 0, 0, 0, 152, 48, 112, 0, 42, 1, 1 }}, + {{38 , 4 , 0, 96, 5, 7, 3, 1, 3, 0, 0, 80, 176, 64, 112, 0, 32, 1, 1 }}, + {{39 , 4 , 0, 96, 5, 9, 3, 1, 18, 0, 1, 160, 216, 32, 152, 132, 37, 1, 1 }}, + {{40 , 4 , 0, 96, 6, 3, 4, 2, 1, 0, 0, 144, 64, 104, 184, 26, 44, 1, 1 }}, }; /Edit When I stop the U-Boot with keyboard, the monitor shows ok the U-Boot screen and any commands given there. It becames blank when U-Boot continues with normal boot.

Hi, So far was working with headless Armbian images. Now I need to attach an HDMI monitor to my OPi ONE. Generated a desktop Armbian 5.24 jessie kernel 3.4.113, attached the HDMI monitor and booted. I saw the inital seconds of U-Boot logging the discovery of the monitor and a few other things and then it went blank. I guess after some reading in the forum that there is no display manager included in the distro or is there some other problem? Is there some build option that we could include a manager (eg KDE/XFCE/etc) in the image generation proccess? Or if there is any guide that gives steps for adding a display manager in Armbian to a not-so-knowledgable-guy like me whould be great. Christos /Edit Got this in my tty/uart port U-Boot SPL 2016.09.01-armbian (Nov 11 2016 - 16:59:49) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2016.09.01-armbian (Nov 11 2016 - 16:59:49 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1024x768 dvi console (overscan 0x0) dotclock: 65000kHz = 65000kHz: (24MHz * 65) / 6 / 4 HDMI PHY divider: 4 pixel_clk: 65000000 pixel_repeat: false x_res: 1024 y_res: 768 hor_back_porch: 160 hor_front_porch: 24 hor_sync_time: 136 ver_back_porch: 29 ver_front_porch: 3 ver_sync_time: 6 hor_sync_polarity: false ver_sync_polarity: false b_interlace: false hdmi enabled In: serial Out: vga Err: vga Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2092 bytes read in 168 ms (11.7 KiB/s) ## Executing script at 43100000 Booting from SD 144 bytes read in 126 ms (1000 Bytes/s) 3138723 bytes read in 337 ms (8.9 MiB/s) 5080432 bytes read in 490 ms (9.9 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 35908 bytes read in 469 ms (74.2 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3138659 Bytes = 3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.25.2 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 140188/936560 files, 628618/3751668 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 8 (jessie)! Expecting device dev-ttyS0.device... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Created slice Root Slice. [ OK ] Created slice User and Session Slice. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on Journal Socket. [ OK ] Created slice System Slice. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice system-getty.slice. Starting Increase datagram queue length... Starting Restore / save the current clock... Starting Load Kernel Modules... Starting Create list of required static device nodes...rrent kernel... Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Starting LSB: Set keymap... [ OK ] Reached target Slices. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Started Increase datagram queue length. [ OK ] Started Restore / save the current clock. [ OK ] Started Load Kernel Modules. [ OK ] Started Create list of required static device nodes ...current kernel. [ OK ] Started LSB: Set keymap. [ OK ] Started udev Coldplug all Devices. Starting Create Static Device Nodes in /dev... Mounting FUSE Control File System... Starting Apply Kernel Variables... [ OK ] Listening on Syslog Socket. Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Mounted FUSE Control File System. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Apply Kernel Variables. Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. Starting Copy rules generated while the root was ro... Starting LSB: Tune IDE hard disks... Starting LSB: Set preliminary keymap... [ OK ] Started Copy rules generated while the root was ro. [ OK ] Started LSB: Tune IDE hard disks. [ OK ] Reached target Sound Card. [ OK ] Created slice system-ifup.slice. [ OK ] Found device /dev/ttyS0. [ OK ] Started LSB: Set preliminary keymap. Starting Remount Root and Kernel File Systems... [ OK ] Started Remount Root and Kernel File Systems. Activating swap /var/swap... Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Activated swap /var/swap. [ OK ] Mounted /tmp. [ OK ] Started Load/Save Random Seed. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... [ OK ] Reached target Remote File Systems. Starting Trigger Flushing of Journal to Persistent Storage... Starting LSB: Prepare console... Starting LSB: Raise network interfaces.... [ OK ] Reached target Swap. [ OK ] Started Create Volatile Files and Directories. [ OK ] Started LSB: Prepare console. [ OK ] Started Trigger Flushing of Journal to Persistent Storage. Starting LSB: Set console font and keymap... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started LSB: Raise network interfaces.. Starting ifup for eth0... [ OK ] Started ifup for eth0. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. [ OK ] Started LSB: Set console font and keymap. [ OK ] Reached target System Initialization. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Timers. Starting Restore Sound Card State... [ OK ] Reached target Basic System. Starting Entropy daemon using the HAVEGE algorithm... [ OK ] Started Entropy daemon using the HAVEGE algorithm. Starting Regular background program processing daemon... [ OK ] Started Regular background program processing daemon. Starting OpenBSD Secure Shell server... [ OK ] Started OpenBSD Secure Shell server. Starting Network Manager... Starting /etc/rc.local Compatibility... Starting Login Service... Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: Advanced IEEE 802.11 management daemon... Starting LSB: Start NTP daemon... Starting LSB: Start/stop sysstat's sadc... Starting LSB: Armbian gathering hardware information... Starting LSB: disk temperature monitoring daemon... Starting LSB: No Display Manager... Starting LSB: Starts LIRC daemon.... Starting D-Bus System Message Bus... [ OK ] Started D-Bus System Message Bus. Starting System Logging Service... Starting Permit User Sessions... [ OK ] Started System Logging Service. [ OK ] Started Restore Sound Card State. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started LSB: Start NTP daemon. [ OK ] Started LSB: Start/stop sysstat's sadc. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started LSB: No Display Manager. [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started Permit User Sessions. [ OK ] Started Login Service. Starting Authenticate and Authorize Users to Run Privileged Tasks... Starting LSB: set CPUFreq kernel parameters... Starting Serial Getty on ttyS0... [ OK ] Started Serial Getty on ttyS0. Starting Getty on tty1... [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. Stopping LSB: Starts LIRC daemon.... [ OK ] Stopped LSB: Starts LIRC daemon.. Starting LSB: Starts LIRC daemon.... [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... Debian GNU/Linux 8 orangepione ttyS0 orangepione login: root Password: Last login: Fri Nov 11 19:30:31 EET 2016 on ttyS0 Linux orangepione 3.4.113-rt143-sun8i #24 SMP PREEMPT RT Fri Nov 11 17:13:18 EET 2016 armv7l ___ ____ _ ___ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) / _ \ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | | | | '_ \ / _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | | |_| | | | | __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| \___/|_| |_|\___| |___/ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.113-rt143-sun8i System load: 0.57 Up time: 2 min Memory usage: 24 % of 490Mb IP: CPU temp: 35°C Usage of /: 16% of 15G root@orangepione:~# dm

@arox If you have something against a specific developer, I'm sure there are better ways to communicate with him rather than bashing him on other people's threads.. I'm here to ask for some assistance, please if you can, do so.

Tested on a OPi PCPlus desktop image I had since 27/Oct, yet pulseaudio is not present!!.. I will do a fresh new desktop build today and test it again.

Ok, thanks for the info! That explains quite a bit since I'm currently trying on a headless NanoPi NEO. Got a desktop with the OPi PCPlus so I'll give it a try there.

Looks ok here.

Hi, Got a latest Armbian jessie image 5.24 with kernel 3.4.113, and could not find pulseaudio in it. I thought it was already present. Is there any hint/guide for installation to OPi or FA H3 boards with Armbian? Christos

Thanks, got the picture allright. In the A53 arena, wich obviously looks it will be the way of things for the immediate future, definitively there is a lot of work that needs to be done..

Orange is advertising PC2 with "Lubuntu and android" on their sales page so I guess they have to give some sort of Linux SDK soon. At times like these I do see how useless is an OrangePi whatever board without a decent O.S. eg Armbian..

Hi, Are there any news on if Armbian will be on the new H5 64bit board? Orange released an Android SDK and an Android image but I guess everyone is waiting for a decent 64bit Debian. Since took the plunge and got into the H5 wagon ordering one, I looked at the released info and obviously there was nothing I could use myself.. So the question goes to the Armbian gurus, guys do you think that there could be an Armbian release for H5 this year? Christos

Thanks for the hints. I'm gona give it a try. To add, have also found this -> http://linux-sunxi.org/Qt5_For_Mali_Binaries but it looks really heavy, even considered the native one -> http://linux-sunxi.org/Qt5_For_Mali_Binaries#Native_compilation but still the mali thing is a bit confusing.. In any case it looks that Qt5 installation is not an easy task.. Christos

Hi, Have some H3 boards with the current Armbian level 5.24. Need though Qt5.. Is there any info on how to do this? How to install Qt5 in Armbian? (Might be too easy but for some reason I cannot find relevant info) Christos

nanopineo login: root Password: Last login: Tue Nov 8 13:30:15 EET 2016 on ttyS0 Linux nanopineo 3.4.113-rt143-sun8i #20 SMP PREEMPT RT Tue Nov 8 11:40:48 EET 2016 armv7l _ _ ____ _ _ _ | \ | | __ _ _ __ ___ | _ \(_) | \ | | ___ ___ | \| |/ _` | '_ \ / _ \| |_) | | | \| |/ _ \/ _ \ | |\ | (_| | | | | (_) | __/| | | |\ | __/ (_) | |_| \_|\__,_|_| |_|\___/|_| |_| |_| \_|\___|\___/ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.113-rt143-sun8i System load: 0.16 Up time: 17 min Memory usage: 10 % of 490Mb IP: CPU temp: 44°C Usage of /: 7% of 15G root@nanopineo:~# rt-tests-1.0/cyclictest -p 80 -t5 -n # /dev/cpu_dma_latency set to 0us policy: fifo: loadavg: 0.03 0.22 0.19 1/119 1750 T: 0 ( 1743) P:80 I:1000 C: 72501 Min: 33 Act: 55 Avg: 55 Max: 144 T: 1 ( 1744) P:80 I:1500 C: 48334 Min: 35 Act: 56 Avg: 57 Max: 178 T: 2 ( 1745) P:80 I:2000 C: 36250 Min: 34 Act: 46 Avg: 55 Max: 149 T: 3 ( 1746) P:80 I:2500 C: 29000 Min: 33 Act: 45 Avg: 59 Max: 156 T: 4 ( 1747) P:80 I:3000 C: 24166 Min: 39 Act: 47 Avg: 54 Max: 201

Dont think that you can go far with this bearing in mind that there is Trustzone enabled.

@lex At least I managed to get a full image generated from the info and repositories mentioned in the thread (artik7 though.. "./release.sh -c config/artik710.cfg -m"). I mean performed succesful compilation and generation of u-boot, kernel, rootfs and all of them combined in a image specifically for SD. The way is there in the driver developer's guide. But when booted did nothing, not even uboot prompt on M3's tty/uart port. Either way though that means the necessary components are there and just sit and waiting for some armbian-team guru ( @Igor , @tkaiser ) to come and see how this can be tailored for the M3 ..just sayin.. Christos

Is this something private/NDA or can it be dissiminated?

Yep, seen schematic too (lol rare for orange to give schematics fast, still wait for the OPiPC+..), mistakenly read somewhere that it is I2C though yes it is SPI, faster obviously but still I prefer eMMC when/if they will get it out.

Hopefully the guys in Armbian will give us some nice 64bit distro for the M3 soon. (+1 for beggars in Armbian for M3 crowd.. )

Think I'll wait for the Plus version, hopefully they'll give some eMMC soon. Flash addition is nice, but I2C is slow..