# Sortie de mise en veille impossible - ASUS - Debian 12

**URL:** <https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392>\
**Category:** Support Debian\
**Created:** [Juin 21, 2023, 5:48 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392 "2023-06-21T17:48:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 21, 2023, 5:48 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/1 "2023-06-21T17:48:05Z")

</div>

Bonjour,  
j’ai un problème de sortie de veille, le PC ne se rallume pas, je dois faire un arrêt forcé avec la touche d’alimentation.  
J’ai installé Debian 12 avec Gnome, KDE et Xfce, aucune différence le problème est le même.  
D’après mes recherches il me semble que le défaut vient de la gestion ACPI mais je ne trouve pas de solution.  
Avez vous des pistes ?  
Merci

la commande journalctl -r -p err donne :

```auto
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20220331/psargs-330)
juin 21 19:26:03 pcleane kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 21 19:26:03 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20220331/psargs-330)

```

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 21, 2023, 9:30 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/2 "2023-06-21T21:30:55Z")

</div>

Le paquet **intel-microcode** est-il installé ? [dépôt non-free-firmware]

`$ uname -rv`

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 8:22 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/3 "2023-06-22T08:22:55Z")

</div>

oui intel-microcode version la plus récente installée

uname -rv :  
`6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) `

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 10:01 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/4 "2023-06-22T10:01:18Z")

</div>

Pas sûr de la corrélation veille / messages acpi.

Retour de :  
`grep 6.1.0-9 /boot/grub/grub.cfg`  
`grep -r enable /sys/firmware/acpi/interrupts`

Pour investigations::

**veille** : s’assurer que le réveil ne soit pas une déshibernation  
ajouter `noresume` en option de noyau (configuration grub / peut être ajouté à la volée au boot en arrêtant grub, en éditant le ligne linux du noyau 6.1.0-9)

**acpi** :  
Ces messages ne sont peut-être pas importants (BIOS qui ne comprend pas toutes les requêtes)  
» voir dans le BIOS la configuration SATA: si RAID, changer en AHCI

Si pas concluant, ajouter `acpi=off` en option de noyau (configuration grub / pour essai temporaire seulement).

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 12:36 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/5 "2023-06-22T12:36:22Z")

</div>

> [@Verner](#):
>
> `grep 6.1.0-9 /boot/grub/grub.cfg`

```
echo	'Loading Linux 6.1.0-9-amd64 ...'
linux	/boot/vmlinuz-6.1.0-9-amd64 root=UUID=d45a0bf9-4570-44cf-9901-77de19a93357 ro quiet
initrd	/boot/initrd.img-6.1.0-9-amd64
menuentry 'Debian GNU/Linux, with Linux 6.1.0-9-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-9-amd64-advanced-d45a0bf9-4570-44cf-9901-77de19a93357' {
	echo	'Loading Linux 6.1.0-9-amd64 ...'
	linux	/boot/vmlinuz-6.1.0-9-amd64 root=UUID=d45a0bf9-4570-44cf-9901-77de19a93357 ro quiet
	initrd	/boot/initrd.img-6.1.0-9-amd64
menuentry 'Debian GNU/Linux, with Linux 6.1.0-9-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-9-amd64-recovery-d45a0bf9-4570-44cf-9901-77de19a93357' {
	echo	'Loading Linux 6.1.0-9-amd64 ...'
	linux	/boot/vmlinuz-6.1.0-9-amd64 root=UUID=d45a0bf9-4570-44cf-9901-77de19a93357 ro single 
	initrd	/boot/initrd.img-6.1.0-9-amd64

```

> [@Verner](#):
>
> `grep -r enable /sys/firmware/acpi/interrupts`

```plaintext
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe66: 12 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe72: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe6E: 6 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe62: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe73: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe6F: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe6D: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe61: 0 EN enabled unmasked

```

> [@Verner](#):
>
> ajouter `noresume` en option de noyau (

ne résout pas le problème

> [@Verner](#):
>
> voir dans le BIOS la configuration SATA: si RAID, changer en AHCI

je ne trouve pas cette configuration !

> [@Verner](#):
>
> ajouter `acpi=off` en option de noyau

debian ne démarre plus

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 12:41 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/6 "2023-06-22T12:41:36Z")

</div>

il arrive peu souvent (de manière aléatoire) qu’à la sortie de veille ce ne soit pas un écran noir (non allumé) mais des messages d’erreur en boucle qui s’affiche  
voici une photo des messages (pas réussi avec journalctl à les afficher)

 ![signal-2023-06-22-143141_002](https://www.debian-fr.org/uploads/default/original/2X/2/220b2eb9750b2cff88d5cc67bb73cbb0ec6c221e.jpeg)

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 12:53 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/7 "2023-06-22T12:53:55Z")

</div>

Ha oui quand-même… un train peut en cacher un autre.  
Il faut commencer par résoudre les erreurs du device **nvme0n1p2**.

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 1:15 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/8 "2023-06-22T13:15:13Z")

</div>

> [@Verner](#):
>
> Il faut commencer par résoudre les erreurs du device **nvme0n1p2**.

là je sèche, comment fait-on ?

la sortie de df -H :

```plaintext
root@pcleane:~# df -H
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 4,0G 0 4,0G 0% /dev
tmpfs 801M 1,9M 799M 1% /run
/dev/nvme0n1p2 20G 6,0G 13G 33% /
tmpfs 4,1G 0 4,1G 0% /dev/shm
tmpfs 5,3M 8,2k 5,3M 1% /run/lock
/dev/nvme0n1p4 229G 13G 205G 6% /home
/dev/nvme0n1p1 66M 6,1M 59M 10% /boot/efi
tmpfs 801M 107k 801M 1% /run/user/1000
root@pcleane:~# 

```

```plaintext
root@pcleane:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 238,5G 0 disk 
├─nvme0n1p1 259:1 0 63M 0 part /boot/efi
├─nvme0n1p2 259:2 0 18,6G 0 part /
├─nvme0n1p3 259:3 0 2,8G 0 part [SWAP]
└─nvme0n1p4 259:4 0 217G 0 part /home
root@pcleane:~# 

```

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 1:19 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/9 "2023-06-22T13:19:08Z")

</div>

Il faut booter sur du liveCD, ou autre installation qui ne monte pas nvme0n1p2.  
Et checker nvme0n1p2 (non montée)  
`fsck.ext4 /dev/nvme0n1p2`

Et  
`$ sudo dmidecode -t0`

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 1:48 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/10 "2023-06-22T13:48:02Z")

</div>

en live cd debian :

> [@Verner](#):
>
> `fsck.ext4 /dev/nvme0n1p2`
> 
> Et  
> `$ sudo dmidecode -t0`

```plaintext
root@debian:~# fsck.ext4 /dev/nvme0n1p2
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p2: clean, 175087/1222992 files, 1575406/4882432 blocks
root@debian:~# 

```

```plaintext
root@debian:~# dmidecode -t0
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: American Megatrends International, LLC.
	Version: X415EA.306
	Release Date: 11/04/2021
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 16 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		ACPI is supported
		Smart battery is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.19
root@debian:~# 

```

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 2:03 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/11 "2023-06-22T14:03:13Z")

</div>

Il faudrait essayer ça, avant de tenter une mise en veille:

`# echo "disable" > /sys/firmware/acpi/interrupts/gpe6F`

Sinon, pour info il y a du BIOS 2023 → [X415EA - Assistance](https://www.asus.com/fr/supportonly/x415ea/helpdesk_bios/)

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 6:30 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/12 "2023-06-22T18:30:10Z")

</div>

> [@Verner](#):
>
> `# echo "disable" > /sys/firmware/acpi/interrupts/gpe6F`

ne fonctionne pas

> [@Verner](#):
>
> Sinon, pour info il y a du BIOS 2023 → [X415EA - Assistance](https://www.asus.com/fr/supportonly/x415ea/helpdesk_bios/)

en effet mais il faut windows pour mettre à jour d’après ce que lit ; je cherche à faire un livecd avec malekal

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 6:58 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/13 "2023-06-22T18:58:42Z")

</div>

> [@davidx](#):
>
> il faut windows

Ce n’est pas ce que je comprends avec [Comment mettre à jour le BIOS avec **EZ Flash**](https://www.asus.com/fr/support/FAQ/1008859)

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 7:46 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/14 "2023-06-22T19:46:38Z")

</div>

> [@Verner](#):
>
> Ce n’est pas ce que je comprends avec [Comment mettre à jour le BIOS avec **EZ Flash**](https://www.asus.com/fr/support/FAQ/1008859)

en effet, merci de la remarque

=\> bios mis à jour, pas de résolution du problème

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 7:57 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/15 "2023-06-22T19:57:31Z")

</div>

> [@davidx](#):
>
> résolution **du** problème

J’en vois 2, pas nécessairement corrélés / pas prouvé:  
» messages acpi peut-être sans conséquences et qui peuvent être masqués (non prioritaire pour le moment)  
 → après mise à jour du BIOS, ça devient plus compliqué si problème central

» problème de réveil

Pour changer un peu:  
`$ lspci -v | awk '/VGA/,/^$/'`

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 8:14 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/16 "2023-06-22T20:14:31Z")

</div>

> [@Verner](#):
>
> après mise à jour du BIOS

pas de changement mais peut être des messages en plus ?  
`journalctl -r -p err`

```plaintext
juin 22 22:06:10 pcleane gdm-launch-environment][787]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
juin 22 22:06:09 pcleane systemd[1411]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1906.scope - Application launched by gnome-session-binary.
juin 22 22:06:09 pcleane systemd[1411]: Failed to start app-gnome-im\x2dlaunch-1870.scope - Application launched by gnome-session-binary.
juin 22 22:06:08 pcleane systemd[1411]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1585.scope - Application launched by gnome-session-binary.
juin 22 22:06:08 pcleane systemd[1411]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1574.scope - Application launched by gnome-session-binary.
juin 22 22:06:08 pcleane systemd[1411]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1572.scope - Application launched by gnome-session-binary.
juin 22 22:06:07 pcleane gdm-password][1384]: gkr-pam: unable to locate daemon control file
juin 22 22:05:59 pcleane bluetoothd[646]: Failed to set mode: Failed (0x03)
juin 22 22:05:59 pcleane bluetoothd[646]: sap-server: Operation not permitted (1)
juin 22 22:05:59 pcleane bluetoothd[646]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
juin 22 22:05:59 pcleane bluetoothd[646]: src/plugin.c:plugin_init() Failed to init bap plugin
juin 22 22:05:59 pcleane bluetoothd[646]: src/plugin.c:plugin_init() Failed to init mcp plugin
juin 22 22:05:59 pcleane bluetoothd[646]: src/plugin.c:plugin_init() Failed to init vcp plugin
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20220331/psargs-330)
juin 22 22:05:58 pcleane kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
juin 22 22:05:58 pcleane kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20220331/psargs-330)

```

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 8:15 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/17 "2023-06-22T20:15:27Z")

</div>

> [@Verner](#):
>
> Pour changer un peu:  
> `$ lspci -v | awk '/VGA/,/^$/'`

```plaintext
root@pcleane:~# lspci -v | awk '/VGA/,/^$/'
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller])
	DeviceName: VGA
	Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics]
	Flags: bus master, fast devsel, latency 0, IRQ 155, IOMMU group 0
	Memory at 6002000000 (64-bit, non-prefetchable) [size=16M]
	Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [100] Process Address Space ID (PASID)
	Capabilities: [200] Address Translation Service (ATS)
	Capabilities: [300] Page Request Interface (PRI)
	Capabilities: [320] Single Root I/O Virtualization (SR-IOV)
	Kernel driver in use: i915
	Kernel modules: i915

```

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 8:47 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/18 "2023-06-22T20:47:38Z")

</div>

Avec un peu de ménage et de tri, tes erreurs se résument à ça, sans savoir si elles sont majeures ou pas.

```nohighlight
kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND
kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20220331/psargs-330)
kernel: ACPI Error: Aborting method _SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
kernel: ACPI Error: Aborting method _SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

bluetoothd[646]: Failed to set mode: Failed (0x03)
bluetoothd[646]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd[646]: sap-server: Operation not permitted (1)
bluetoothd[646]: src/plugin.c:plugin_init() Failed to init bap plugin
bluetoothd[646]: src/plugin.c:plugin_init() Failed to init mcp plugin
bluetoothd[646]: src/plugin.c:plugin_init() Failed to init vcp plugin

gdm-password][1384]: gkr-pam: unable to locate daemon control file
gdm-launch-environment][787]: GLib-GObject: g_object_unref: assertion ‹ G_IS_OBJECT (object) › failed

systemd[1411]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1572.scope - Application launched by gnome-session-binary.
systemd[1411]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1574.scope - Application launched by gnome-session-binary.
systemd[1411]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1585.scope - Application launched by gnome-session-binary.
systemd[1411]: Failed to start app-gnome-im\x2dlaunch-1870.scope - Application launched by gnome-session-binary.
systemd[1411]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1906.scope - Application launched by gnome-session-binary.

```

---

<div class="post-metadata">

**Author:** ![davidx](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/ecae2f/32.png) [@davidx](https://www.debian-fr.org/u/davidx)\
**Post date:** [Juin 22, 2023, 9:02 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/19 "2023-06-22T21:02:12Z")

</div>

> [@Verner](#):
>
> Avec un peu de ménage et de tri, tes erreurs se résument à ça, sans savoir si elles sont majeures ou pas.

merci pour le ménage ; vois tu une erreur qui pourrait causer le problème en sortie de veille ?  
sachant que le problème était le même avec kde ou xcfe, donc je ne pencherais pas pour les app-gnome, ni le bluetooth (mais mes connaissances en erreurs sont très limitées !)

---

<div class="post-metadata">

**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\
**Post date:** [Juin 22, 2023, 9:17 UTC](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392/20 "2023-06-22T21:17:46Z")

</div>

Je ne vois rien qui me semble majeur, et je n’y connais rien à gnome

`$ systemctl status gnome-session-manager`

[Page suivante](https://www.debian-fr.org/t/sortie-de-mise-en-veille-impossible-asus-debian-12/88392.md?page=2)