Seit der Installation, März 2024, erscheint die login-Zeile vor den letzten boot-log-Zeilen.
Kein login-Manager installiert.
login eingeben, PW, fertig.
Das irritiert aber etwas. Wo muss ich da suchen ?
Mein System:

Architektur:                       x86_64
  CPU Operationsmodus:             32-bit, 64-bit
  Adressgrößen:                    39 bits physical, 48 bits virtual
  Byte-Reihenfolge:                Little Endian
CPU(s):                            16
  Liste der Online-CPU(s):         0-15
Anbieterkennung:                   GenuineIntel
Modellname:                      12th Gen Intel(R) Core(TM) i7-12650H

lspci:

0000:00:00.0 Host bridge: Intel Corporation Device 4649 (rev 02)
0000:00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02)
0000:00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics] (rev 0c)
0000:00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02)
0000:00:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
0000:00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02)
0000:00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02)
0000:00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02)
0000:00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
0000:00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
0000:00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
0000:00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
0000:00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
0000:00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
0000:00:15.3 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #3 (rev 01)
0000:00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
0000:00:17.0 System peripheral: Intel Corporation RST VMD Managed Controller
0000:00:1d.0 PCI bridge: Intel Corporation Device 51b3 (rev 01)
0000:00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01)
0000:00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
0000:00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] (rev a1)
0000:01:00.1 Audio device: NVIDIA Corporation Device 22be (rev a1)
0000:2b:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer E2600 GbE Controller (rev 21)
10000:e0:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02)
10000:e0:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02)
10000:e0:17.0 SATA controller: Intel Corporation Alder Lake-P SATA AHCI Controller (rev 01)
10000:e1:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
10000:e2:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. NV2 NVMe SSD SM2267XT (DRAM-less) (rev 03)

journalctl -b (Auszug):

Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: base HW address: e4:60:17:39:ee:7d
Jun 17 17:40:28 an5175571s6 boltd[640]: [30c68780-90c5-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x463e'
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Jun 17 17:40:28 an5175571s6 kernel: iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0
Jun 17 17:40:28 an5175571s6 iwd[641]: event: connect-failed, status: 1
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Firmware loaded in 1427860 usecs
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Waiting for device to boot
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Device booted in 15868 usecs
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Firmware timestamp 2024.14 buildtype 1 build 81454
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Firmware SHA1: 0xdfd62093
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Fseq status: Success (0x00)
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Fseq executed: 00.00.02.41
Jun 17 17:40:29 an5175571s6 kernel: Bluetooth: hci0: Fseq BT Top: 00.00.02.41

Die Meldung , daß agetty im credential-Verzeichnis nichts findet, konnte ich lt. WIKI beseitigen.
Dadurch wurden die boot-logs nach dem login weniger.
Aber ganz weg ist es nicht.

Danke schonmal
Andreas

  • brikler hat auf diesen Beitrag geantwortet.

    firmahager Das irritiert aber etwas. Wo muss ich da suchen ?

    ich würde zum probleme suchen journalctl -p err benutzen, alles andere im log ist zwar nicht schön, kannst du aber ignorieren (wenn dus kannst

      brikler

      Danke für's lesen und antworten !!

      [root@an5175571s6 ~]# journalctl -p err

      -- Boot e9662bf44e2e42f4812cec38c0067455 --
      Jun 18 16:57:02 an5175571s6 kernel: integrity: Problem loading X.509 certificate -65
      Jun 18 16:57:02 an5175571s6 kernel: integrity: Problem loading X.509 certificate -65
      Jun 18 16:57:03 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
      Jun 18 16:57:03 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
      Jun 18 16:57:03 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
      Jun 18 16:57:04 an5175571s6 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
      Jun 18 16:59:12 an5175571s6 systemd[1]: Failed to start Time & Date Service.
      Jun 18 16:59:27 an5175571s6 systemd-networkd-wait-online[1244]: Timeout occurred while waiting for network connectivity.
      Jun 18 16:59:27 an5175571s6 systemd[1]: Failed to start Wait for Network to be Configured.
      Jun 18 16:59:28 an5175571s6 systemd[1]: Failed to mount /home/andreas/sshfspingu02.
      
      ``` 
      Andreas

      Habe eben nochmal neu gebootet. Weil vorhin war der DNS noch nicht ganz hochgefahren.

      -- Boot 68db0c2140e34cdf9230a9e8d2a3b52e --
      Jun 18 18:22:01 an5175571s6 kernel: integrity: Problem loading X.509 certificate -65
      Jun 18 18:22:01 an5175571s6 kernel: integrity: Problem loading X.509 certificate -65
      Jun 18 18:22:02 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
      Jun 18 18:22:02 an5175571s6 kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
      Jun 18 18:22:03 an5175571s6 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:0 type:45 scope:1 part:233
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: fifo:c00000:0000:0000:[(udev-worker)[243]] errored - disabling channel
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:8 type:45 scope:1 part:233
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: fifo:c00400:0001:0008:[(udev-worker)[243]] errored - disabling channel
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: systemd-logind[642]: VMM allocation failed: -22
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:0 type:45 scope:1 part:233
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:8 type:45 scope:1 part:233
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: systemd-logind[642]: VMM allocation failed: -22
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:0 type:45 scope:1 part:233
      Jun 18 18:22:26 an5175571s6 kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:8 type:45 scope:1 part:233
      Jun 18 18:22:45 an5175571s6 kernel: nouveau 0000:01:00.0: imem: suspend failed, -22
      Jun 18 18:22:45 an5175571s6 kernel: nouveau 0000:01:00.0: disp: init failed, -22
      Jun 18 18:22:45 an5175571s6 kernel: nouveau 0000:01:00.0: disp: failed restart, -22
      Jun 18 18:22:45 an5175571s6 kernel: nouveau: DRM-master:00000000:00000080: suspend failed with -22
      Jun 18 18:22:45 an5175571s6 kernel: nouveau 0000:01:00.0: can't suspend (nouveau_pmops_runtime_suspend [nouveau] returned -22)
      Jun 18 18:24:02 an5175571s6 systemd[1]: Failed to start Time & Date Service.

      Warum ntp nicht klappt, weiß ich nicht.

      [root@an5175571s6 ~]# systemctl status systemd-timesyncd
      ● systemd-timesyncd.service - Network Time Synchronization
           Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
           Active: active (running) since Tue 2024-06-18 18:22:02 CEST; 8min ago
             Docs: man:systemd-timesyncd.service(8)
         Main PID: 616 (systemd-timesyn)
           Status: "Contacted time server 192.168.3.101:123 (pingu03.famhager)."
            Tasks: 2 (limit: 18740)
           Memory: 2.0M (peak: 3.1M)
              CPU: 35ms
           CGroup: /system.slice/systemd-timesyncd.service
                   └─616 /usr/lib/systemd/systemd-timesyncd
      
      Jun 18 18:22:02 an5175571s6 systemd[1]: Starting Network Time Synchronization...
      Jun 18 18:22:02 an5175571s6 systemd[1]: Started Network Time Synchronization.
      Jun 18 18:22:03 an5175571s6 systemd-timesyncd[616]: Network configuration changed, trying to establish connection.
      Jun 18 18:22:03 an5175571s6 systemd-timesyncd[616]: Contacted time server 192.168.3.101:123 (pingu03.famhager).
      Jun 18 18:22:03 an5175571s6 systemd-timesyncd[616]: Initial clock synchronization to Tue 2024-06-18 18:22:04.227486 CEST.

      iwlwifi und Bluetooth, fehlt mir die Ahnung. Konnte bisher keinen Ansatz im Netz finden.
      Zertifikats- und GraKa-Problem kann ich ebenfalls nicht einordnen, wie schwer das wiegt.

      Was ich auf dem NB machen will, läuft.

      Gruß
      Andreas

      • brikler hat auf diesen Beitrag geantwortet.

        firmahager iwlwifi und Bluetooth, fehlt mir die Ahnung. Konnte bisher keinen Ansatz im Netz finden.

        da ist wahrscheinlich der kernel schuld => ignoriere es

          brikler
          Okay,
          bleibt noch die Frage:
          Wie und wo wird die Reihenfolge des Bootvorgangs festgelegt ?
          Das managed bestimmt systemd mit seinen Abhängigkeiten in den conf-Files ?
          Warum kommt der login und danach noch paar logs ?

          Man kann wahrscheinlich mit quiet alle logs unterbinden. Ich hätte aber gerne an der Ursache geschraubt.
          Weniger an den Auswirkungen.

          Andreas

            firmahager Wie und wo wird die Reihenfolge des Bootvorgangs festgelegt ?

            gar nicht, systemd startet alles parallel

              firmahager Wie und wo wird die Reihenfolge des Bootvorgangs festgelegt ?
              Das managed bestimmt systemd mit seinen Abhängigkeiten in den conf-Files ?

              Genau, diese ergibt sich aus den in den Units konfigurierten Abhängigkeiten.
              Zur Analyse des Bootvorgangs ist systemd-analyze dein Freund:

              • systemd-analyze blame
              • systemd-analyze critical-chain
              • systemd-analyze plot > boot.svg

                brikler

                schard

                Danke Euch Beiden.
                Der Bootprozess läuft rd. 5 sec.
                Die längsten Initialisierungen:

                      266ms dev-nvme0n1p3.device
                       207ms boot.mount
                       196ms bolt.service
                       181ms user@1000.service
                       179ms polkit.service
                       155ms systemd-resolved.service
                        94ms iwd.service
                        89ms systemd-networkd.service
                        72ms udisks2.service
                        61ms systemd-udev-trigger.service
                        59ms plymouth-start.service
                        57ms upower.service
                        55ms systemd-tmpfiles-setup-dev-early.service
                        52ms systemd-tmpfiles-clean.service
                        51ms systemd-journal-flush.service
                        50ms systemd-fsck@dev-disk-by\x2duuid-0dde60a8\x2d353f\x2d4f9b\x2d8df8\x2d0f55addbf37e.service
                        46ms systemd-fsck@dev-disk-by\x2duuid-4083\x2dD431.service
                        45ms home.mount
                   ............

                Die Warteliste der services sieht so aus:

                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 @1.736s
                └─multi-user.target @1.736s
                  └─getty.target @1.736s
                    └─getty@tty1.service @1.736s
                      └─plymouth-quit-wait.service @1.705s +28ms
                        └─systemd-user-sessions.service @1.697s +7ms
                          └─network.target @1.664s
                            └─iwd.service @1.569s +94ms
                              └─basic.target @1.567s
                                └─dbus-broker.service @1.547s +18ms
                                  └─dbus.socket @1.517s
                                    └─sysinit.target @1.511s
                                      └─systemd-resolved.service @1.355s +155ms
                                        └─systemd-tmpfiles-setup.service @1.320s +33ms
                                          └─local-fs.target @1.318s
                                            └─boot.mount @1.062s +207ms
                                              └─systemd-fsck@dev-disk-by\x2duuid-4083\x2dD431.service @1.014s +46ms
                                                └─dev-disk-by\x2duuid-4083\x2dD431.device @1.008s

                Das svg-File:
                Hätte ich gerne wohin geladen. Finde aber nichts im Forum. Bzw. sprunge.us klappt nicht

                systemd-analyze plot | curl -F 'sprunge=<-' http://sprunge.us
                
                <html><head>
                <meta http-equiv="content-type" content="text/html;charset=utf-8">
                <title>404 Page not found</title>
                </head>
                <body text=#000000 bgcolor=#ffffff>
                <h1>Error: Page not found</h1>
                <h2>The requested URL was not found on this server.</h2>
                <h2></h2>
                </body></html>

                Wenn ich da reinschaue, sehe ich die Zeit für firmware, loader und kernel.
                Den Start von systemd bei rd. 4 sec. Die Initialisierung aller Units/Services ist bei 5,5 sec. durch.
                Also nichts zum Haare raufen.

                Kann ich noch was machen ?
                Vorab schon mal vielen Dank.
                Andreas

                3 Monate später

                Problem hat sich seit 3 Tagen aufgelöst.
                Die letzten Zeilen vom Boot-Log:

                Okt 02 18:16:56 an5175571s6 systemd[827]: Listening on p11-kit server.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Listening on PipeWire PulseAudio.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Listening on PipeWire Multimedia System Sockets.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Listening on D-Bus User Message Bus Socket.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Reached target Sockets.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Reached target Basic System.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/andreas/.cache/kcrash-metadata/*.ini).
                Okt 02 18:16:56 an5175571s6 systemd[1]: Started User Manager for UID 1000.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Starting Update XDG user dir configuration...
                Okt 02 18:16:56 an5175571s6 systemd[1]: Started Session 1 of User andreas.
                Okt 02 18:16:56 an5175571s6 login[812]: LOGIN ON tty1 BY andreas
                Okt 02 18:16:56 an5175571s6 systemd[827]: Finished Update XDG user dir configuration.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Reached target Main User Target.
                Okt 02 18:16:56 an5175571s6 systemd[827]: Startup finished in 195ms.

                cat /var/log/pacman.log:

                [2024-09-27T17:35:52+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:35:52+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:35:58+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:35:58+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:05+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:05+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:14+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:14+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:24+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:24+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:33+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:33+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:44+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:44+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:36:52+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:36:52+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:37:00+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:37:00+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:37:10+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:37:10+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:37:17+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:37:17+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:37:25+0200] [PACMAN] Running 'pacman -Syu'
                [2024-09-27T17:37:25+0200] [PACMAN] synchronizing package lists
                [2024-09-27T17:37:28+0200] [PACMAN] starting full system upgrade
                [2024-09-27T17:39:01+0200] [ALPM] transaction started
                [2024-09-27T17:39:01+0200] [ALPM] upgraded boost-libs (1.86.0-2 -> 1.86.0-3)
                [2024-09-27T17:39:01+0200] [ALPM] upgraded cairo (1.18.2-1 -> 1.18.2-2)
                [2024-09-27T17:39:01+0200] [ALPM] upgraded fribidi (1.0.15-1 -> 1.0.16-1)
                [2024-09-27T17:39:01+0200] [ALPM] upgraded libopenmpt (0.7.9-1 -> 0.7.10-1)
                [2024-09-27T17:39:01+0200] [ALPM] upgraded gtk-update-icon-cache (1:4.16.1-1 -> 1:4.16.2-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded firefox (130.0.1-1 -> 130.0.1-2)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded hdf5-openmpi (1.14.4.3-1 -> 1.14.4.3-2)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded git (2.46.1-1 -> 2.46.2-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded python-fonttools (4.53.1-1 -> 4.54.1-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded libraqm (0.10.1-2 -> 0.10.2-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded freecad (1.0rc1-3 -> 1.0rc2-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded gssdp (1.6.3-1 -> 1.6.3-2)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded gupnp (1:1.6.6-1 -> 1:1.6.7-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded libarchive (3.7.5-1 -> 3.7.6-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded libuv (1.48.0-2 -> 1.49.0-1)
                [2024-09-27T17:39:02+0200] [ALPM] upgraded protobuf (28.1-1 -> 28.2-1)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded marble-common (24.08.1-3 -> 24.08.1-4)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded mesa-utils (9.0.0-4 -> 9.0.0-5)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded ostree (2024.7-4 -> 2024.8-1)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded python-platformdirs (4.2.2-1 -> 4.3.6-1)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded thunderbird (128.2.2-1 -> 128.2.3-1)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded thunderbird-i18n-de (128.2.2-1 -> 128.2.3-1)
                [2024-09-27T17:39:03+0200] [ALPM] installed libvlc (3.0.21-6)
                [2024-09-27T17:39:03+0200] [ALPM] upgraded vlc (3.0.21-4 -> 3.0.21-6)
                [2024-09-27T17:39:03+0200] [ALPM] transaction completed
                [2024-09-27T17:39:03+0200] [ALPM] running '20-systemd-sysusers.hook'...
                [2024-09-27T17:39:03+0200] [ALPM] running '30-systemd-daemon-reload-system.hook'...
                [2024-09-27T17:39:03+0200] [ALPM] running '30-systemd-tmpfiles.hook'...
                [2024-09-27T17:39:04+0200] [ALPM] running '30-systemd-update.hook'...
                [2024-09-27T17:39:04+0200] [ALPM] running '30-update-mime-database.hook'...
                [2024-09-27T17:39:04+0200] [ALPM] running '90-mkinitcpio-install.hook'...
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.10.10-arch1-1'
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
                [2024-09-27T17:39:04+0200] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
                [2024-09-27T17:39:07+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
                [2024-09-27T17:39:07+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
                [2024-09-27T17:39:07+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
                [2024-09-27T17:39:07+0200] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
                [2024-09-27T17:39:07+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.10.10-arch1-1'
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
                [2024-09-27T17:39:08+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
                [2024-09-27T17:39:09+0200] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
                [2024-09-27T17:39:09+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
                [2024-09-27T17:39:09+0200] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
                [2024-09-27T17:39:10+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
                [2024-09-27T17:39:15+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
                [2024-09-27T17:39:15+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
                [2024-09-27T17:39:16+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
                [2024-09-27T17:39:16+0200] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
                [2024-09-27T17:39:16+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
                [2024-09-27T17:39:16+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
                [2024-09-27T17:39:16+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
                [2024-09-27T17:39:17+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
                [2024-09-27T17:39:17+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
                [2024-09-27T17:39:17+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
                [2024-09-27T17:39:17+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
                [2024-09-27T17:39:19+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
                [2024-09-27T17:39:19+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
                [2024-09-27T17:39:20+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
                [2024-09-27T17:39:21+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
                [2024-09-27T17:39:21+0200] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
                [2024-09-27T17:39:21+0200] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
                [2024-09-27T17:39:21+0200] [ALPM] running 'gtk-update-icon-cache.hook'...
                [2024-09-27T17:39:22+0200] [ALPM] running 'update-desktop-database.hook'...
                [2024-09-27T17:39:22+0200] [ALPM] running 'update-vlc-plugin-cache.hook'...
                
                ``` 
                Da fehlt mir die Ahnung. 
                
                Grüße
                Andreas