February 28, 20251 yr Hi, Today I updated to Armbian v25.2 and did the good old reboot after the update. I never had issue with runing the SBC headless, but since the update I get a blinking blue status LED for a couple of minutes until the system boots. When I tried to plug in a monitor to get an idea what is going on, the SBC boots normally. Monitoring with HDMI monitor plugged in: https://paste.next.armbian.com/ehirazemot Monitoring without HDMI monitor plugged in: https://paste.next.armbian.com/zaqipatoci Most notable difference are: [ 105.189528] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out [ 105.189543] meson-drm ff900000.vpu: [drm] *ERROR* [CRTC:43:meson_crtc] commit wait timed out [ 115.429535] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out [ 115.429544] meson-drm ff900000.vpu: [drm] *ERROR* [CONNECTOR:33:Composite-1] commit wait timed out [ 125.669535] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out [ 125.669544] meson-drm ff900000.vpu: [drm] *ERROR* [PLANE:37:meson_primary_plane] commit wait timed out Do you guys have any idea how to fix this? Edited February 28, 20251 yr by Holgi
March 4, 20251 yr Hi, I estimated a similar behaviour after upgrading to 25.2.2: the box seemingly didn't start headless anymore., i.e. it was not reacheable remotely. My guess is that the absence of a HDMI connected screen during boot process lead to problems initializing the network ... maybe Connecting a monitor solved the boot problem. So I tried the use of a HDMI dummy plug which is working fine: the box is reacheable via network as expected. Regards, Joe
March 4, 20251 yr Author My network configuration also got mangled in the update, yet I was able to fix it by essentially redoing it from scratch and setting the correct permissions. This seems to be unrelated to the HDMI issue slowing down booting. I googled a bit more and found this mailing list conversation discussing an issue which seems to be fairly similar if not identical: https://patchwork.kernel.org/project/linux-clk/patch/20250213221702.606-1-linux@martijnvandeventer.nl/ Patching and compiling the kernel myself is something I don't trust myself doing. As I'm rarely rebooting my system, I'm currently accepting the long boot times.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.