Because our system worked for years and was very fast (also in booting) I refreshed everything. So I did a new Image from scratch for Raspberry-Pi 4 8GB-RAM.
Everything works as expect, BUT not the loading-process. First impression was the internet-connection, but with the
I’ve got this feedback (changed the @-sign to the %-sign because of board-issues here)
The time when unit became active or started is printed after the “%” character.
The time the unit took to start is printed after the “+” character.
graphical. Target @1min 31.152s
└─lightdm.service @1min 31.027s +122ms
└─systemd-user-sessions.service @4.901s +70ms
└─network.target @4.836s
└─wpa_supplicant.service @5.411s +104ms
└─dbus.service @3.658s +571ms
└─basic.target @3.617s
└─sockets.target @3.617s
└─dbus.socket @3.616s
└─sysinit.target @3.595s
└─systemd-udev-settle.service @1.424s +2.169s
└─systemd-udev-trigger.service @1.023s +386ms
└─systemd-udevd-kernel.socket @840ms
└─system.slice @707ms
└─-.slice @707ms
What is happening there that the graphical-part is now taking a 1,5minute delay before it continous from the shell-mode to switch to the Mate-Desktop? Same screen but older software-version has this effect not…
How can I get more information on that?
