Tinkerboard not starting after first boot

Troubleshooting
1

I am using a Asus Tinker Board (1). After flashing the latest version of Dietpi (Debian Bookworm) on a SD card the Tinker Board boots fine. It’s processing the first boot script and then restarts. Then the Tinker Board looks dead. Only the red power light is on. No network activity and no data activity.
I flashed the SD card once again and get the same result. Bullseye seems to work fine.

Required Information

  • DietPi version | DietPi_ASUSTB-ARMv7-Bookworm
  • Distro version | Debian Bookworm
  • Architecture | ARMv7
  • SBC model | Asus Tinker Board
  • Power supply used | 5.1V 2.5A TT Electronics
  • SD card used | Sandisk 16GB Class 10

I cannot give more info because it does not boot after the first run.

2

Haha, same problem dude.
Seems like problem in some armbian packages updates (because I have same problems and with armbian too after update, hehe).
Glad to see that I’m not single with this problem :slight_smile:
But… I still don’t know how to solve this…

3

Seems to be similar to TInkerboard not booting after updating

Feel free to test plain Armbian if it is really same once system has been updated

4

As a temporary solution of this problem, you can use apt-mark hold on this problematic packages.
I recorded video with instruction for you: https://www.youtube.com/watch?v=mIOdTrU7lO8

5

Thanks! That worked for me.

1 Like
6

Hi, ist there any way to prevent the auto update on first boot to nuke the fresh system?

7

Pressing CTRL C or X during boot will boot into the dietpi menu. Then you can exit the menu and perform the solution.

8

Thanks

9

For my own install I just created a pre-boot script that has the apt hold stuff from the above youtube video.

I think I did this script:
/boot/Automation_Custom_PreScript.sh

With this in there:

apt-mark hold armbian-firmware
apt-mark hold linux-dtb-current-rockchip
apt-mark hold linux-image-current-rockchip
apt-mark hold linux-u-boot-tinkerboard-current

That will prevent the issue.

If you want to follow along we’re discussing here:

1 Like
10

Hello!
I need to inform that now, this problematic packages is fixed (Literally yesterday), and you can use this commands to update it now:

sudo apt-mark unhold armbian-firmware
sudo apt-mark unhold linux-dtb-current-rockchip
sudo apt-mark unhold linux-image-current-rockchip
sudo apt-mark unhold linux-u-boot-tinkerboard-current
sudo apt upgrade

I am just updated, and everything works properly :slight_smile: