Can you replicate this issue on a fresh DietPi installation of the DietPi_v127_OdroidXU4-armv7-(Jessie).img, after its been updated?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
root@DietPi-XU4:~# uname -a
Linux DietPi-XU4 3.10.103+ #1 SMP PREEMPT Sat Sep 3 10:17:24 CEST 2016 armv7l GNU/Linux
I've had some rebooting problems recently in view of the above this may explain it.
Strange, not experienced any my end. Is there anything specific going wrong during the reboot?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
It's nothing consistent but once or twice I rebooted and nothing happened and once or twice I rebooted and it shut down and didn't restart, so I had to power cycle. But mostly it's working as it should.
It's nothing consistent but once or twice I rebooted and nothing happened and once or twice I rebooted and it shut down and didn't restart, so I had to power cycle. But mostly it's working as it should.
John
Hi John,
Does sound PSU related. I believe during boot, the XU4 power usage peaks dramatically (eg: all usb devices are powered at once), CPU is probably running full clock. So any issues with "unstable power" would be most apparent then.
Although if i remember correctly, you upgraded the PSU on your XU4?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
Hi,
I have the same problem : after poweroff not booting again. my kernel is 3.10.96+
tried two PSU's one 6A and one 10A.
I think it has something todo with links to the initrd that are not correct
edit :
I just found out that the file
exynos5422-odroidxu3.dtb does not exist in the 132 boot partition
copying exynos5422-odroidxu3.dtb as root from a fresh 127 image that has not been updated to 132 to my 132 emmc solved the boot problem for me, but I'm still at kernel 3.10.96+ and not at 3.10.103+ while the kernel 103 is available on the boot partition.
