Vasy

Memory chips are there though. Weird decision from manufacturer...

Thanks. I tried my luck also with OIBAF PPA but still no joy. All the best!

Hi balbes150 Thanks for the great work so far! I've deployed the actual image and the Panfrost video acceleration does not work. Turned on the glamor acceleration, glmark2 works. Libva and mesa in place, still vainfo complains about missing sun4i-drm driver. dmesg shows that something is there, but not sure how to make it work with VA. Any plans to add it soon? Thanks.

Thanks once again, I will research there. Have a great weekend and happy cooking new releases

The box itself is a weird no-name, but Antutu etc checked all specs as fine

Look on the Yandex share in the first post, familiarize yourself with the structure in there and also the instructions in the first post. You need to download both the xz file that you need, plus the TX6 uboot, I used the one from July. I used balenaEtcher to write the xz to the sdcard, then again balenaEtcher just for the uboot (since it places it in the boot area of the card). Then it booted on my Allwinner H6 box. Without writing the uboot on the card, it didn't work. The instructions do not emphasize this too much and I expected that I place uboot as a file in the boot folder (as for Amlogic for example). Wow this sounds bad. With the original Android, using a terminal I got the full amount of RAM when running the "free" command.

Your Tanix TX6 uboot worked with my weird "H10 play" H6 box, even installed and booted from eMMC. However, only 3 out of 4 GBytes of RAM are detected. I've added the "mem=4096M" parameter for kernel, does not seem to help. Is it a kernel or an u-boot problem? Are these u-boot files updated somewhere so I can check for a newer one? Thanks!

Bad bump, this is a dedicated Armbian forum and not a general Linux support. Google is your friend, trust your feelings and fare well

Thanks! Plot twist: I flashed the 1109 version and now it automagically boots past that point. balbes150 has definitely done some magic that now works Only 3 gigs of RAM out of 4 are detected, but will fiddle with the kernel parameters.

Interesting, the mmcblk devices are being detected, so there should be no reason for linux not to boot up Is there a parameter I can pass in extlinux.conf to make the bootup scripts more verbose?

Is btrfs needed in your release? If no, could you please remove it from initramfs? I have a nasty issue, the system hangs on boot on "Scanning for Btrfs filesystems" and just dies there.

Tried again to boot. Upon startup with reset button pressed, the status LED stays red and the device does not boot at all. Later edit: followed some guides on YT and burned again the u-boot to SD with balena etcher. Now it boots but stops at "Scanning for Btrfs filesystem". To dig further...

Thanks mate for helping here, I will try so. I will read the instructions again and do it by the numbers. Is eMMC boot also stable, or will I brick it if I write armbian there? I always aim for eMMC since read/write speeds are way faster than SD.

Did anyone manage to boot Armbian on H10 Play (Allwinner H6) box? I tried via USB and SD-Card with reset button pressed and it doesn't work...

Thanks again, all the best!