@lex Posted December 2, 2017 Posted December 2, 2017 5 hours ago, seandroid said: I have burned a copy to sd card using your instructions here: https://github.com/avafinger/bpi-m64-firmware-v2 @seandroid Please, try to use this instructions here, and set res to 720p, it has latest kernel fix. HDMI -> VGA not always works, it depends on many factors (quality,etc,etc...) and resolutions. Can't do much about this.
blubbblubb Posted December 2, 2017 Posted December 2, 2017 On 12/1/2017 at 2:41 PM, @lex said: Just for the record, i looked at boot log, boot device ID becomes 1 when there is SD CARD inserted, so kernel cannot find rootfs. The solution for that specific Image to boot from eMMC with "empty" SD CARD inserted would be one of this: * Use UUIDs * Fix u-boot to pass correct ID * Change kernel args manually 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?
@lex Posted December 3, 2017 Posted December 3, 2017 On 12/2/2017 at 11:47 AM, blubbblubb said: i wanted to ask if it is possible to specify UUIDs in there as well? Please try: root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx instead of root=/dev/mmcblk1p2 where xxxxxx is your rootfs UUID
blubbblubb Posted December 3, 2017 Posted December 3, 2017 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?)
@lex Posted December 3, 2017 Posted December 3, 2017 (edited) 1 hour ago, blubbblubb said: wiki/documentation page for the possible uEnv.txt options? uEnv.txt, ArmbianEnv.txt are dependents on which u-boot version is in use and patches applied, i can tell you u-boot 2017.09 can be used to load and run legacy and mainline kernel and that depends on which patches are applied and how is configured. I don't know if there is a wiki/documentation somewhere (possibly there is) , i usually search here in Armbian forum (as @tkaiser say most of problems and solutions are already fixed/done some time ago) or you can refer to https://www.denx.de/wiki/U-Boot and also https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt Edited December 3, 2017 by @lex typo - kernel args
Recommended Posts