Guten Morgen Ubuntuusers Forum, ich habe seit mehreren Monaten nun folgendes Problem das mein Ubuntu länger als 90 Sekunden zum booten benötigt, zuerst dachte ich das die NVidia Driver (595) wieder mal kaputt sind, weswegen ich auf 580 open gewechselt bin (hatte damit keine Probleme mit meiner Laptop rtx 3060).
Hat das Problem aber nicht gelöst, weswegen ich ein bios Upgrade gemacht habe, was auch nicht gebracht hat (warscheinlich hatte dies das Problem schlimmer gemacht, kann mich aber nicht mehr erinnern)
Zudem hatte ich Probleme mit dem Audio, manchmal tauchte keine Mikro/Lautsprecher auf, manchmal nur die "nicht funktionierende" Raptor Lake Audiakarte.
KI, auch schon befragt, keine Lösung in Sicht, jedenfalls habe ich aber auch mein Ubuntu Cinnamon massiv modifiziert (bin auf KDE Plasma (Wayland) gewechselt) weswegen ich fragen wollte ob man die audio configs resetten könnte, hier sind ein paar Logs
- $ sudo systemd-analyze blame
27.745s locate.service
2.708s plymouth-quit-wait.service
1.115s modprobe@efi_pstore.service
1.055s snap-bare-5.mount
1.053s snap-core-17284.mount
1.052s snap-core-17292.mount
1.051s snap-core18-2979.mount
1.050s snap-core18-2999.mount
1.049s snap-core20-2769.mount
1.048s snap-core20-2866.mount
1.047s snap-core22-2339.mount
1.046s snap-core22-2411.mount
1.045s snap-core24-1587.mount
1.044s snap-core24-1643.mount
1.043s snap-cups-1183.mount
1.043s snap-cups-1197.mount
1.042s snap-dotnet\x2druntime\x2d70-37.mount
1.041s snap-dotnet\x2druntime\x2d70-43.mount
1.039s snap-dust-19.mount
1.038s snap-firefox-8339.mount
1.036s snap-firefox-8364.mount
1.035s snap-gnome\x2d3\x2d28\x2d1804-198.mount
1.034s snap-gnome\x2d3\x2d38\x2d2004-143.mount
1.033s snap-gnome\x2d42\x2d2204-226.mount
1.032s snap-gnome\x2d42\x2d2204-247.mount
1.031s snap-gnome\x2d46\x2d2404-145.mount
1.030s snap-gnome\x2d46\x2d2404-153.mount
1.029s snap-gtk2\x2dcommon\x2dthemes-13.mount
1.028s snap-gtk\x2dcommon\x2dthemes-1535.mount
1.027s snap-josm-143.mount
1.026s snap-josm-146.mount
1.025s snap-kf6\x2dcore24-34.mount
1.023s snap-kf6\x2dcore24-36.mount
1.023s snap-libinput-127.mount
1.022s snap-libinput-138.mount
1.020s snap-lxqt\x2dsupport\x2dcore24-13.mount
1.019s snap-lxqt\x2dsupport\x2dcore24-16.mount
1.018s snap-mesa\x2d2404-1165.mount
1.017s snap-mesa\x2dcore22-498.mount
1.016s snap-mesa\x2dcore22-504.mount
1.015s snap-qt5\x2dcore20-23.mount
1.014s snap-qt5\x2dcore20-24.mount
1.013s snap-snapd-26382.mount
1.012s snap-snapd-26865.mount
1.011s snap-ubuntu\x2dmake-1050.mount
1.010s snap-ubuntu\x2dmake-1067.mount
1.008s snap-vulnapi-108.mount
1.008s snap-vulnapi-112.mount
827ms thermald.service
816ms snapd.seeded.service
692ms snapd.service
641ms NetworkManager.service
606ms docker.service
340ms blueman-mechanism.service
295ms user@1000.service
243ms udisks2.service
221ms waydroid-container.service
207ms dev-nvme0n1p5.device
206ms cups.service
196ms polkit.service
192ms accounts-daemon.service
188ms containerd.service
182ms networkd-dispatcher.service
174ms hardinfo2.service
167ms lm-sensors.service
160ms update-notifier-download.service
151ms avahi-daemon.service
149ms systemd-journal-flush.service
149ms bluetooth.service
141ms dbus.service
135ms lxc-net.service
133ms apport.service
127ms apparmor.service
124ms grub2-common.service
118ms grub-common.service
116ms systemd-logind.service
116ms gpu-manager.service
115ms virtualbox.service
112ms switcheroo-control.service
110ms apport-autoreport.service
109ms virtlogd.service
109ms upower.service
108ms rsyslog.service
103ms systemd-machined.service
100ms systemd-udev-trigger.service
96ms clamav-daemon.service
95ms devolonetsvc.service
92ms sysstat.service
91ms systemd-hostnamed.service
90ms ModemManager.service
86ms kdump-tools.service
85ms lxcfs.service
77ms libvirt-guests.service
74ms dpkg-db-backup.service
74ms e2scrub_reap.service
74ms sysstat-collect.service
73ms systemd-resolved.service
71ms snapd.apparmor.service
68ms systemd-journald.service
67ms kerneloops.service
65ms systemd-binfmt.service
64ms systemd-modules-load.service
64ms power-profiles-daemon.service
60ms systemd-udevd.service
59ms systemd-oomd.service
57ms mono-xsp4.service
52ms smartmontools.service
51ms lxc.service
50ms lvm2-monitor.service
49ms colord.service
48ms dev-loop5.device
45ms dev-loop4.device
45ms gdm.service
44ms systemd-tmpfiles-setup.service
44ms dev-loop3.device
43ms proc-sys-fs-binfmt_misc.mount
41ms virtlockd.service
41ms dev-loop7.device
40ms dev-loop2.device
40ms keyboard-setup.service
38ms dev-loop24.device
37ms systemd-timesyncd.service
36ms dev-loop15.device
35ms dev-loop13.device
35ms dev-loop6.device
35ms dev-loop37.device
34ms libvirtd.service
33ms dev-loop27.device
33ms systemd-backlight@backlight:nvidia_0.service
33ms dev-loop41.device
33ms dev-loop1.device
31ms dev-loop32.device
31ms dev-loop17.device
30ms dev-loop9.device
30ms dev-loop42.device
30ms dev-loop0.device
30ms console-setup.service
30ms dev-loop26.device
30ms setvtrgb.service
30ms dev-loop28.device
30ms dev-loop12.device
29ms dev-loop23.device
29ms dev-loop10.device
29ms finalrd.service
29ms dev-loop21.device
29ms dev-loop16.device
29ms dev-loop34.device
28ms dev-loop39.device
28ms systemd-remount-fs.service
27ms dev-loop38.device
27ms dev-loop29.device
27ms dev-loop19.device
27ms dev-loop11.device
27ms dev-loop25.device
27ms dev-loop18.device
26ms clamav-daemon.socket
26ms tmp.mount
26ms dev-loop22.device
25ms dev-loop35.device
24ms alsa-restore.service
24ms dev-loop30.device
24ms dev-loop31.device
23ms dev-loop36.device
23ms plymouth-start.service
23ms atd.service
22ms dev-loop8.device
22ms dev-loop43.device
22ms blk-availability.service
22ms dev-loop40.device
22ms qemu-kvm.service
22ms dev-loop20.device
21ms dev-loop14.device
21ms chrome-remote-desktop.service
19ms binfmt-support.service
19ms plymouth-read-write.service
17ms wpa_supplicant.service
17ms dev-loop33.device
16ms dev-loop44.device
16ms dev-hugepages.mount
15ms openvpn.service
14ms rtkit-daemon.service
14ms dev-mqueue.mount
14ms systemd-random-seed.service
13ms ufw.service
13ms systemd-tmpfiles-setup-dev-early.service
13ms systemd-sysctl.service
12ms run-lock.mount
12ms systemd-rfkill.service
12ms systemd-user-sessions.service
11ms sys-kernel-debug.mount
11ms docker.socket
11ms sys-kernel-tracing.mount
11ms systemd-udev-load-credentials.service
10ms grub-initrd-fallback.service
9ms libvirtd.socket
8ms kmod-static-nodes.service
8ms snapd.socket
7ms modprobe@configfs.service
7ms modprobe@drm.service
7ms user-runtime-dir@1000.service
7ms systemd-tmpfiles-setup-dev.service
6ms modprobe@fuse.service
6ms sys-fs-fuse-connections.mount
5ms sys-kernel-config.mount- journalctl -xb im Anhang line 5017 passiert warscheinlich der Sprung
- und ein Bild des ttys während den 90s hang, einmal nvidia 595 und 580 open im Anhang.
LG Michael