talraash

Just write image, change dtb x96-max-rmii and run box with reset button in av.

No... wired network work with dtb from 5.2.1

ok... in a few hours, then I will edit this post. upd Same behavior as before wired network work only with g12a-x96-max-rmii DT.

Yep... i have 2 different models with 100mb h96max2 and x96max in both case netwok work with meson-g12a-x96-max-rmii.dtb

Rewrite it. Use armbian as example. Write correct memory/bus addresses etc. You can find specific help in google just type "Device tree"

You can't use dtb from android as is...

lol... just compile from sources (RK legacy or mainline) u-boot and kernel and install/compile package what you want. or use image from rk topick)

@Gossamer Don't use " " (space) in folder path.

High performance soc with flat metal heat sink... what a genius R&D)

different ram clock maybe, or some other options in DT.

I finally “killed” my last tv box on s905x. How does s905x2 feel like in linux? According to synthetic tests, should the power of new soc be sufficient for sw video decoding up to 1080p? Does it make sense to pay a little extra and get boxes on the new soc?

It's just chromium fork with minor tweaks... Use instruction for chromium.

audio subsystem via rca don't work in mainline. Use hdmi audio or usb audio card.

Not always. If you break the u-boot being in nand there may be problems. If the u-boot in nand is broken, it was possible to restore the operation of the box only by closing the nand contacts and writing the correct u-boot or full image.

Is it necessary? Firefox work fine with multimedia, next build of chromium may also be fine. Chromium is very resource intensive at compile time(one build with compiliting time ~3 hours need 16 threads cpu ~ 32Gb ram and ~100 gb storage on ssd).