blubbblubb

Great works perfectly, and again something i should have been able to guess (Is there some sort of wiki/documentation page for the possible uEnv.txt options?)

Ok i can't believe i actually didn't try to specifiy the root fs in /etc/fstab with UUIDs before ... I dont have the board at hand until after the weekend but i wil try it then. I also don't see the reason to change the kernel args and then hardcode the device in /etc/fstab Edit: now i added the rootfs with UUID in /etc/fstab, however this alone is not enough for it to boot, after adding: root=/dev/mmcblk1p2 in uEnv.txt as well everything works, however seeing as now there is a hardcoded device again and im not able to find extensive documentation on the uEnv.txt file i wanted to ask if it is possible to specify UUIDs in there as well?

no i didn't. After i installed the system to emmc i did however create a new partition table on the sdcard and created a new partition (i assumed this would be enough). To be sure i just executed the dd command and tried to boot with the sd card again and nothing changed, still stuck while booting.

As i wasn't able to find the information i seek (or was not able to understand the posts which contained it) i wanted to ask if it is possible to boot the bpi m64 from emmc with an sd card inserted for additional storage. I followed the instructions from https://github.com/avafinger/bpi-m64-firmware to install the system to the emmc and it boots fine if there is no sd card inserted, however as soon as i insert an sd card it does not boot anymore, from what i could gather online this is the case for all the bananapi devices and there are some workarounds with adjusting the root variable in the uEnv.txt however with the bpi m64 there is no root variable in the uEnv.txt Would it be possible to tell the system somehow to boot from emmc instead of the sd card?