Langsamer Boot

Hallo Zusammen und vielen Dank für die Aufnahme.
Ich habe ein Dual-Boot System (EndeavourOS und Windows). Leider bootet mein System sehr langsam:

Startup finished in 3.600s (firmware) + 8.295s (loader) + 1.228s (kernel) + 3.348s (initrd) + 27.247s (userspace) = 43.721s 
graphical.target reached after 27.246s in userspace.
System:
  Host: marcel-endeavour Kernel: 6.1.56-1-lts arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.8 Distro: EndeavourOS
Machine:
  Type: Laptop System: HP product: OMEN by HP Laptop v: N/A
    serial: <superuser required>
  Mobo: HP model: 8469 v: 68.21 serial: <superuser required> UEFI: AMI
    v: F.09 date: 04/24/2019
Battery:
  ID-1: BAT0 charge: 79.4 Wh (100.0%) condition: 79.4/79.4 Wh (100.0%)
CPU:
  Info: 6-core model: Intel Core i7-8750H bits: 64 type: MT MCP cache:
    L2: 1.5 MiB
  Speed (MHz): avg: 800 min/max: 800/4100 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia
    v: 535.113.01
  Device-3: Realtek HP Wide Vision HD Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 535.113.01
    renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
  API: Vulkan v: 1.3.264 drivers: nvidia surfaces: xcb,xlib
Audio:
  Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
  Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.1.56-1-lts status: kernel-api
  Server-1: PipeWire v: 0.3.81 status: active
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi
  IF: wlan0 state: up mac: 30:24:32:fc:3a:69
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: N/A
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
    type: USB
  Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
Drives:
  Local Storage: total: 1.03 TiB used: 95.17 GiB (9.1%)
  ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 119.24 GiB
  ID-2: /dev/sda vendor: HGST (Hitachi) model: HTS721010A9E630
    size: 931.51 GiB
Partition:
  ID-1: / size: 634.44 GiB used: 95.07 GiB (15.0%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 511 MiB used: 103.8 MiB (20.3%) fs: vfat
    dev: /dev/sda1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 45.0 C pch: 49.0 C mobo: N/A gpu: nvidia
    temp: 44 C
  Fan Speeds (rpm): N/A
Info:
  Processes: 329 Uptime: 13m Memory: total: 8 GiB available: 7.57 GiB
  used: 2.53 GiB (33.4%) Shell: Bash inxi: 3.3.30

Hab ihr eine Idee an was es liegt?
Treiber, Kernel, etc. sind eigentlich alle akutell.

Vielen Dank für Eure Hilfe!

LG

Helfen dir

systemd-analyze blame 

und

systemd-analyze critical-chain  

weiter? Ich finde diese Anleitung hier ganz gut:

Hallo milkytwix,

danke für die Anleitung:

Offensichtlich hängt es an der Festplatte bzw. kann es sein das Windows reinpfuscht?

17.745s dev-disk-by\x2ddiskseq-1\x2dpart1.device
17.745s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda-sda1.device
17.745s dev-disk-by\x2ddiskseq-1\x2dpart1.device
17.745s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda-sda1.device
17.745s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart1.device
17.745s dev-disk-by\x2dpartuuid-52635e48\x2d881c\x2d4dfc\x2daf97\x2d37393d90937f.device
17.745s dev-disk-by\x2did-ata\x2dHGST_HTS721010A9E630_JR1000BNK1TM1E\x2dpart1.device
17.745s dev-disk-by\x2did-wwn\x2d0x5000cca8e6eb1748\x2dpart1.device
17.745s dev-sda1.device
17.745s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart1.device
17.745s dev-disk-by\x2duuid-D14A\x2dBEDA.device
17.735s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart3.device
17.735s dev-disk-by\x2did-wwn\x2d0x5000cca8e6eb1748\x2dpart3.device
17.735s dev-disk-by\x2dpartlabel-endeavouros.device
17.735s dev-disk-by\x2duuid-c8e7ac34\x2d9445\x2d4e61\x2d85af\x2dca88494e68f8.device
17.735s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda-sda3.device
17.735s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart3.device
17.735s dev-disk-by\x2ddiskseq-1\x2dpart3.device
17.735s dev-disk-by\x2dpartuuid-bc09963b\x2dbb5a\x2d434b\x2dabee\x2d0abc6701085c.device
17.735s dev-sda3.device
17.735s dev-disk-by\x2did-ata\x2dHGST_HTS721010A9E630_JR1000BNK1TM1E\x2dpart3.device
17.735s dev-disk-by\x2dlabel-endeavouros.device
17.695s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart2.device
17.695s dev-disk-by\x2ddiskseq-1\x2dpart2.device
17.695s dev-disk-by\x2duuid-01D9EA4C8913CA90.device
17.695s dev-disk-by\x2did-ata\x2dHGST_HTS721010A9E630_JR1000BNK1TM1E\x2dpart2.device
17.695s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart2.device
17.695s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda-sda2.device
17.695s dev-disk-by\x2did-wwn\x2d0x5000cca8e6eb1748\x2dpart2.device
17.695s dev-disk-by\x2dpartuuid-9ce700b0\x2daa6b\x2d9c9e\x2d41e8\x2ddd36b40b42dc.device
17.695s dev-sda2.device
16.139s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
16.139s dev-nvme0n1p1.device
16.139s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
16.139s dev-disk-by\x2did-nvme\x2deui.00080d0400147b40\x2dpart1.device
16.139s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P\x2dpart1.device
16.139s dev-disk-by\x2dpartuuid-7cb7514e\x2d663e\x2d497a\x2d8336\x2d7a56c235f237.device
16.139s dev-disk-by\x2duuid-0C6AA66E6AA653EC.device
16.139s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P_1\x2dpart1.device
16.139s dev-disk-by\x2ddiskseq-2\x2dpart1.device
16.138s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1.device
16.138s dev-nvme0n1.device
16.138s dev-disk-by\x2did-nvme\x2deui.00080d0400147b40.device
16.138s dev-disk-by\x2ddiskseq-2.device
16.138s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
16.138s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P.device
16.138s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P_1.device
16.138s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P_1\x2dpart2.device
16.138s dev-disk-by\x2dpartlabel-Basi.device
16.138s dev-disk-by\x2did-nvme\x2deui.00080d0400147b40\x2dpart2.device
16.138s dev-disk-by\x2duuid-22F8276AF8273B83.device
16.138s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
16.138s dev-disk-by\x2dpartuuid-1f0bddf1\x2d80cc\x2d4cd8\x2dadf2\x2db2b9f9af0147.device
16.138s dev-nvme0n1p2.device
16.138s dev-disk-by\x2dlabel-Windows\x5cx20RE\x5cx20tools.device
16.138s dev-disk-by\x2ddiskseq-2\x2dpart2.device
16.138s dev-disk-by\x2did-nvme\x2dKBG30ZMV128G_TOSHIBA_58NPC43CP11P\x2dpart2.device
16.138s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
16.072s dev-disk-by\x2did-wwn\x2d0x5000cca8e6eb1748.device
16.072s dev-sda.device
16.072s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.device
16.072s dev-disk-by\x2did-ata\x2dHGST_HTS721010A9E630_JR1000BNK1TM1E.device
16.072s dev-disk-by\x2ddiskseq-1.device
16.072s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda.device
16.072s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0.device
15.391s sys-devices-platform-serial8250-tty-ttyS24.device
15.391s dev-ttyS24.device
15.391s sys-devices-platform-serial8250-tty-ttyS20.device
15.391s dev-ttyS20.device
15.390s dev-ttyS2.device
15.390s sys-devices-platform-serial8250-tty-ttyS2.device
15.390s dev-ttyS22.device
15.390s sys-devices-platform-serial8250-tty-ttyS22.device
15.389s sys-devices-platform-serial8250-tty-ttyS13.device
15.389s dev-ttyS13.device
15.389s dev-ttyS15.device
15.389s sys-devices-platform-serial8250-tty-ttyS15.device
15.388s sys-devices-platform-serial8250-tty-ttyS21.device
15.388s dev-ttyS21.device
15.388s dev-ttyS0.device
15.388s dev-ttyS19.device
15.388s sys-devices-platform-serial8250-tty-ttyS19.device
15.388s sys-devices-platform-serial8250-tty-ttyS0.device
15.388s sys-devices-platform-serial8250-tty-ttyS14.device
15.388s dev-ttyS14.device
15.388s dev-ttyS23.device
15.388s sys-devices-platform-serial8250-tty-ttyS23.device
15.388s sys-devices-platform-serial8250-tty-ttyS12.device
15.388s dev-ttyS12.device
15.387s dev-ttyS27.device
15.387s sys-devices-platform-serial8250-tty-ttyS27.device
15.387s dev-ttyS17.device
15.387s sys-devices-platform-serial8250-tty-ttyS17.device
15.387s dev-ttyS25.device
15.387s sys-devices-platform-serial8250-tty-ttyS25.device
15.387s dev-ttyS26.device
15.387s sys-devices-platform-serial8250-tty-ttyS26.device
15.386s sys-devices-platform-serial8250-tty-ttyS28.device
15.386s dev-ttyS28.device
15.386s sys-devices-platform-serial8250-tty-ttyS10.device
15.386s dev-ttyS11.device
15.386s dev-ttyS10.device
15.386s sys-devices-platform-serial8250-tty-ttyS11.device
15.386s dev-ttyS16.device
15.386s sys-devices-platform-serial8250-tty-ttyS16.device
15.386s dev-ttyS3.device
15.386s sys-devices-platform-serial8250-tty-ttyS3.device
15.385s dev-ttyS29.device
15.385s sys-devices-platform-serial8250-tty-ttyS29.device
15.384s dev-ttyS1.device
15.384s sys-devices-platform-serial8250-tty-ttyS1.device
15.384s dev-ttyS4.device
15.384s sys-devices-platform-serial8250-tty-ttyS4.device
15.384s dev-ttyS30.device
15.384s sys-devices-platform-serial8250-tty-ttyS30.device
15.382s dev-ttyS31.device
15.382s sys-devices-platform-serial8250-tty-ttyS31.device
15.382s dev-ttyS5.device
15.382s sys-devices-platform-serial8250-tty-ttyS5.device
15.382s sys-devices-platform-serial8250-tty-ttyS18.device
15.382s dev-ttyS18.device
15.382s sys-devices-platform-serial8250-tty-ttyS7.device
15.382s dev-ttyS7.device
15.381s dev-ttyS9.device
15.381s sys-devices-platform-serial8250-tty-ttyS9.device
15.380s dev-ttyS6.device
15.380s sys-devices-platform-serial8250-tty-ttyS6.device
15.379s dev-ttyS8.device
15.379s sys-devices-platform-serial8250-tty-ttyS8.device
15.199s sys-module-configfs.device


hey willkommen im Forum :enos:

Hast du das selbe mit dem Main Kernel oder nur bei LTS?

Hallo Joe!

Velen Dank. :slight_smile:
Ich habe auch schon den Kernel Version 6.5.6 ausprobiert und auch den Main-Kernel. Dauert eigentlich immer so lange, egal welcher Kernel.

War einen Versuch wert…
Die vollen Ausgaben der beiden Befehle würden mehr zeigen…

z.B. critical-chain gibt soetwas aus:

NetworkManager-wait-online.service @1.472s +4.750s

da könnte man sehen wo es hakt.
Wenn das nichts interessantes ausgibt kann immer noch der boot log analysiert werden… den aber besser nicht öffentlich posten:
journalctl -b -0 ist auch lang natürlich kann in eine Datei geschrieben werden:
journalctl -b -0 > ~/Dokumente/boot.log

Oder durchsuche den nach Fehlern:
journalctl -b -0 | grep error
journalctl -b -0 | grep failed
o.ä.

Kannst den auch auf meinem verschlüsseltem pastebin posten und mit password versehen… und mir den link und das passwort geben dann kann ich rein schauen…

Hier anbei die critical-chain Ausgabe:

graphical.target @24.621s
└─multi-user.target @24.619s
  └─cups.service @22.708s +1.908s
    └─network.target @22.679s
      └─wpa_supplicant.service @22.454s +221ms
        └─dbus.service @15.660s +798ms
          └─basic.target @15.635s
            └─sockets.target @15.633s
              └─dbus.socket @15.632s
                └─sysinit.target @15.578s
                  └─systemd-update-done.service @15.535s +42ms
                    └─ldconfig.service @14.138s +1.369s
                      └─local-fs.target @14.103s
                        └─boot-efi.mount @14.024s +77ms
                          └─systemd-fsck@dev-disk-by\x2duuid-D14A\x2dBEDA.service @11.941s +1.960s
                            └─dev-disk-by\x2duuid-D14A\x2dBEDA.device @584542y 2w 2d 20h 1min 44.642s +16.831s

und dann noch die journalctl

Okt 08 15:55:09 marcel-endeavour kernel: pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Okt 08 15:55:09 marcel-endeavour kernel: pcieport 0000:00:1d.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Okt 08 15:55:09 marcel-endeavour kernel: pcieport 0000:00:1d.7: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Okt 08 15:55:25 marcel-endeavour kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Okt 08 15:56:21 marcel-endeavour ksmserver[1283]: Qt: Session management error: networkIdsList argument is NULL
Okt 08 15:56:46 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 3 (BadWindow), sequence: 12035, resource id: 4194317, major code: 129 (SHAPE), minor code: 6 (Input)
Okt 08 15:57:34 marcel-endeavour plasmashell[1967]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 15:59:24 marcel-endeavour plasmashell[2539]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:02:17 marcel-endeavour plasma-discover[3542]: org.kde.plasma.libdiscover: error loading "packagekit-backend" "Die Bibliothek /usr/lib/qt/plugins/discover/packagekit-backend.so kann nicht geladen werden: (libpackagekitqt5.so.1: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)" QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","archreq":0,"className":"PackageKitBackendFactory","debug":false,"version":331520})
Okt 08 16:03:20 marcel-endeavour plasmashell[3874]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:04:47 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 152 (BadDamage), sequence: 28791, resource id: 6299156, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Okt 08 16:05:02 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 152 (BadDamage), sequence: 38503, resource id: 6299288, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Okt 08 16:06:43 marcel-endeavour plasmashell[5830]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:14:28 marcel-endeavour plasmashell[7867]: Qt: Session management error: Could not open network socket
Okt 08 16:15:41 marcel-endeavour google-chrome.desktop[8049]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:22:21 marcel-endeavour plasmashell[8921]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:26:04 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 3 (BadWindow), sequence: 14805, resource id: 102760497, major code: 129 (SHAPE), minor code: 6 (Input)
Okt 08 16:35:53 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 152 (BadDamage), sequence: 14092, resource id: 6309960, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Okt 08 16:36:01 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 3 (BadWindow), sequence: 17041, resource id: 102760514, major code: 129 (SHAPE), minor code: 6 (Input)
Okt 08 16:36:17 marcel-endeavour plasmashell[10963]: Qt: Session management error: Could not open network socket
Okt 08 16:38:30 marcel-endeavour kwin_x11[1286]: kwin_core: XCB error: 3 (BadWindow), sequence: 52345, resource id: 102760546, major code: 129 (SHAPE), minor code: 6 (Input)
Okt 08 16:38:37 marcel-endeavour plasmashell[11307]: libva error: vaGetDriverNames() failed with unknown libva error
[marcel@marcel-endeavour ~]$ journalctl -b -0 | grep failed
Okt 08 15:55:09 marcel-endeavour kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Okt 08 15:55:19 marcel-endeavour kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Okt 08 15:55:24 marcel-endeavour (udev-worker)[553]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Okt 08 15:55:24 marcel-endeavour (udev-worker)[553]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \  -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.
Okt 08 15:55:25 marcel-endeavour kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Okt 08 15:55:25 marcel-endeavour kernel: cfg80211: failed to load regulatory.db
Okt 08 15:55:26 marcel-endeavour kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
Okt 08 15:55:42 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Okt 08 15:55:48 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Okt 08 15:56:13 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Okt 08 15:56:13 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Okt 08 15:56:25 marcel-endeavour org_kde_powerdevil[1325]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 08 15:56:27 marcel-endeavour org_kde_powerdevil[1325]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 08 15:56:31 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Okt 08 15:56:31 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Okt 08 15:56:32 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 15:56:33 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Okt 08 15:56:33 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Okt 08 15:56:47 marcel-endeavour wireplumber[1389]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
Okt 08 15:56:47 marcel-endeavour wireplumber[1389]: <WpSiAudioAdapter:0x5573e9bcc620> failed to activate item: Object activation aborted: proxy destroyed
Okt 08 15:57:31 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 15:57:34 marcel-endeavour plasmashell[1967]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 15:57:56 marcel-endeavour dbus-daemon[1209]: [session uid=1000 pid=1209] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
Okt 08 15:59:24 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 15:59:24 marcel-endeavour plasmashell[2539]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:01:03 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Okt 08 16:02:19 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:02:20 marcel-endeavour fwupd[3555]: 14:02:20.024 FuPluginIntelMe      failed to get public key using /fpf/OemCred: generic failure [0xb]
Okt 08 16:02:20 marcel-endeavour fwupd[3555]: 14:02:20.073 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:1f.0: failed to mmap SPIBAR: Die Operation ist nicht erlaubt
Okt 08 16:03:20 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:03:20 marcel-endeavour plasmashell[3874]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:03:48 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Okt 08 16:06:42 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:06:43 marcel-endeavour plasmashell[5830]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:08:42 marcel-endeavour plasmashell[5830]: Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
Okt 08 16:15:40 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:15:41 marcel-endeavour google-chrome.desktop[8049]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:22:19 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:22:21 marcel-endeavour plasmashell[8921]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:24:20 marcel-endeavour plasmashell[8921]: Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
Okt 08 16:38:34 marcel-endeavour dbus-daemon[872]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Okt 08 16:38:37 marcel-endeavour plasmashell[11307]: libva error: vaGetDriverNames() failed with unknown libva error
Okt 08 16:40:34 marcel-endeavour plasmashell[11307]: Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER

ist das längste +16.831s
sollte nicht länger als 1-2 Sekunden sein dort…

kernel: pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+

wird vermutlich nur mit LTS angezeigt…

ist das ein hybrid intel/nvidia gpu notebook und gpu switcher ist eingerichtet? oder nur der Nvidia installiert und sonst nichts geändert?

(udev-worker)[553]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \  -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.

ist ein hybrid intel/nvidia gpu notebook, habe mit envycontrol nvidia aktiviert

zeige mal:

inxi -Gaz

Ich kann zwar nichts Hilfreiches zur Diskussion beitragen, aber dennoch ein herzliches Wilkommen im Forum auch von mir @Schenkelhals0815 :enos_flag:

Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: DP-2,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
    vendor: Hewlett-Packard driver: nvidia v: 535.113.01
    alternate: nouveau,nvidia_drm non-free: 535.xx+
    status: current (as of 2023-09) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 ports: active: none empty: DP-1,HDMI-A-1
    bus-ID: 01:00.0 chip-ID: 10de:1c8c class-ID: 0300
  Device-3: Realtek HP Wide Vision HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3 chip-ID: 0bda:58eb
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 75 s-size: 652x366mm (25.67x14.41")
    s-diag: 748mm (29.44")
  Monitor-1: eDP-1 mapped: eDP-1-1 model: ChiMei InnoLux 0x175a built: 2016
    res: 1920x1080 hz: 60 dpi: 128 gamma: 1.2 size: 381x214mm (15x8.43")
    diag: 437mm (17.2") ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 3 drv: swrast surfaceless:
    drv: nvidia x11: drv: nvidia inactive: gbm,wayland,device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 535.113.01
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    memory: 3.91 GiB
  API: Vulkan v: 1.3.264 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1050 Ti driver: nvidia v: 535.113.01 device-ID: 10de:1c8c
    surfaces: xcb,xlib

Vielen Dank und Hallo :slight_smile:

1 Like

sieht gut aus rendert auf der Nvidia GPU…

Scheint also nicht daran zu liegen… das der switcher nicht funktioniert…

Ich glaub wirklich, dass es an der HDD liegt auf der das System installiert ist. Windows ist auf einer SSD installiert und das bootet richtig schnell

Ja HDD ist ein Flaschenhals ist ja auch nicht das es 3 Minuten dauert zum booten…