Sorry @mbod ! It was initially @rottinhell
But as I have the same issue, I thought I can join in (as an open discussion or brainstorming)
I’m sorry, I surely didn’t mean to interrupt or create a confusion. I just thought there is no point I go create another thread with the same topic.
Just ignore my posts and carry on. I’ll just listen.
Please accept my sincere apologies
mbod
October 2, 2021, 7:34am
22
Why do you have entries for USB, DVD and Network? From my point of view there is no need for it. Why dont you just take them out and try again?
Have you checked your boot order in bios menu? Are you on uefi or legacy system? AFAIK this command is for uefi bootloaders.
These are default set in firmware setting (bios menu). No matter how i change inside the os, it will be the same unless i change it in bios. And i dont know how to delete entries from bios, i dont think i even want to to that.
mbod
October 2, 2021, 8:47am
24
I would say this is the boot order in the BIOS. It would disable all devices in the BIOS boot menu except for the one which holds your grub.
I am on a old hpg60-ous and this is my boot time,
4.977s dev-sda4.device
3.561s ldconfig.service
1.424s systemd-random-seed.service
960ms polkit.service
767ms systemd-sysusers.service
699ms systemd-remount-fs.service
596ms systemd-udevd.service
593ms systemd-fsck@dev-disk-by\x2duuid-52b3782a\x2d7ba1\x2d4fb3\x2d97b5\x2d3e9f350f4f04.service
575ms boot.mount
521ms NetworkManager.service
387ms systemd-logind.service
353ms user@1000.service
322ms modprobe@fuse.service
245ms systemd-tmpfiles-setup.service
242ms systemd-udev-trigger.service
234ms systemd-rfkill.service
209ms modprobe@drm.service
204ms wpa_supplicant.service
201ms lvm2-monitor.service
182ms dev-disk-by\x2duuid-4b91e353\x2d7887\x2d4a33\x2d93fd\x2d9748fe6edc0a.swap
131ms systemd-journald.service
126ms systemd-tmpfiles-setup-dev.service
111ms systemd-journal-catalog-update.service
97ms systemd-sysctl.service
76ms systemd-update-utmp.service
73ms systemd-backlight@backlight:acpi_video0.service
61ms rtkit-daemon.service
39ms sys-kernel-tracing.mount
39ms dev-hugepages.mount
39ms sys-kernel-config.mount
37ms dev-mqueue.mount
36ms sys-kernel-debug.mount
35ms systemd-journal-flush.service
32ms kmod-static-nodes.service
31ms alsa-restore.service
29ms modprobe@configfs.service
24ms systemd-update-done.service
14ms user-runtime-dir@1000.service
13ms systemd-user-sessions.service
5ms tmp.mount
3ms sys-fs-fuse-connections.mount
[ndm@ndm-server ~]$ 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 @13.658s
└─sddm.service @13.657s
└─systemd-user-sessions.service @13.640s +13ms
└─network.target @13.627s
└─NetworkManager.service @13.105s +521ms
└─dbus.service @13.098s
└─basic.target @13.089s
└─sockets.target @13.089s
└─dbus.socket @13.089s
└─sysinit.target @13.087s
└─systemd-update-done.service @13.062s +24ms
└─ldconfig.service @9.498s +3.561s
└─local-fs.target @9.496s
└─boot.mount @8.920s +575ms
└─systemd-fsck@dev-disk-by\x2duuid-52b3782a\x2d7ba1\x2d4fb3\x2d97b5\x2d3e9f350f4f04.service @8.325s +593ms
└─dev-disk-by\x2duuid-52b3782a\x2d7ba1\x2d4fb3\x2d97b5\x2d3e9f350f4f04.device @8.323s
try stacer.
system
Closed
October 4, 2021, 11:49am
26
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.