Am Sonntag, den 04.02.2018, 12:54 -0500 schrieb Scott Tablett:
> On 2/4/2018 5:46 AM, Gert Wollny wrote:
> > There is another boot partition available in
> > images/kernel-update.tar.bz2
> >
> > and this I got to boot. It doesn't have a ramdisk. Currently, I use
> > a Ubuntu 16.04 userspace with a patched glibc to accept the old
> > kernel 3.0* that was there before though, so for some reason NFS is
> > not working and NAT seems to be disabled in the kernel (have to
> > investigate).
It turned out that iptables-nat is disabled in the kernel and some
module nfsd is missing.
unfortunately, I did an upgrade on my userspace and now it seems that
systemd has troubles with the kernel and stops booting after the
Ubuntu-blabla message, so i can not tell you much more right now.
> Thanks Gert,
>
> You give a good idea having root on sdcard versus ramdisk. I am not
> seeing kernel-update.tar.bz2 in debian installer images folder.
> Maybe you are referring to Ubuntu.
>
> ftp://ftp.ca.debian.org/debian/dists/testing/main/installer-
> armhf/current/images/
I was referring to
http://www.compulab.com/products/computer-on-modules/cm-fx6/#devres
This package includes the closed source driver for the graphics card,
but one should be able to use the config as a base for creating a new
4.14.16 based kernel that has etnavi support. In fact, I build such a
kernel that also booted and mounted the root partition, but then
systemd hangs same like with the kernel provided by compulab.
>
> Thanks for pointing out update. I updated on-board SPI flash
> following the link you provided.
> Debian installer boot.scr results in same message.
> The Debian boot.scr checks for ${boot_targets} . This is not set in
> Compulab u-boot update.
When I look at this boot.scr then you have to set many parameters to
run this, but I don't know much about uboot
best,
Gert