Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1

#1 Le 07/01/2025, à 15:41

jimbou

[RESOLU] Démarrage très lent après installation toute fraiche

Bonjour,

Après avoir installé Windows, j'ai installé Ubuntu 24 en dual boot.

Tout se passe normalement sous Windows. Mais sous Ubuntu, le démarrage est très lent.

Quand j'essaie de faire Esc pendant le démarrage, il ne se passe rien, je reste en mode page de démarrage (=je ne passe pas en mode console avec affichage des étapes).

Quelques infos:

fal33-14@fal33-14-Ordi:~$ systemd-analyze time
Startup finished in 10.675s (firmware) + 10.069s (loader) + 2.821s (kernel) + 1min 36.945s (userspace) = 2min 512ms 
graphical.target reached after 1min 36.918s in userspace.
fal33-14@fal33-14-Ordi:~$
fal33-14@fal33-14-Ordi:~$ 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 @1min 36.918s
└─power-profiles-daemon.service @1min 36.834s +83ms
  └─multi-user.target @1min 36.827s
    └─plymouth-quit-wait.service @1min 32.391s +4.435s
      └─systemd-user-sessions.service @1min 32.336s +48ms
        └─network.target @1min 32.317s
          └─NetworkManager.service @1min 30.966s +1.349s
            └─dbus.service @1min 30.444s +248ms
              └─basic.target @1min 30.430s
                └─sockets.target @1min 30.430s
                  └─snapd.socket @1min 30.425s +5ms
                    └─sysinit.target @1min 30.413s
                      └─tpm2.target @1min 30.413s
fal33-14@fal33-14-Ordi:~$

Comme j'ai vu sur un post que ça pouvait venir du SSD :

fal33-14@fal33-14-Ordi:~$ sudo smartctl -s on -a  /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.0-13-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       256GB SSD
Serial Number:                      CP48BAJ0500431
Firmware Version:                   SN10726
PCI Vendor/Subsystem ID:            0x1e4b
IEEE OUI Identifier:                0x3a5a27
Total NVM Capacity:                 256060514304 [256 GB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          256060514304 [256 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            3a5a27 0230000fa1
Local Time is:                      Tue Jan  7 15:28:28 2025 CET
Firmware Updates (0x1a):            5 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     90 Celsius
Critical Comp. Temp. Threshold:     95 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.50W       -        -    0  0  0  0        0       0
 1 +     5.80W       -        -    1  1  1  1        0       0
 2 +     3.60W       -        -    2  2  2  2        0       0
 3 -   0.7460W       -        -    3  3  3  3     5000   10000
 4 -   0.7260W       -        -    4  4  4  4     8000   49000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        33 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    96429 [49,3 GB]
Data Units Written:                 133911 [68,5 GB]
Host Read Commands:                 840469
Host Write Commands:                893118
Controller Busy Time:               1
Power Cycles:                       12
Power On Hours:                     1
Unsafe Shutdowns:                   7
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               33 Celsius
Temperature Sensor 2:               36 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

fal33-14@fal33-14-Ordi:~$

Je vous aurais bien mis la section de syslog relative au dernier démarrage, mais ça fait trop long pour le post. Personnellement, je n'y ai rien vu d'anormal, et elle me donne l'impression que l'attente se produit avant que l'enregistrement dans syslog commence.

D'avance merci.

Dernière modification par jimbou (Le 07/01/2025, à 16:33)

Ubuntu 24.04 avec Gnome

Hors ligne

#2 Le 07/01/2025, à 15:45

geole

Re : [RESOLU] Démarrage très lent après installation toute fraiche

Bonjour
J'ai vu que tu as un NVME
Donne aussi les erreurs 

journalctl --no-pager -b -p err

Dernière modification par geole (Le 07/01/2025, à 15:51)

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#3 Le 07/01/2025, à 15:49

iznobe

Re : [RESOLU] Démarrage très lent après installation toute fraiche

Bonjour , montre :

lsblk -fe7 | cat
grep -v ^# /etc/fstab

bizzare le retour de la derniere commande .
rien avant TPM2 ?
serait ce la puce TPM qui pose soucis ?

retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .

Hors ligne

#4 Le 07/01/2025, à 15:53

jimbou

Re : [RESOLU] Démarrage très lent après installation toute fraiche

fal33-14@fal33-14-Ordi:~$ journalctl --no-pager -b -p err
janv. 07 15:47:47 fal33-14-Ordi kernel: x86/cpu: SGX disabled by BIOS.
janv. 07 15:47:47 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
janv. 07 15:50:38 fal33-14-Ordi gdm-password][2111]: gkr-pam: unable to locate daemon control file
janv. 07 15:50:41 fal33-14-Ordi systemd[2123]: Failed to start app-gnome-im\x2dlaunch-2616.scope - Application launched by gnome-session-binary.
janv. 07 15:50:41 fal33-14-Ordi systemd[2123]: Failed to start app-gnome-snap\x2duserd\x2dautostart-2585.scope - Application launched by gnome-session-binary.
janv. 07 15:50:41 fal33-14-Ordi systemd[2123]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2623.scope - Application launched by gnome-session-binary.
fal33-14@fal33-14-Ordi:~$ 
fal33-14@fal33-14-Ordi:~$ grep -v ^# /etc/fstab
/dev/disk/by-uuid/0fdd9790-3216-44f2-ab4a-670b934ef6df / ext4 defaults 0 1
/dev/disk/by-uuid/F0C7-17B2 /boot/efi vfat defaults 0 1
/swap.img	none	swap	sw	0	0
fal33-14@fal33-14-Ordi:~$ 
fal33-14@fal33-14-Ordi:~$ lsblk -fe7 | cat
NAME        FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                            
├─nvme0n1p1 vfat   FAT32       F0C7-17B2                              64,9M    32% /boot/efi
├─nvme0n1p2                                                                        
├─nvme0n1p3 ntfs               34E8C84CE8C80DD4                                    
├─nvme0n1p4 ntfs               D0BA7990BA797436                                    
└─nvme0n1p5 ext4   1.0         0fdd9790-3216-44f2-ab4a-670b934ef6df     96G    11% /
fal33-14@fal33-14-Ordi:~$

Ubuntu 24.04 avec Gnome

Hors ligne

#5 Le 07/01/2025, à 15:56

iznobe

Re : [RESOLU] Démarrage très lent après installation toute fraiche

hum , ca ressemble a un bug de puce TPM ca , non ?

janv. 07 15:47:47 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.

retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .

Hors ligne

#6 Le 07/01/2025, à 15:58

geole

Re : [RESOLU] Démarrage très lent après installation toute fraiche

 tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1

  ===> https://www.spinics.net/lists/linux-int … 03318.html
Donne aussi

mokutil --sb-state

Dernière modification par geole (Le 07/01/2025, à 15:59)

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#7 Le 07/01/2025, à 16:02

iznobe

Re : [RESOLU] Démarrage très lent après installation toute fraiche

montre :

systemctl status dev-tpmrm0.device
systemctl status tpm2.target

retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .

Hors ligne

#8 Le 07/01/2025, à 16:05

jimbou

Re : [RESOLU] Démarrage très lent après installation toute fraiche

fal33-14@fal33-14-Ordi:~$ mokutil --sb-state
SecureBoot disabled
fal33-14@fal33-14-Ordi:~$

Mais le timeout sur TPM m'a donné une idée : j'ai entré systemctl mask dev-tpmrm0.device, et maintenant ça démarre à fond la caisse !

J'ai 5 PC identiques (même marque, même modèle, même année), mais mon fol espoir d'en configurer 1 pour ensuite copier l'image disque sur les 4 autres s'est heurté à la dure réalité. J'en suis à mon 4eme, et je découvre encore des différences de comportement.

Ubuntu 24.04 avec Gnome

Hors ligne

#9 Le 07/01/2025, à 16:06

geole

Re : [RESOLU] Démarrage très lent après installation toute fraiche

Tu as donc masqué le problème. Pour tenter de le connaître mieux

journalctl --no-pager  -g tpm -n 100

An Ubuntu forum suggests adding tpm_tis.interrupts=0 to the kernel command line will avoid the timeout on systems that don’t have TPM2

Dernière modification par geole (Le 07/01/2025, à 16:19)

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#10 Le 07/01/2025, à 16:13

jimbou

Re : [RESOLU] Démarrage très lent après installation toute fraiche

Voilà le résultat de la dernière demande, un peu remis d'aplomb car sur la console ça n'était pas clair.

fal33-14@fal33-14-Ordi:~$ journalctl -g tpm -n 100
janv. 07 15:55:52 fal33-14-Ordi gnome-remote-de[751]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:55:52 fal33-14-Ordi gnome-remote-de[752]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:55:52 fal33-14-Ordi systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:52 fal33-14-Ordi systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:52 fal33-14-Ordi systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: Reached target tpm2.target - Trusted Platform Module.
janv. 07 15:55:49 fal33-14-Ordi systemd[1]: systemd 256.5-2ubuntu3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
janv. 07 15:55:49 fal33-14-Ordi kernel: ima: No TPM chip found, activating TPM-bypass!
janv. 07 15:55:49 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:55:49 fal33-14-Ordi kernel: ACPI: Reserving TPM2 table memory at [mem 0xdae516b0-0xdae516e3]
janv. 07 15:55:49 fal33-14-Ordi kernel: ACPI: TPM2 0x00000000DAE516B0 000034 (v03 DELL   CBX3     00000001 AMI  00000000)
janv. 07 15:55:49 fal33-14-Ordi kernel: efi: ACPI=0xdae1e000 ACPI 2.0=0xdae1e000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 TPMFinalLog=0xdb719000 ESRT=0xdbb5f118 MEMATTR=0xd8781118 MOKvar=0xdbbdc000 INITRD=0xd3982518 TPMEventLog=0xcb938018 
-- Boot 7ecde50d717f4c01b46531febb56213a --
janv. 07 15:55:27 fal33-14-Ordi systemd[1]: Stopped target tpm2.target - Trusted Platform Module.
janv. 07 15:54:59 fal33-14-Ordi polkitd[1131]: Operator of unix-session:2 successfully authenticated as unix-user:fal33-14 to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-unit-files for system-bus-name::1.135 [systemctl mask dev-tpmrm0.device] (owned by unix-user:fal33-14)
janv. 07 15:49:17 fal33-14-Ordi gnome-remote-de[1128]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:49:17 fal33-14-Ordi gnome-remote-de[1127]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: Reached target tpm2.target - Trusted Platform Module.
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
janv. 07 15:49:17 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
janv. 07 15:47:47 fal33-14-Ordi systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
janv. 07 15:47:47 fal33-14-Ordi systemd[1]: systemd 256.5-2ubuntu3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
janv. 07 15:47:47 fal33-14-Ordi kernel: ima: No TPM chip found, activating TPM-bypass!
janv. 07 15:47:47 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:47:47 fal33-14-Ordi kernel: ACPI: Reserving TPM2 table memory at [mem 0xdae516b0-0xdae516e3]
janv. 07 15:47:47 fal33-14-Ordi kernel: ACPI: TPM2 0x00000000DAE516B0 000034 (v03 DELL   CBX3     00000001 AMI  00000000)
janv. 07 15:47:47 fal33-14-Ordi kernel: efi: ACPI=0xdae1e000 ACPI 2.0=0xdae1e000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 TPMFinalLog=0xdb719000 ESRT=0xdbb5f118 MEMATTR=0xd8780118 MOKvar=0xdbbdc000 INITRD=0xd3982518 TPMEventLog=0xcb938018 
-- Boot 0bac6893921e4b07835c789d8526cc2c --
janv. 07 15:47:20 fal33-14-Ordi systemd[1]: Stopped target tpm2.target - Trusted Platform Module.
janv. 07 15:16:09 fal33-14-Ordi gnome-remote-de[1111]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:16:09 fal33-14-Ordi gnome-remote-de[1110]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: Reached target tpm2.target - Trusted Platform Module.
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
janv. 07 15:16:08 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
janv. 07 15:14:38 fal33-14-Ordi systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
janv. 07 15:14:38 fal33-14-Ordi systemd[1]: systemd 256.5-2ubuntu3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
janv. 07 15:14:38 fal33-14-Ordi kernel: ima: No TPM chip found, activating TPM-bypass!
janv. 07 15:14:38 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:14:38 fal33-14-Ordi kernel: ACPI: Reserving TPM2 table memory at [mem 0xdae516b0-0xdae516e3]
janv. 07 15:14:38 fal33-14-Ordi kernel: ACPI: TPM2 0x00000000DAE516B0 000034 (v03 DELL   CBX3     00000001 AMI  00000000)
janv. 07 15:14:38 fal33-14-Ordi kernel: efi: ACPI=0xdae1e000 ACPI 2.0=0xdae1e000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 TPMFinalLog=0xdb719000 ESRT=0xdbb5f118 MEMATTR=0xd877d018 MOKvar=0xdbbdc000 INITRD=0xd3982518 TPMEventLog=0xcb938018 
-- Boot 235d0a8b338b497b93a89a1e8995378a --
janv. 07 15:12:20 fal33-14-Ordi systemd[1]: Stopped target tpm2.target - Trusted Platform Module.
janv. 07 15:03:08 fal33-14-Ordi gnome-remote-de[1056]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:03:08 fal33-14-Ordi gnome-remote-de[1055]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: Reached target tpm2.target - Trusted Platform Module.
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
janv. 07 15:03:07 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
janv. 07 15:01:37 fal33-14-Ordi systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
janv. 07 15:01:37 fal33-14-Ordi systemd[1]: systemd 256.5-2ubuntu3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
janv. 07 15:01:37 fal33-14-Ordi kernel: ima: No TPM chip found, activating TPM-bypass!
janv. 07 15:01:37 fal33-14-Ordi kernel: tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1
janv. 07 15:01:37 fal33-14-Ordi kernel: ACPI: Reserving TPM2 table memory at [mem 0xdae516b0-0xdae516e3]
janv. 07 15:01:37 fal33-14-Ordi kernel: ACPI: TPM2 0x00000000DAE516B0 000034 (v03 DELL   CBX3     00000001 AMI  00000000)
janv. 07 15:01:37 fal33-14-Ordi kernel: efi: ACPI=0xdae1e000 ACPI 2.0=0xdae1e000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 TPMFinalLog=0xdb719000 ESRT=0xdbb5f118 MEMATTR=0xd8780118 MOKvar=0xdbbdc000 INITRD=0xd3982518 TPMEventLog=0xcb938018 
-- Boot 9a7bd9c22f0141a9b7e2e6ae833c5517 --
janv. 07 15:01:18 fal33-14-Ordi systemd[1]: Stopped target tpm2.target - Trusted Platform Module.
janv. 07 14:52:38 fal33-14-Ordi gnome-remote-de[1053]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 14:52:38 fal33-14-Ordi gnome-remote-de[1054]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: Reached target tpm2.target - Trusted Platform Module.
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
janv. 07 14:52:37 fal33-14-Ordi systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
janv. 07 14:51:07 fal33-14-Ordi systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...

Ubuntu 24.04 avec Gnome

Hors ligne

#11 Le 07/01/2025, à 16:25

iznobe

Re : [RESOLU] Démarrage très lent après installation toute fraiche

@geole , pour info : https://bbs.archlinux.org/viewtopic.php?id=296699

retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .

Hors ligne

Pages : 1