Forcing u-boot to detect USB3 storage

[SirRyanTheGeek]

For Ayufan's Bionic, write "bionic-minimal-xxx.img" images to "MicroSD".
Then, edit the following file and change it to mount "usb-device" on the "root-system".
/boot/extlinux/extlinux.conf
The above file is a general text file, so I think it can be understood if you look inside.

That's where I was heading, too. I'm wondering that when I list out my block devices, do I specify /dev/sda or some other label?

The file has the following in it:

Code:

root@rock64:/var/log# cat /boot/extlinux/extlinux.conf
timeout 10
menu title select kernel

label kernel-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   kernel /boot/vmlinuz-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   initrd /boot/initrd.img-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   devicetreedir /boot/dtbs/4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4

label kernel-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a-memtest
   kernel /boot/vmlinuz-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   initrd /boot/initrd.img-4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   devicetreedir /boot/dtbs/4.4.167-1163-rockchip-ayufan-g3d2c5b33817a
   append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest

 My block device list shows:

Code:

root@rock64:/var/log# lsblk -o NAME,LABEL
NAME        LABEL
sda
|-sda1
|-sda2
|-sda3
|-sda4
|-sda5
|-sda6      boot
`-sda7      linux-root
mtdblock0
mmcblk1
|-mmcblk1p1
|-mmcblk1p2
|-mmcblk1p3
|-mmcblk1p4
|-mmcblk1p5
|-mmcblk1p6 boot
`-mmcblk1p7 linux-root

So replacing "root=LABEL=linux-root" with "root=/dev/sda" you think might do the trick? Hopefully increasing the timeout to 200 instead of 10 will allow it enough time (and that it honors that value when no monitor is attached).

I'll give that a shot - thanks!

---

Nope. Didn't work that way. In fact, after the delay the indicator lights winked out on the board! lol!

Hmmm. There's gotta be a way to do this...