Armbian reboot hangs and is unresponsive

not tryng any hypervisota or any vm stuff. iust a a simple install.

Thank you. I will try this tomorrow and report back.

2 Likes

Welcome to Armbian 23.02.2 Jammy with Linux 5.10.110-rockchip-rk3588

No end-user support: work in progress

System load: 2% Up time: 0 min
Memory usage: 5% of 3.65G IP: 192.168.1.53
CPU temp: 35°C Usage of /: 6% of 234G
RX today: 46.7 KiB

Tip of the day: Help us fund build iron https://forum.armbian.com/crowdfunding/project/9-funding-equipment/

[ Kernel and firmware upgrades disabled: armbian-config ]
Last check: 2023-03-29 12:56

Last login: Wed Mar 29 12:55:14 2023 from 192.168.1.168
root@pg-592:~# apt install mali-g610-firmware
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package mali-g610-firmware
root@pg-592:~# apt-get install mali-g610-firmware
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package mali-g610-firmware

Well, you need to add the repository - that’s the first thing you should do on armbian, actually.

The two ppas in the “in order to enable 3d acceleration”…

Thanks I wasn’t sure what to do at that point. That worked:
mali-g610-firmware is already the newest version (1.0.0-2).
mali-g610-firmware set to manually installed.
The following package was automatically installed and is no longer required:

trying a boot loop again with cron now.

I don’t know what the problem is :frowning:

System still hangs on reboot. I have to physically remove power and re-power to get it to boot. Any other ideas on fixing this boot problem?

Well by taking out options I believe there is still something about these files:


I have only tried the release version and not the armbian version since its made for nvme might help? Maybe not but… its the only thing I am seeing that could fix this maybe.

Rock 5b - sudden reboot, bootloop in login screen, firmware runs unstable… Tested different operating systems like Armbian, Android, Ubuntu via Nvme and Emmc… always system crash followed by reboot and bootloop in login screen. Apparently there are problems in the power management of the Rock5b system. Too much or too little power, handshaking and dependencies incorrect…? The system was first powered directly from a 60Watt USB-C power supply from Allnet China. The USB C cable that is used is suitable for up to 100 watts. Today I used a multi USB C hub for testing and this hung between the power supply and the Rock 5B! Completely surprisingly, the system runs uninterrupted and without any problems since then. The multi USB C hub now controls the data stream to the USB 3.0 hard drive and also the power supply. During some tests with several video applications and copy operations at the same time, there were absolutely no problems. Power supply and 3TB USB 3.0 hard drive are connected to the multi USB hub and the system running stable.

1 Like

A hub to handle a steady power sounds about right.

1 Like

I’m currently testing with MonkaBlyat’s Afterburner Armbian Image and I’m really pleased with performance and capabilities especially in streaming via youtube and 4k resolution without any problem. 8k is unfortunately a bit too much for my internet connection. DarkevilPT Thanks for your recommendation. I must say the USB C hub is currently a very important bridge between power supply and Rock5b. The system l
running for about 10 hours in continuous operation without a single reboot. This would be absolutely unthinkable without the USB hub, since at least 4plus X reboots per hour with every tested operating system, whether android, debian, ubuntu or armbian.

Translated with www.DeepL.com/Translator (free version)

Just to be clear… the issues Ive had never happen on the system but when starting it or shutting it down.
When for the first time I had those random reboots happened on openFyde and all it required was a spi flash to clear.

After that… its a bit random at times… then again if you are using hubs u better stick usb for mouse cable or usb for keyboard on the dongle… cause … having them plugged to the board directly might stuck on booting with the blue light of death… so yeah.

1 Like

I contacted Roxa . They provided a list of power supplies that they have tested.

I am looking for a replacement for raspberry pi 4B for my company in deploying our IOT edge solutions. The rock5b has all the right features. Except.: it will not reboot. It reboots fine sometimes , then hangs forever. I can’t deploy this board if I cant reboot it remotely.
Every official os I try, if I set up a cron like this to test:
*/2 * * * * /usr/sbin/reboot #boot every 2 min to see if it fails.
Reboot fails. Sometimes the 1st try, sometimes the nth. This board is basically junk if you cant reboot it remotely or on a schedule . I just can’t understand how you can go through all this amazing engineering to produce a board the rock5b, that can’t reboot.
Please come up with a fix, so I can buy these boards and use them in real industrial applications.

They responded with :slight_smile:

Currently ROCK 5B has compatibility issues with PD power supply. Please check the following list:
https://wiki.radxa.com/Rock5/5b/power_supply
The workaround for now is to use non-PD power supply, or use our official power supply:
https://shop.allnetchina.cn/collections/power/products/radxa-power-pd-30w

FYI:
A non-PD power supply typically provides a fixed power output and does not have the ability to negotiate power requirements with the connected device.

I am using a non PD power supply:

So as there response is not helping me yet, it might help you If you look at the tested power supply options. I ordered the official power supply to test with but I doubt that will fix this fail on reboot issue.

This is the bootloader for arm I used: https://github.com/huazi-yg/rock5b

https://github.com/huazi-yg/rock5b/releases/download/rock5b/rkspi_loader.img
I got this image from this forum.

I found this link: https://wiki.radxa.com/Rock5/guide/build-u-boot-on-5b

DarkevilPT, can you share the link to the prebuilt images that you reference here. I’m having a hard time finding wiki page with it.

Yes Sir. I do the windows method but linux ninjas do the easy wey:
https://wiki.radxa.com/Rock5/install/spi#Advanced_.28external.29_method

Either way works… and I must say… I did it yesterday and so far so good … but I did in the past and idk what triggers the hanging but this only fixes it ‘temporarly’ idk… But do try it and u will notice it will reboot fine.

Thanks for the link. I wanted to check that I am using the same armbian image. I am its the same. I flash it the linux method.

I’m curious if you would add a cron job to reboot and see if you have the same problem I have. Leave it run overnight.

in terminal:
run:
crontab -e
add this:
*/5 * * * * /usr/sbin/reboot

it will reboot every 5 min. Leave it run overnight. See if you have a system running in the morning.

That might explain this - your voltage is too low. Aim for 12 V, 20 can be done too

I found the issue. For those who are trying to run Arbmian with only a nvme drive (no mcirosd). It is NOT a power supply problem.

The issue:
If you follow this guide (https://wiki.radxa.com/Rock5/guide/build-u-boot-on-5b) and compile your boot loader, or you use a spl_loader image thats pre built. The rcok5b will NOT boot without an mic-sd card present.

Then you will look around and someone will point you to this spl flash image.

The problem is this boot loader. Something is wrong with it regarding reboot. Using this boot loader causes inconsistent reboot. Sometimes it will boot sometimes it will hang up.

If you boot with the other boot loaders using an sd card. Rebooting works.

2 Likes

OK. I don’t boot off the nvme and my SPI is clear so I didn’t know.