-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reboot issues #5
Comments
This is a known issue that I was unfortunately unable to solve. Perhaps with the latest u-boot mainline it could be solved. I believe kernel 5.4 and 5.6 there is no such issue. |
I've found in the readme file. |
You can check https://github.com/avafinger/nanopi-r2s-ubuntu-server-minimal-image/releases/tag/v0.2 which is ubuntu 19.10 and then issue the following to upgrade to 20.04 LTS:
And trim/remove the unwanted services that will be created/started in 20.04 LTS. |
Maybe https://github.com/avafinger/nanopi-r2s-ubuntu-server-minimal-image/releases/tag/v0.3 is a better choice. |
do you mean the kernel 5.4.28 will fine? |
use kernel5.4.28 ‘s boot + tagv0.5 ’s rootfs |
I don't know why WAN would interfere in "reboot" process. |
maybe not WAN,only a guess。 I can't get UART debug log.
try tagv0.3. can't reboot |
To be able to investigate we need a complete boot log (shutdown -h now and reboot). Please get a USB TTL debug so we can have a look at the boot log. |
friendlyarm release the ubuntu20.04(kernel5.10),i will test it。 now I can't get UART debug log. i need some time try USB TTL link |
|
did anyone figure this out? |
when terminal run : sudo reboot
the nanopi r2s shutdown but not boot success
tag 0.5 + kernel 5.8.1
The text was updated successfully, but these errors were encountered: