hexdump

i think the arm version of the surface pro 9 is close to the devkit - surface pro x is an older design using a snapdragon 8cx gen2 (i think) and not the gen3 the devkit is using and which is a very different soc

@hartraft - there are two kernel options for mglru: CONFIG_LRU_GEN=y and CONFIG_LRU_GEN_ENABLED=y - the first is to have mglru built into the kernel and the second is to have it enabled by default - if they are not in your kernel config it might be required to rebuild the kernel with them (or at least the first) enabled

@SteeMan - interesting, i did not know about ampart, but as you said: for s905 it is better to still just run from sd card as trying to boot from emmc is quite complicated and risky to brick the device

@DWP - running s905 from emmc is very complex and far from easy - you can have a look at this thread to get an idea about this topic:

but be careful with such scripts and check them by hand to make sure they do not touch the emmc low level or your created partitions ... for copying over "rsync -axADHSX --no-inc-recursive --delete /source/ /target" always worked well for me - be careful with the "--delete" and note that the source should have a "/" appended and the target not if you want target to be a 1:1 copy of source good luck and best wishes - hexdump

@winnt5 - maybe start with data only and see if you can handle it well from an sd-card booted system and then maybe move on from there ... maybe you can just partition everything from cache on (i.e. after its starting poiint if there is nothing reserved/hidden inbetween - better double check the layout a few times) as you like it as all those should be android partitions and not related to boot ... there is always a chance that something goes wrong and you brick the box - maybe do a dd dump of the full device beforehand ... in the end you are on your own if you play around with this

@winnt5 - any partitioning tool should like fdisk, gdisk etc. - just make sure you are creating an mbr partition table and not gpt and best is to some detailed mode if available in the tool used to be able to hit the block numbers of the data partition exactly good luck and best wishes - hexdump

@SteeMan - in case you want to experiment (i.e. not sure if it really works), you might play around with chainloading the g12a-u-boot.bin (s905x2) and sm1-u-boot.bin (s905x3) from https://github.com/hexdump0815/u-boot-misc/releases/tag/200926-01 or gxb-u-boot.bin (s905) or gxl-u-boot.bin (s905x) from https://github.com/hexdump0815/u-boot-misc/releases/tag/200718-01 ... basic chainloading goes like this - https://github.com/hexdump0815/imagebuilder/blob/master/boot/boot-amlogic_gx-aarch64/s905_autoscript.txt - maybe compare it to the balbes150 boot scripts for fancier ways and most probably better armbian integration ... the files mostly exist in a serial version for serial console and another one for hdmi output and usb keyboard input (which sometimes works and sometimes not) ... better ignore the boot-xyz.dd file at the links above - they are for booting amlogic boxes without the legacy u-boot, but using them is quite complicated and risky (you can seriously brick the box worst case) as mentioned all this is without any warranty or support, but it might be a good starting point for experiments good luck and best wishes - hexdump