Soo, I finally got time to dive into this again...
I also tried compiling not just Ayufan's kernel, but failed. I also tried to compile mainline Linux 4.20 kernel from Torvalds, same result. By the way, The RockPro64 device tree got into mainline in September 2018... So theoretically we would be able to compile Linux Images from Mainline Linux, or even just take the official ArchLinuxARM kernel.
When I extract the ramdisk + kernel + dtb from Ayufan's .deb packages and Place them into /boot (like I described in the start of the thread), the board suddenly boots.
That the board hangs on 'Waiting for root device LABEL=linux-root' is normal, because the file system drivers are all in the initramfs. So, broken initramfs means no file system drivers means no bootpartition and thus no boot.
Interestingly, in my frustration I tried to just not define any initramfs in extlinux.conf, and still got to 'Waiting for root device LABEL=linux-root'. So, this just gave me an idea: Before I start digging through tons of code and the mkinitpio procedure, why not just statically tell linux to compile filesystem, pcie, raid etc. drivers into the Image and just boot without an initramfs altogether? Any thoughts on where that might go wrong?
First Problem: I have my rootfs on an LVM partition, which needs userspace tools... great
Greetings,
Matyas
I also tried compiling not just Ayufan's kernel, but failed. I also tried to compile mainline Linux 4.20 kernel from Torvalds, same result. By the way, The RockPro64 device tree got into mainline in September 2018... So theoretically we would be able to compile Linux Images from Mainline Linux, or even just take the official ArchLinuxARM kernel.
When I extract the ramdisk + kernel + dtb from Ayufan's .deb packages and Place them into /boot (like I described in the start of the thread), the board suddenly boots.
That the board hangs on 'Waiting for root device LABEL=linux-root' is normal, because the file system drivers are all in the initramfs. So, broken initramfs means no file system drivers means no bootpartition and thus no boot.
Interestingly, in my frustration I tried to just not define any initramfs in extlinux.conf, and still got to 'Waiting for root device LABEL=linux-root'. So, this just gave me an idea: Before I start digging through tons of code and the mkinitpio procedure, why not just statically tell linux to compile filesystem, pcie, raid etc. drivers into the Image and just boot without an initramfs altogether? Any thoughts on where that might go wrong?
First Problem: I have my rootfs on an LVM partition, which needs userspace tools... great
Greetings,
Matyas