I’ve installed Raspberry Pi OS 64bit on my AML-S905X-CC and it runs my Docker apps really well. But when I use “sudo shutdown -H” from the command line to shutdown the Pi, the system goes to a Halt state for about a minute and then reboots. Any suggestions?
Just tried “sudo shutdown -P”. Does the same thing except it reboots a little sooner than with -H.
sudo shutdown -H now should halt the machine and not reboot it.
sudo shutdown -P now will trigger a reset but since there’s no way to turn the board on again except to plug and unplug power.
If this is not the case, please let us know and we will re-test.
shutdown -H now and -P now both reboot the S905XX booting from EMMC.
-H takes about 30 seconds to reboot. -P reboots after 5 seconds
PRETTY_NAME=“Debian GNU/Linux 11 (bullseye)”
SUPPORT_URL=“Debian -- User Support”
Reflash the bootloader. You have the watchdog on.
Any instructions on this? Below are the contents of /etc/default/grub
lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT=“noquiet nowatchdog nmi_watchdog=0”
#GRUB_INIT_TUNE=“480 440 1”
Use libretech-flash-tool against the MicroSD card on a different Linux computer. It will rewrite the bootloader and leave the rest of the image intact.
This is understood. What about for EMMC? Just run the
sudo pyamlboot/run.sh aml-s905x-cc ums-emmc then use the flash tool? I have working images that I do want to redo.
Yes, you can do that.
I also have the problem that my s905x reboots when sending the shutdown command.
I’ve followed your instructions and re-flashed the bootloader via ibretech-flash-tool - but no change.
How do I manually disable the watchdog? I’ve found similar issue in a Raspi forum where the GPIO was causing this - could the reboot-instead-of-shutdown behavior also be caused by this and the remapping?
I’m not using the GPIO at all.
Please check the latest bootloader. This should no longer be an issue. You can wake the board after shutdown/suspend here: Libre Computer AML-S905X-CC Le Potato Wakeup Sources
Never gave feedback here - correct, the latest bootloader fixed this.
Awesome, thanks alot.