Vous n'êtes pas identifié(e).
Pages : 1
Pour Xorg.0.log en revanche, je ne sais pas trop comment lire les marqueurs de temps sur le côté : où commencer, où m'arrêter.
Merci pour tant de dévouement
re,
je cherche (suis pas un utilisateur de la veille prolongée) , il doit avoir un sujet sur le forum assez ancien
donc moi il semble que sur plusieurs machines je suis en "s3" => suspend to ram
il serait bon de vérifier comment tu est configurer ( dans ton bios EFI)
la nuance c'est que la machine reste alimenté (cpu0 et ram) en s3
sinon c'est le mode "to disk" ou la machine n'est plus alimenté (juste pour le réveil )
deux liens
=> https://wiki-ubuntu-com.translate.goog/ … pto=nui,sc
=> https://doc.ubuntu-fr.org/veille_et_hibernation
ps: désactiver l'erp dans le bios (mode économie d'énergie ) , l'option porte peut être un autre nom
et regarder les modes disponibles "s1 a s5) de mémoire
Merci pour tes recherches.
Je n'utilise pas non plus la veille prolongée, il s'agit de veille "normale".
Cela dit, quand j'étais sous Ubuntu 20.04, je n'avais pas ce problème. Entre-temps rien n'a changé dans le bios EFI...
J'éplucherai les logs tout à l'heure.
re, voila la partie debian bullseye gpu nvidia sur amd r7 1700 , beaucoup moins propre mais bon ça fonctionne
Oct 10 20:38:19 debian30 systemd[1]: Starting Suspend...
Oct 10 20:38:19 debian30 systemd-sleep[1958]: Suspending system...
Oct 10 20:38:19 debian30 kernel: [ 1227.716172] PM: suspend entry (deep)
Oct 10 20:38:19 debian30 kernel: [ 1227.718695] Filesystems sync: 0.002 seconds
Oct 10 20:42:47 debian30 kernel: [ 1228.024601] Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.026775] OOM killer disabled.
Oct 10 20:42:47 debian30 kernel: [ 1228.026777] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.028035] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 20:42:47 debian30 kernel: [ 1228.029309] serial 00:03: disabled
Oct 10 20:42:47 debian30 kernel: [ 1228.058680] sd 11:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 20:42:47 debian30 kernel: [ 1228.058737] sd 11:0:0:0: [sda] Stopping disk
Oct 10 20:42:47 debian30 kernel: [ 1228.195083] ACPI: Preparing to enter system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.503500] PM: Saving platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.503551] Disabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.505333] smpboot: CPU 1 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.508116] smpboot: CPU 2 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.510639] smpboot: CPU 3 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.513197] smpboot: CPU 4 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.515772] smpboot: CPU 5 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.518466] smpboot: CPU 6 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.520999] smpboot: CPU 7 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.523566] smpboot: CPU 8 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.525532] smpboot: CPU 9 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.528007] smpboot: CPU 10 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.530375] smpboot: CPU 11 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.532749] smpboot: CPU 12 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.535148] smpboot: CPU 13 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.537330] smpboot: CPU 14 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.539463] smpboot: CPU 15 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.540430] ACPI: Low-level resume complete
Oct 10 20:42:47 debian30 kernel: [ 1228.540473] PM: Restoring platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.541024] Enabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.541062] x86: Booting SMP configuration:
Oct 10 20:42:47 debian30 kernel: [ 1228.541063] smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 10 20:42:47 debian30 kernel: [ 1228.541176] microcode: CPU1: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.543347] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.543350] ACPI: \_PR_.C002: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.543628] CPU1 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.543693] smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 10 20:42:47 debian30 kernel: [ 1228.543886] microcode: CPU2: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.546053] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.546055] ACPI: \_PR_.C004: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.546258] CPU2 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.546272] smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 10 20:42:47 debian30 kernel: [ 1228.546391] microcode: CPU3: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.548560] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.548562] ACPI: \_PR_.C006: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.548754] CPU3 is up
Oct 10 20:42:47 debian30 kernel:[ 1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[ 1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 1229.394] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 1229.394] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 1229.394] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 1229.394] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 1229.394] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 1229.394] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 1229.394] (II) NVIDIA(0): Config Options in the README.
[ 1229.422] (II) event5 - Power Button: is tagged by udev as: Keyboard
[ 1229.422] (II) event5 - Power Button: device is a keyboard
[ 1229.424] (II) event4 - Power Button: is tagged by udev as: Keyboard
[ 1229.424] (II) event4 - Power Button: device is a keyboard
[ 1229.425] (II) event0 - Microsoft Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[ 1229.425] (II) event0 - Microsoft Microsoft Basic Optical Mouse v2.0 : device is a pointer
[ 1229.427] (II) event1 - SEM USB Keyboard: is tagged by udev as: Keyboard
[ 1229.427] (II) event1 - SEM USB Keyboard: device is a keyboard
[ 1229.428] (II) event2 - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[ 1229.428] (II) event2 - SEM USB Keyboard Consumer Control: device is a keyboard
[ 1229.430] (II) event3 - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[ 1229.430] (II) event3 - SEM USB Keyboard System Control: device is a keyboard
[ 1229.431] (II) event7 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[ 1229.431] (II) event7 - Eee PC WMI hotkeys: device is a keyboard
[ 1275.469] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[ 1430.932] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[ 1478.867] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[ 1484.348] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow [ 1228.548768] smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 10 20:42:47 debian30 kernel: [ 1228.548928] microcode: CPU4: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.551118] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.551120] ACPI: \_PR_.C008: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.551359] CPU4 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.551381] smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 10 20:42:47 debian30 kernel: [ 1228.551545] microcode: CPU5: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.553716] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.553719] ACPI: \_PR_.C00A: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.553952] CPU5 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.553971] smpboot: Booting Node 0 Processor 6 APIC 0xc
Oct 10 20:42:47 debian30 kernel: [ 1228.554135] microcode: CPU6: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.556345] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.556347] ACPI: \_PR_.C00C: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.556589] CPU6 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.556609] smpboot: Booting Node 0 Processor 7 APIC 0xe
Oct 10 20:42:47 debian30 kernel: [ 1228.556774] microcode: CPU7: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.558953] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.558955] ACPI: \_PR_.C00E: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.559210] CPU7 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.559231] smpboot: Booting Node 0 Processor 8 APIC 0x1
Oct 10 20:42:47 debian30 kernel: [ 1228.559378] microcode: CPU8: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.561575] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.561577] ACPI: \_PR_.C001: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.561937] CPU8 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.561968] smpboot: Booting Node 0 Processor 9 APIC 0x3
Oct 10 20:42:47 debian30 kernel: [ 1228.562085] microcode: CPU9: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.564269] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.564271] ACPI: \_PR_.C003: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.564568] CPU9 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.564586] smpboot: Booting Node 0 Processor 10 APIC 0x5
Oct 10 20:42:47 debian30 kernel: [ 1228.564704] microcode: CPU10: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.566882] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.566884] ACPI: \_PR_.C005: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.567187] CPU10 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.567204] smpboot: Booting Node 0 Processor 11 APIC 0x7
Oct 10 20:42:47 debian30 kernel: [ 1228.567320] microcode: CPU11: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.569503] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.569505] ACPI: \_PR_.C007: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.569836] CPU11 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.569851] smpboot: Booting Node 0 Processor 12 APIC 0x9
Oct 10 20:42:47 debian30 kernel: [ 1228.570010] microcode: CPU12: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.572220] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.572223] ACPI: \_PR_.C009: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.572583] CPU12 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.572603] smpboot: Booting Node 0 Processor 13 APIC 0xb
Oct 10 20:42:47 debian30 kernel: [ 1228.572747] microcode: CPU13: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.574936] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.574938] ACPI: \_PR_.C00B: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.575289] CPU13 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.575309] smpboot: Booting Node 0 Processor 14 APIC 0xd
Oct 10 20:42:47 debian30 kernel: [ 1228.575468] microcode: CPU14: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.577658] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.577661] ACPI: \_PR_.C00D: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.578029] CPU14 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.578049] smpboot: Booting Node 0 Processor 15 APIC 0xf
Oct 10 20:42:47 debian30 kernel: [ 1228.578212] microcode: CPU15: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.580433] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.580435] ACPI: \_PR_.C00F: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.580821] CPU15 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.582418] ACPI: Waking up from system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.664512] usb usb1: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664515] usb usb2: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664796] sd 11:0:0:0: [sda] Starting disk
Oct 10 20:42:47 debian30 kernel: [ 1228.665298] serial 00:03: activated
Oct 10 20:42:47 debian30 kernel: [ 1228.978609] ata2: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979322] ata5: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979341] ata6: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.053715] OOM killer enabled.
Oct 10 20:42:47 debian30 kernel: [ 1229.053716] Restarting tasks ... done.
Oct 10 20:42:47 debian30 kernel: [ 1229.054796] PM: suspend exit
Oct 10 20:42:47 debian30 systemd-sleep[1958]: System resumed.
Oct 10 20:42:47 debian30 kernel: [ 1229.139438] ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139797] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.144314] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.145689] ata1.00: configured for UDMA/100
Oct 10 20:42:47 debian30 systemd-sleep[2101]: /dev/sda:
Oct 10 20:42:47 debian30 systemd-sleep[2101]: setting Advanced Power Management level to 0xfe (254)
Oct 10 20:42:47 debian30 systemd-sleep[2101]: APM_level#011= 254
Oct 10 20:42:47 debian30 kernel: [ 1229.149174] ata12.00: configured for UDMA/133
Oct 10 20:42:47 debian30 kernel: [ 1229.149465] ata12.00: Enabling discard_zeroes_data
Oct 10 20:42:47 debian30 systemd[1]: systemd-suspend.service: Succeeded.
Oct 10 20:42:47 debian30 systemd[1]: Finished Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Sleep.
Oct 10 20:42:47 debian30 systemd[1]: Reached target Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Suspend.
Oct 10 20:42:50 debian30 kernel: [ 1231.804443] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
et voila le log de X (la fin au redemarrage) des bug aussi mais ça fonctionne
[ 1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[ 1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 1229.394] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 1229.394] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 1229.394] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 1229.394] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 1229.394] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 1229.394] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 1229.394] (II) NVIDIA(0): Config Options in the README.
[ 1229.422] (II) event5 - Power Button: is tagged by udev as: Keyboard
[ 1229.422] (II) event5 - Power Button: device is a keyboard
[ 1229.424] (II) event4 - Power Button: is tagged by udev as: Keyboard
[ 1229.424] (II) event4 - Power Button: device is a keyboard
[ 1229.425] (II) event0 - Microsoft Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[ 1229.425] (II) event0 - Microsoft Microsoft Basic Optical Mouse v2.0 : device is a pointer
[ 1229.427] (II) event1 - SEM USB Keyboard: is tagged by udev as: Keyboard
[ 1229.427] (II) event1 - SEM USB Keyboard: device is a keyboard
[ 1229.428] (II) event2 - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[ 1229.428] (II) event2 - SEM USB Keyboard Consumer Control: device is a keyboard
[ 1229.430] (II) event3 - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[ 1229.430] (II) event3 - SEM USB Keyboard System Control: device is a keyboard
[ 1229.431] (II) event7 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[ 1229.431] (II) event7 - Eee PC WMI hotkeys: device is a keyboard
[ 1275.469] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[ 1430.932] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[ 1478.867] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[ 1484.348] (EE) event1 - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
donc la configuration de l' EFI (un bug acpi), le matériel , une application particulière qui est rester ouverte au passage en "veille profonde"
mais certainement pas le driver nvidia ou lightdm
avec un peu de chance tu peu trouver des traces dans le syslog et le log de X
ps: sur ceux je vais installer le daemon acpi
journalctl -r -p err
-- Journal begins at Sun 2021-10-10 20:17:54 CEST, ends at Sun 2021-10-10 20:43:18 CEST. --
oct. 10 20:18:11 debian30 pulseaudio[812]: Error opening PCM device iec958:1: Aucun fichier ou dossier de ce type
oct. 10 20:18:10 debian30 lightdm[873]: gkr-pam: unable to locate daemon control file
08:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
08:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
Grand merci pour ton aide, j'ai installé acpi, acpid et acpi-support-base.
Le démon est bien actif :
Mais le problème persiste.
Merci aussi pour les retours sur NVidia, ta 1060 est bien sous la version 460.xxx du pilote propriétaire ?
Plutôt qu'ajouter des paquets, j'en retirerais, ou plutôt je débrancherais progressivement ce qui gère la veille des écrans, à savoir :
- Le gestionnaire d'alimentation d'xfce (dans paramètres)
- L'écran de veille (dans paramètres aussi, s'il est installé, c'est xscreensaver)
- lightdm (je ne l'ai plus, du coup à part le désinstaller, installer xinit et faire un starx, je ne peux plus indiquer comment régler ses options...)
xfce4-power-manager n'est pas coupable car j'avais déjà mon problème avant de l'installer. En fait je l'ai installé au cas où il m'aiderait (ce qui n'a pas été le cas).
xscreensaver n'est pas installé.
J'essayerai ce soir sans lightdm, il me faut le temps de me replonger dans la docu des xinitrc...
Bonjour
le retour de lspci
lspci
de glxinfo -B (du paquet mesa-utils)
glxinfo -B
de la présence de acpid
apt policy acpid
des erreurs sur la machine
journalctl -b -r -p err
Alors, lspci :
glxinfo -B :
apt policy acpid :
journalctl -b -r -p err :
Soit j'installe Buster en tant que Stable (c'est-à-dire en spécifiant stable plutôt que buster dans mon /etc/apt/sources.list), afin de basculer automatiquement sur Bullseye quand Buster deviendra Oldstable. Je suppose que c'est la façon officiellement recommandée de procéder.
Soit j'installe Testing en spécifiant bullseye dans mon /etc/apt/sources.list, afin de rester sur Bullseye quand elle deviendra la nouvelle Stable. Éventuellement, je pourrais aussi installer Sid et basculer sur Bullseye le moment venu.
Le freeze est en effet si proche... je me dis que Bullseye devrait assez peu changer d'ici son passage en Stable. Donc, au total, en termes de quantité de trucs à régler manuellement, il se pourrait bien que commencer sur Testing / Sid maintenant puis passer sur Stable dans quelques mois me donne moins de boulot que de migrer de Buster à Bullseye. J'ai bon ?
Qui plus est, Buster commence à accuser un peu son âge, par exemple pour le bureau Xfce que je compte installer et qui a pas mal avancé depuis (ainsi, je crois que la migration sur GTK 3 est encore inachevée dans la version offerte par Buster)... sachant que je viens d'Ubuntu LTS qui est un peu plus récent. Autant les mises à jour intempestives m'horripilent (je ne m'intéresserais pas à Debian autrement), autant je préfère éviter une rétrogradation des paquets.
Donc voilà où j'en suis, pour l'instant j'ai l'intention de voir ce que ça donne avec Bullseye Testing. Dans le meilleur des cas, si tout marche, je ne touche à rien et j'évite les mises à jour (pour ne rien casser) jusqu'à la sortie de Bullseye Stable. Si ça coince, j'essaye Sid... Dans tous les cas, je préférerais éviter d'avoir à tout réinstaller à la sortie de la prochaine Stable.
Merci pour vos avis !
Pages : 1