@bohdi Big thanks, I managed to get it running but still have an error later - the command line differs from what I have in uboot Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! LABEL=rootfs does not exist. Dropping to a shelby dkuku - uBoot
Will try this when I get home, also with the ubot env i had it loaded but then flashed new uboot and reset this to default envs from uboot with env command because too much clutter and i was thinking it helps ;)by dkuku - uBoot
@bohdi Hi, I was using screen for serial connection and it gave me just 1 screen of output ;) this is from minicom: Maybe as a walkaround is there a option to hardcode the commandline somewhere? I know that when compiling kernel there is an option for that. what about device tree ? U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:52:06 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkby dkuku - uBoot
Hi, I'm fighting half of the day and slowly giving up. Nsa320 with latest debian and kernel on usb stick and latest uboot with default settings (env default -a). When booting I get an error: [ 7.268011] NET: Registered protocol family 17 [ 7.272551] Key type dns_resolver registered [ 7.276898] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300) [ 7.284314] registeredby dkuku - uBoot