06-21-2018, 06:07 PM
(06-05-2018, 10:14 AM)jzhang18 Wrote: Actually, The local boot process never finished after upgraded to new Kernel. ..
I have no idea on how to fix "Warning: root device does not exist" during kernel update. search on internet, there are tons of similar posts. it seems a very common issue in Linux world.
As far as I can tell, this warning is simply just that - a warning that there isn't a device labeled 'root' in the fstab. As long as there are not any other warnings or more importantly, errors, then the install should be fine as fare as the update process is concerned.
(06-21-2018, 11:41 AM)gregb49 Wrote: Are there any clearer instructions on how to install the files from github and which ones to choose, or I should I just try another debian image?
So that was the stretch mate image you used? 0.6.57 or an earlier one (i.e. 0.6.44).
I suspect (haven't tried yet, but have seen enough reports) that there is either something broken in kernel updates, or the kernel version being updated to is a broken one. Best solution would be to not update or mark the kernel package so that it doesn't get updated until the stability issue is resolved. I have tried some of the images (bionic-container) post 0.6.53 and the rock64 was booting again, but maybe it's gone dopey again or the update process has a fault.
