Stránka 1 z 1
Zamrzlý počítač po čisté instalaci
Napsal: 26 říj 2025, 19:12
od Darina Lakovičová
Poraďte pánové pls. Čistá instalace Mint 22.2.
Udělám všechny updaty, nastavím si plochu a doinstaluji programy které budu potřebovat.
Potom mi Mint zamrzne. Mohu hýbat pouze myší. Nejde mi PC nijak vypnout.
Kdo by mi doporučoval, vypnout ho natvrdo tak tomu řeknu pouze toto.
Dnes jsem to dvakrát udělala. Výsledek byl, že počítač nenajel a jen zahlásil myšmaš chyby na boot disku.
Musela jsem provádět dvakrát čistou instalaci. Proto ho nechci natvrdo vypínat než se ke mě dostane nějaká rada.
Prozatím by mi stačilo jen poradit jak ho vypnout.
Potom ho zapnu, spustím disgnostiky a hodím to sem.
Děkuji vám.
Re: Zamrzlý počítač po čisté instalaci
Napsal: 26 říj 2025, 20:19
od alfisko
Skús ctrl+alt+F1 pokiaľ to zareaguje objaví sa terminál. Tam sudo shutdown now.
Keď potrebujem natvrdo vypnúť tak držím tlačítko až kým sa PC nevypne a ešte sa mi nestalo že by to potom nenabehlo. Keď nič, tak to bude problém hardvéru.
Re: Zamrzlý počítač po čisté instalaci
Napsal: 26 říj 2025, 20:44
od Darina Lakovičová
Povedlo se. Díky. Teď testy.
Kód: Vybrat vše
vaxy@vaxy:~$ systemd-analyze
Startup finished in 27.756s (firmware) + 5.170s (loader) + 5.652s (kernel) + 48.001s (userspace) = 1min 26.581s
graphical.target reached after 47.674s in userspace.
vaxy@vaxy:~$ systemd-analyze blame
20.938s blueman-mechanism.service
17.016s NetworkManager.service
10.303s dev-sdb1.device
8.895s accounts-daemon.service
8.792s udisks2.service
7.412s ModemManager.service
5.368s systemd-journal-flush.service
5.101s apparmor.service
4.813s power-profiles-daemon.service
4.762s rsyslog.service
4.747s polkit.service
4.604s avahi-daemon.service
4.584s NetworkManager-wait-online.service
4.242s bluetooth.service
4.210s dbus.service
4.210s e2scrub_reap.service
4.209s gpu-manager.service
3.844s wpa_supplicant.service
3.649s thermald.service
3.328s lvm2-monitor.service
3.087s cups.service
2.979s ubuntu-system-adjustments.service
2.942s systemd-tmpfiles-setup.service
2.647s systemd-tmpfiles-setup-dev-early.service
2.645s grub-common.service
2.142s systemd-resolved.service
1.982s systemd-udevd.service
1.637s plymouth-start.service
1.598s systemd-modules-load.service
1.473s systemd-udev-trigger.service
1.438s keyboard-setup.service
1.389s grub-initrd-fallback.service
1.343s lightdm.service
1.331s plymouth-quit-wait.service
1.200s systemd-logind.service
1.180s systemd-sysctl.service
1.008s systemd-random-seed.service
970ms systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service
855ms lm-sensors.service
650ms systemd-journald.service
488ms switcheroo-control.service
377ms systemd-rfkill.service
348ms systemd-binfmt.service
346ms user@1000.service
327ms ufw.service
324ms casper-md5check.service
308ms systemd-remount-fs.service
270ms finalrd.service
245ms upower.service
244ms systemd-timesyncd.service
228ms console-setup.service
224ms plymouth-read-write.service
198ms kerneloops.service
185ms flatpak-system-helper.service
154ms setvtrgb.service
121ms dev-hugepages.mount
120ms dev-mqueue.mount
118ms sys-kernel-debug.mount
117ms sys-kernel-tracing.mount
113ms kmod-static-nodes.service
110ms modprobe@configfs.service
106ms modprobe@drm.service
103ms modprobe@fuse.service
78ms boot-efi.mount
69ms systemd-update-utmp.service
66ms proc-sys-fs-binfmt_misc.mount
60ms rtkit-daemon.service
60ms systemd-user-sessions.service
11ms alsa-restore.service
10ms systemd-tmpfiles-setup-dev.service
9ms user-runtime-dir@1000.service
9ms systemd-update-utmp-runlevel.service
7ms modprobe@efi_pstore.service
7ms sys-kernel-config.mount
6ms openvpn.service
6ms modprobe@loop.service
5ms sys-fs-fuse-connections.mount
4ms modprobe@dm_mod.service
1ms blk-availability.service
vaxy@vaxy:~$ 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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.ser>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.serv>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.servic>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @1>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.7>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.79>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s >
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970>
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
~
~
~
lines 1-20/20 (END)
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 @47.674s
└─multi-user.target @47.674s
└─kerneloops.service @47.475s +198ms
└─network-online.target @47.305s
└─NetworkManager-wait-online.service @42.720s +4.584s
└─NetworkManager.service @25.692s +17.016s
└─dbus.service @21.464s +4.210s
└─basic.target @21.382s
└─sockets.target @21.382s
└─uuidd.socket @21.382s
└─sysinit.target @21.331s
└─systemd-resolved.service @19.189s +2.142s
└─systemd-tmpfiles-setup.service @16.233s +2.942s
└─local-fs.target @15.948s
└─boot-efi.mount @15.869s +78ms
└─systemd-fsck@dev-disk-by\x2duuid-225F\x2dE03D.service @14.798s +970ms
└─dev-disk-by\x2duuid-225F\x2dE03D.device @14.762s
Myslela jsem, že ten poslední příkaz se vypsal několikrát stejně ale není tomu tak. Není stejný a proto ho sem dávám celý ve své mega délce.
Re: Zamrzlý počítač po čisté instalaci
Napsal: 27 říj 2025, 12:33
od menom
.
Ten start systemu vypada na bezny standard pri plotnovom disku. Asi mrknut na to cez program Disky (Disks).
.
Re: Zamrzlý počítač po čisté instalaci
Napsal: 27 říj 2025, 12:59
od alfisko
Ešte pozrieť dmesg a /var/log/syslog že či sa tam nepíše že kde je chyba. Cez ten terminal.