09-24-2017, 04:37 AM
Hi !
I installed linux-image-4.13.0-rockchip-ayufan-130-g4f68418_0.5.13_arm64.deb on top of stretch-minimal-rock64-0.5.13-130-arm64.img.xz. The sytems starts with 4.13.0-rockchip-ayufan-130-g4f68418 but fails to identify the root filesystem now:
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=linux-root does not exist. Dropping to a shell!
Is there any way to boot 4.4.77 in uboot again (like in grub) or to hard code the device for the roor filesystem instead of the defined LABEL:
earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 init=/sbin/init coherent_pool=1M ethaddr=96:e3:6f:f5:12:17 eth1addr=96:e3:6f:f5:12:37 serial=794bb69656b7cf1
Many thanks !
I installed linux-image-4.13.0-rockchip-ayufan-130-g4f68418_0.5.13_arm64.deb on top of stretch-minimal-rock64-0.5.13-130-arm64.img.xz. The sytems starts with 4.13.0-rockchip-ayufan-130-g4f68418 but fails to identify the root filesystem now:
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=linux-root does not exist. Dropping to a shell!
Is there any way to boot 4.4.77 in uboot again (like in grub) or to hard code the device for the roor filesystem instead of the defined LABEL:
earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 init=/sbin/init coherent_pool=1M ethaddr=96:e3:6f:f5:12:17 eth1addr=96:e3:6f:f5:12:37 serial=794bb69656b7cf1
Many thanks !