Hi ich habe ein HP Elitebook 8470p was sehr Lam ist es braucht ungefähr beim Start 6 min bis der CPU erträglich ist. werde morgen die Zeit stoppen,kann mir jemand sagen wie ich die Kartoffel schneller mache?
Ubuntu startet extrem langsam
Anmeldungsdatum: Beiträge: 68 Wohnort: irgendwo in nirgendwo |
|
Anmeldungsdatum: Beiträge: 4378 Wohnort: Göttingen |
Lies Dir mal systemd/systemd-analyze durch. |
(Themenstarter)
Anmeldungsdatum: Beiträge: 68 Wohnort: irgendwo in nirgendwo |
so mal analysiert: bgf@bgf-HP-EliteBook-8470p:~$ systemd-analyze Startup finished in 5.632s (kernel) + 2min 23.861s (userspace) = 2min 29.494s graphical.target reached after 2min 23.522s in userspace. bgf@bgf-HP-EliteBook-8470p:~$ systemd-analyze blame 1min 33.220s plymouth-quit-wait.service 30.783s snapd.service 23.068s dev-sda1.device 20.844s logrotate.service 18.926s fwupd.service 18.434s dev-loop31.device 18.159s dev-loop55.device 18.125s dev-loop54.device 17.975s dev-loop39.device 17.963s dev-loop57.device 17.460s dev-loop53.device 17.373s NetworkManager-wait-online.service 17.318s dev-loop38.device 17.310s dev-loop45.device 17.309s dev-loop32.device 17.306s dev-loop48.device 16.825s accounts-daemon.service 16.753s dev-loop47.device 16.712s dev-loop51.device 16.572s dev-loop36.device 16.221s dev-loop18.device 16.183s dev-loop43.device 16.051s dev-loop56.device 15.664s dev-loop49.device 15.587s dev-loop52.device 15.460s dev-loop50.device 15.450s dev-loop46.device 15.085s dev-loop35.device 15.003s dev-loop37.device 14.866s dev-loop40.device 14.581s dev-loop34.device 14.560s dev-loop41.device 14.342s dev-loop42.device 14.274s dev-loop44.device 14.050s dev-loop29.device 13.834s udisks2.service 13.677s dev-loop25.device 13.673s dev-loop19.device 13.672s dev-loop22.device 13.670s dev-loop30.device 13.669s dev-loop33.device 13.352s systemd-journal-flush.service 12.814s dev-loop27.device 12.731s dev-loop28.device 12.534s dev-loop26.device 12.479s systemd-tmpfiles-setup.service 12.052s dev-loop1.device 11.863s dev-loop23.device 11.675s dev-loop24.device 11.658s dev-loop21.device 11.491s dev-loop16.device 11.302s dev-loop8.device 11.061s iio-sensor-proxy.service 11.054s avahi-daemon.service 11.051s bluetooth.service 11.026s dev-loop20.device 11.023s dev-loop17.device 10.980s dbus.service 10.964s vboxdrv.service 10.954s power-profiles-daemon.service 10.933s dev-loop14.device 10.706s dev-loop15.device 10.347s dev-loop12.device 10.240s polkit.service 9.558s dev-loop11.device 9.542s ModemManager.service 9.500s switcheroo-control.service 9.495s systemd-logind.service 9.493s thermald.service 9.456s dev-loop13.device 9.249s dev-loop9.device 9.240s dev-loop10.device 9.098s dev-loop6.device 8.604s nginx.service 7.859s cups.service 7.642s dev-loop5.device 7.380s dev-loop7.device 7.209s snapd.apparmor.service 7.014s dev-loop3.device 6.971s dev-loop0.device 6.518s apport-autoreport.service 6.129s dev-loop2.device 6.112s gdm.service 6.070s systemd-udevd.service 5.710s smartmontools.service 5.345s snapd.seeded.service 4.925s snap-asciiquarium-19.mount 4.662s snap-asciiquarium-42.mount 4.638s snap-bare-5.mount 4.538s snap-canonical\x2dlivepatch-190.mount 4.528s snap-canonical\x2dlivepatch-196.mount 4.440s snap-code-125.mount 4.428s snap-cool\x2dretro\x2dterm-150.mount 4.400s snap-core-14784.mount 4.391s snap-core-14946.mount 4.271s snap-core18-2714.mount 4.268s snap-core18-2721.mount 4.259s snap-core20-1828.mount 4.246s snap-core20-1852.mount 3.959s snap-core22-583.mount 3.957s snap-core22-607.mount 3.827s rsyslog.service 3.804s snap-firefox-2487.mount 3.766s snap-firefox-2559.mount 3.712s snap-ghettorecorder-11.mount 3.707s snap-gnome\x2d3\x2d28\x2d1804-161.mount 3.553s snap-gnome\x2d3\x2d28\x2d1804-194.mount 3.472s snap-gnome\x2d3\x2d38\x2d2004-119.mount 3.468s snap-gnome\x2d3\x2d38\x2d2004-137.mount 3.448s snap-gnome\x2d42\x2d2204-65.mount 3.201s snap-gnome\x2d42\x2d2204-68.mount 3.180s snap-gnome\x2dsystem\x2dmonitor-178.mount 3.178s snap-gnome\x2dsystem\x2dmonitor-181.mount 3.151s snap-gtk\x2dcommon\x2dthemes-1534.mount 2.925s snap-gtk\x2dcommon\x2dthemes-1535.mount 2.875s NetworkManager.service 2.743s grub-common.service 2.739s apparmor.service 2.646s apport.service 2.561s snap-hunspell\x2ddictionaries\x2d1\x2d7\x2d2004-2.mount 2.536s snap-kde\x2dframeworks\x2d5\x2dqt\x2d5\x2d15\x2d3\x2dcore20-8.mount 2.213s snap-minetest-1828.mount 2.138s lxc-net.service 1.986s gpu-manager.service 1.948s gpm.service 1.946s snap-ncspot-181.mount 1.914s plymouth-start.service 1.854s snap-node-6895.mount 1.852s snap-node-7346.mount 1.819s snap-qr\x2dcode\x2dgenerator\x2ddesktop-304.mount 1.807s snap-retroarch-1839.mount 1.800s snap-retroarch-2005.mount 1.764s update-notifier-download.service 1.723s snap-reversu-1.mount 1.629s lm-sensors.service 1.588s chrome-remote-desktop.service 1.582s e2scrub_reap.service 1.538s wpa_supplicant.service 1.463s packagekit.service 1.403s snap-snap\x2dstore-599.mount 1.386s snap-snap\x2dstore-638.mount 1.383s snap-snapd-18357.mount 1.369s snap-snapd-18596.mount 1.266s systemd-resolved.service 1.213s sysfsutils.service 1.184s systemd-sysusers.service 1.159s systemd-modules-load.service 1.110s systemd-tmpfiles-setup-dev.service 1.079s snap-snapd\x2ddesktop\x2dintegration-49.mount 1.017s colord.service 983ms snap-snapd\x2ddesktop\x2dintegration-57.mount 952ms snap-spotify-60.mount 941ms snap-spotify-63.mount 896ms snap-spt-289.mount 852ms snap-suligap\x2dpython3\x2dqrcode-4.mount 825ms upower.service 808ms binfmt-support.service 771ms keyboard-setup.service 741ms systemd-sysctl.service 699ms systemd-random-seed.service 637ms systemd-backlight@backlight:intel_backlight.service 625ms snap-telegram\x2ddesktop-4627.mount 623ms snap-telegram\x2ddesktop-4654.mount 613ms user@1000.service 609ms snap-the\x2dpowder\x2dtoy-44.mount 606ms snap-the\x2dpowder\x2dtoy-46.mount 598ms snap-vlc-2344.mount 580ms snap-vlc-3078.mount 567ms snap-wine\x2dplatform\x2d6\x2dstable-19.mount 554ms lxc.service 533ms snap-wine\x2dplatform\x2druntime-342.mount 527ms snap-wine\x2dplatform\x2druntime-343.mount 515ms openvpn.service 450ms grub-initrd-fallback.service 425ms systemd-udev-trigger.service 323ms systemd-oomd.service 322ms systemd-journald.service 302ms dev-hugepages.mount 300ms dev-mqueue.mount 300ms modprobe@drm.service 298ms sys-kernel-debug.mount 296ms sys-kernel-tracing.mount 283ms swapfile.swap 273ms systemd-user-sessions.service 272ms setvtrgb.service 244ms systemd-timesyncd.service 233ms ufw.service 230ms kmod-static-nodes.service 229ms modprobe@configfs.service 226ms modprobe@fuse.service 200ms rtkit-daemon.service 199ms snap.canonical-livepatch.canonical-livepatchd.service 185ms plymouth-read-write.service 176ms kerneloops.service 169ms blueman-mechanism.service 162ms vboxautostart-service.service 162ms vboxballoonctrl-service.service 159ms systemd-remount-fs.service 132ms proc-sys-fs-binfmt_misc.mount 118ms systemd-update-utmp.service 111ms console-setup.service 74ms virtualbox.service 63ms vboxweb-service.service 52ms modprobe@chromeos_pstore.service 49ms var-snap-firefox-common-host\x2dhunspell.mount 23ms snap-code-126.mount 21ms user-runtime-dir@1000.service 9ms alsa-restore.service 8ms modprobe@efi_pstore.service 7ms systemd-update-utmp-runlevel.service 7ms modprobe@pstore_blk.service 4ms modprobe@pstore_zone.service 3ms modprobe@ramoops.service 3ms systemd-rfkill.service 3ms sys-kernel-config.mount 3ms sys-fs-fuse-connections.mount 2ms snapd.socket bgf@bgf-HP-EliteBook-8470p:~$ 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 @2min 23.522s └─multi-user.target @2min 23.522s └─plymouth-quit-wait.service @50.301s +1min 33.220s └─systemd-user-sessions.service @50.004s +273ms └─network.target @49.729s └─NetworkManager.service @46.852s +2.875s └─dbus.service @35.808s +10.980s └─basic.target @35.776s └─sockets.target @35.776s └─cups.socket @43.039s └─sysinit.target @35.631s └─systemd-resolved.service @34.363s +1.266s └─systemd-tmpfiles-setup.service @21.813s +12.479s └─systemd-journal-flush.service @8.417s +13.352s └─systemd-remount-fs.service @8.232s +159ms └─systemd-journald.socket @7.929s └─-.mount @7.901s └─-.slice @7.901s und hier hab ich selber gestoppt: m:ss m=Minute s=Sekunde 0:00 Tastendruck 0:04 Ubuntu startet Boot 2:06 Anmeldebildschirm erscheint 3:27 Oberfläche zusehen 4:03 Startprogramme gestartet ruckelig 6:45 CPU ungefähr erträglich .... - 3:27 100% CPU 3:27 - 4:50 70% CPU 4:50 - 5:05 50% CPU 5:05 - 5:20 20% - 30% CPU Verzögerung des Tastendrucks zum öffnen des Startmenüs nach 5:00 : 0:06 |
Anmeldungsdatum: Beiträge: 2209 |
Könnte einfach Altersschwäche sein bei 8470p... ☹
Mach' auf jedenfall Backup! 💡 |
(Themenstarter)
Anmeldungsdatum: Beiträge: 68 Wohnort: irgendwo in nirgendwo |
uaserdem er leuft auchtotal lam |
Supporter, Wikiteam
Anmeldungsdatum: Beiträge: 17584 Wohnort: in deinem Browser, hier auf dem Bildschirm |
Plymouth abstellen. |
(Themenstarter)
Anmeldungsdatum: Beiträge: 68 Wohnort: irgendwo in nirgendwo |
Habs a mal gemacht es gibt kein Wesentlichen unterschied. |
Anmeldungsdatum: Beiträge: 3991 |
Platte geprüft? Du kannst ja mal die Smart-Werte mit den Smartmontools auslesen. |
Anmeldungsdatum: Beiträge: 2209 |
Plymouth dekativieren, zeigt direkt am Bildschirm, wo es hakt und humpelt. Dient also mehr der bequemen Fehleranaylyse. Die anderen Punkte sind da wichtiger und zielführender. Eine sterbende, mechanische Platte ist da sehr wahrscheinlich. SSD für 30,- Euronen ist an dieser Stelle hilfreich. 👍 |