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
Hi, I just wanted to say that in the end I left everything as original as possible in the Q40S, and the truth is that it's brutally fast.
I just downloaded the MX Tools app.
~$ systemd-analyze
Startup finished in 1.319s (firmware) + 976ms (loader) + 2.083s (kernel) + 2.632 s (userspace) = 7.011s
graphical.target reached after 2.580s 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.580s
└─udisks2.service @2.165s +414ms
└─basic.target @2.139s
└─sockets.target @2.138s
└─dbus.socket @2.138s
└─sysinit.target @2.132s
└─apparmor.service @1.874s +258ms
└─local-fs.target @1.872s
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.891s
└─local-fs-pre.target @864ms
└─keyboard-setup.service @673ms +190ms
└─systemd-journald.socket @664ms
└─-.mount @638ms
└─-.slice @638ms
Congratulations to the creators of Q40S for such an operating system, the truth is that it is very complete, stable and light
I recommend earlyoom.service and irqbalance.service to make the system lighter because they make the processes easier.
as the kernel OOM-KILLER is rather stupid and mean.
Offline
~$ systemd-analyze
Startup finished in 1.319s (firmware) + 976ms (loader) + 2.083s (kernel) + 2.632s (userspace) = 7.011s
graphical.target reached after 2.580s in userspace.
Here in contrary it looks like:
Startup finished in 3.200s (kernel) + 6.990s (userspace) = 10.190s
graphical.target reached after 6.963s in userspace.
Unfortunately it looses more than 6 second with network stuff, probably WiFi:
...
─network-online.target @6.934s
└─NetworkManager-wait-online.service @545ms +6.387s
but it isn't possible do deactivate WiFi in the BIOS.
Is it possible to set WiFi deactivated in Q4(Gemini) per default, and activate the device only on demand?
Last edited by FlexQ4 (2025-05-21 22:17)
Offline
Yes, but make sure it doesn't affect other applications while you boot the PC.
Here's the command:
sudo systemctl disable NetworkManager-wait-online.service
Offline
Nice, thanks josek! systemd-analyze now states:
Startup finished in 3.161s (kernel) + 1.837s (userspace) = 4.999s
graphical.target reached after 1.518s in userspace
So i've gained about 5 seconds - and i can see no disadvantage of disabling the "NetworkManager-wait-online.service": both, cabled an WLan work as usual if activate / switch them on.
But, tbh: it doesn't make any difference for the real boot-up time at all - 25 sec in both cases, the service enabled or disabled...
Anyway: Cheers!
Last edited by FlexQ4 (2025-05-22 22:30)
Offline
I'm glad it worked for you, look if you have an SSD or HDD it's not always the disk, because one thing is the boot and another thing is the desktop environment, be it Trinity, Plasma, LXDE etc, another is the services that run in the background, your sound card, also video, nvidia or intel, also the wifi, it has several drives, the programs, also all that you have to keep in mind that it adds up, until reaching 25 or 40 seconds
I just reinstalled grub because today I uninstalled it, that is, it was deleted and I think it was a bug because I only wanted to uninstall chrome and there it was deleted, luckily I realized because I saw the package history and I didn't turn off the laptop and I took advantage of cleaning my EFI or sda1 partition and the truth is that I am removing more unnecessary things from the system to make it lighter and I am learning more about Linux to get the most out of it and reduce the RAM consumption at 200 or 300MB because in the end each update sometimes slows down the PC but every second always counts.
Offline
I'm glad it worked for you, look if you have an SSD or HDD it's not always the disk, because one thing is the boot and another thing is the desktop environment, be it Trinity, Plasma, LXDE etc, another is the services that run in the background, your sound card, also video, nvidia or intel, also the wifi, it has several drives, the programs, also all that you have to keep in mind that it adds up, until reaching 25 or 40 seconds
Thanks again for your annotations, josek!
Aamof my system (mb) does feature quite a lot of hw stuff for the OS to handle at startup: Not 1 but 2 wired network devices, plus Wifi, plus bluetooth, several partitions (2 additional OS's, plus ntfs data partitions) on the ssd, a CD drive, sound etc.
So i really don't complain about the 25 second boot-up time (to TDE) at all.
On the other hand side: Windows 7 gets the bootup done in about 15 seconds merely on the same system - that's why i've got an eye of it.
And i totally agree with you: every update and new release, of everything: needs more RAM, disk space, CPU power... which requires a lot efforts to control and bridle ;-)
Offline
Pages: 1