SimonHayterUK

Hi Balbes150, I have an MXQ S805 1GB (KOT49H.20151225 test-keys) also know as the m201C version which has 1022MiB rather than 510MB. I have a problem using either of these images: Armbian_21.02.0-trunk_Aml-s812_bionic_current_5.10.0_.img.xz Armbian_21.02.0-trunk_Aml-s812_focal_current_5.10.0_.img.xz Using BalenaEtcher I burn the images onto SD card absolutely fine and they verify okay (tried multiple SD cards). Then I proceed by editing uEnv.txt and changing the default dtb from meson8m2-mxiii-plus.dtb to meson8b-mxq.dtb and renaming armbian_first_run.txt.old to armbian_first_run.txt, then proceeding to boot from the SD card using the hidden recovery/boot button behind the AV socket I attempt to boot, sadly, I get MODE not supported. I've tried two different screens made by Acer and Samsung, and no luck. I even tried changing the option from 60hz (which I know my screen supports) to 50Hz and even tried to use 720p/480p rather than 1080p neither of them work. The Samsung reports no signal, while the Acer screen reports invalid display mode. Using the meson8b-odroidc1.dtb rather than the MXQ I can get it too boot with no display errors, I do however get zram config issues, and , but its very slow, and unstable, mostly due to the fact I think the Ghz is higher on the Odroids than these cheap MXQ. Is there something I'm doing wrong? I've had a look at your builder and do not see MXQ as one of the supported boards, just a La Frita, and Odroid C1 which most likely will cause me the same issues. The MXQ board seems very popular and not sure why I'm having problems while many are not.