DietPi on BananaPi M5

At the moment I still have have a tiny server with a bunch of containers running on a Nanopi Neo 3.
It’s performance is still OK, but adding more containers could run into performance or memory restrictions.
I also had a Banana Pi M5 laying around, but had no actual need for it until now. I had bought it becuase it seemed attractive:

  • 16Gb EMMC
  • 4GB Memory
  • a bit more powerfull than the NPN3
    So today I created a Dietpi version for this board.
    Of course I ran into problems like “invalid certificates” “expired certificates” etc but could solve that using de sub-shell during the conversion by:
  • adjusting the system time to the proper one with: dpkg-reconfigure tzdata
  • adjust the sources.list files to a working mirror (this happend a few times along the way, also during the 1st real DietPi boot update run)
    The most time consuming was when the script timed out with the messag: A dependency job for serial-getty@ttyS0.service failed
    During the hardware conversion 8 tty’s were found(?) to be converted? But in the end I disabled/masked all of them manually modifying each sytemctrl start getty@ttySx command to disable and resume. But every tty took its time to time-out.
    Anyway, in the end it I succeeded to have I regular Dietpi verion running on the Bananapi M5.

Still one thing bothers me: I use it headless, but I have not found a way to disable de display drivers yet.
When I will use it as a server I do ot intend to reboot it often, but rebooting the system takes more then a few minutes because the boot sequense tries to initialise but cannot gpu and or other drivers. How do I know?
On the debug console the following meson-drm messages appeared:

[    1.623367] meson-drm ff900000.vpu: DSI transceiver device is disabled
[    5.511965] panfrost ffe40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[   15.838354] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   15.838373] meson-drm ff900000.vpu: [drm] *ERROR* [CRTC:43:meson_crtc] commit wait timed out
[   26.078362] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   26.078378] meson-drm ff900000.vpu: [drm] *ERROR* [CONNECTOR:33:Composite-1] commit wait timed out
[   36.318362] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   36.318380] meson-drm ff900000.vpu: [drm] *ERROR* [PLANE:37:meson_primary_plane] commit wait timed out
[   46.558360] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   46.558377] meson-drm ff900000.vpu: [drm] *ERROR* [CRTC:43:meson_crtc] commit wait timed out
[   56.798337] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   56.798347] meson-drm ff900000.vpu: [drm] *ERROR* [CONNECTOR:33:Composite-1] commit wait timed out
[   67.038370] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   67.038389] meson-drm ff900000.vpu: [drm] *ERROR* [PLANE:37:meson_primary_plane] commit wait timed out
[   77.278344] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   77.278361] meson-drm ff900000.vpu: [drm] *ERROR* [CRTC:43:meson_crtc] commit wait timed out
[   87.518335] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   87.518344] meson-drm ff900000.vpu: [drm] *ERROR* [CONNECTOR:33:Composite-1] commit wait timed out
[   97.758350] meson-drm ff900000.vpu: [drm] *ERROR* flip_done timed out
[   97.758369] meson-drm ff900000.vpu: [drm] *ERROR* [PLANE:37:meson_primary_plane] commit wait timed out

After a lot of those messages and may minutes later I finally can log into the system using ssh.
From there on the system seems to run OK.

My question: how can I disable the graphical items so there is no unneeded delay during (re)boot?
In the Dietpi-config I can only change the display settings, but not disable it completely.
I have seen some remarkts about headless here: AUTO_SETUP_HEADLESS disabling GPU - #4 by RyoShinzo
But that seems to be to old and I cannot locate the items referenced there.
I have searched in the various config and/or ini files but some I don’t even have or in the ones I do have I see no reference that seems related to enable/disable the graphical hardware or display.

Any help appreciated
By the way, I used a minimal Armbian image to boot from and then ran the dietpi-conversion script

Best to use following commands to check boot sequence and time needed per step

systemd-analyze blame
systemd-analyze critical-chain