You are not logged in.
Pages: 1
Hello, I would like to know if it is possible to change or optimize the boot system more simply, such as systemd-boot or booting the kernel directly.
I understand that the question is kind of silly, but I'm testing the limits that can be reached without damaging the system because it turns out that before I used Windows 10 and the boot was 35 seconds depending on the programs and system services, (using hibernation is not worth it), however with Q40S the process is simpler because in cold boot it reached 25 seconds and until now I managed to get it down to 8 seconds without text mode and keeping the graphic mode without hibernating. My SSD is a SanDisk U100 from 2012, 24GB, it's a low-end
systemd-analyze time
Startup finished in 1.317s (firmware) + 1.020s (loader) + 3.124s (kernel) + 2.313s (userspace) = 7.776s
graphical.target reached after 2.266s in userspace.
systemd-analyze critical-chain
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 @2.266s
└─tdm.service @2.257s +6ms
└─systemd-user-sessions.service @2.239s +11ms
└─network.target @2.203s
└─NetworkManager.service @2.003s +199ms
└─dbus.service @1.820s +178ms
└─basic.target @1.790s
└─sockets.target @1.790s
└─dbus.socket @1.790s
└─sysinit.target @1.777s
└─apparmor.service @1.516s +261ms
└─local-fs.target @1.515s
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.525s
└─local-fs-pre.target @574ms
└─keyboard-setup.service @378ms +195ms
└─systemd-journald.socket @371ms
└─-.mount @350ms
└─-.slice @350ms
Offline
Pages: 1