Sur laptop Toshiba satellite A200-2C4 avec Manjaro 16.10 XFCE, depuis quelques temps problème de retour de veille (testé sous 3 noyau différents). Le champ de login délire et de mot de passe, clignote aléatoirement, réagit bizarrement. Impossible de se reconnecter : extinction par commutateur obligatoire pour redémarrer.... Ce matin écran noir (noyau 4.9), redémarrage nécessaire. A noter que cela ne se produit que si la veille dépasse une certaine durée...
Bonjour. Je suppose que ça peut venir de ta mémoire vive. Comment obtiens tu 3012 de Ram ? Deux barrettes je suppose , mais de combien? Normalement, celle qui a la plus grande capacité doit être sur le premier slot, mais la fréquence doit être identique. Si tu as dmidecode d'installé, donne le retour de :
sudi inxi -m
Ça ne solutionnera en rien ton problème, mais nous éclairera un peu plus sur la capacité de ta mémoire vive a recevoir la mise en veille.
Noyau récent MANJARO x86_64 bits: 64 Xfce 4.16
ASUSTeK model: PRIME B350M-A v: Rev X.0x
6-Core: AMD Ryzen 5 2600X
AMD Baffin [Radeon RX 460/560D / Pro
driver: amdgpu v: kernel
Display: x11 server: X.Org driver: amdgpu,ati unloaded: modesetting
OpenGL: renderer: Radeon RX 560 Series
Arch en Dual. Aucun lien publicitaire ne saurait être toléré dans la signature!
Là on serait bon. Comment passe tu en veille ? Par la fonction proposée par Xfce? (xfce-session-logout) Essayes de passer par systemctl suspend que tu peux taper en terminal .
Noyau récent MANJARO x86_64 bits: 64 Xfce 4.16
ASUSTeK model: PRIME B350M-A v: Rev X.0x
6-Core: AMD Ryzen 5 2600X
AMD Baffin [Radeon RX 460/560D / Pro
driver: amdgpu v: kernel
Display: x11 server: X.Org driver: amdgpu,ati unloaded: modesetting
OpenGL: renderer: Radeon RX 560 Series
Arch en Dual. Aucun lien publicitaire ne saurait être toléré dans la signature!
Le problème ne vient donc pas de LightDM comme j'ai pu penser. Driver CG ?
Autre chose, j'avais compiz installé (je l'ai supprimé) mais impossible de me souvenir si le problème est apparu avant ou après cette désinstall (pi ça à peut être ou sûrement même rien à voir)...
Je pense que c'est Lightdm qui qui nous emm de. J'ai viré tout gestionnaire de connexion sur la tour étant le seul utilisateur avec un seul DM (Xfce). Je n'ai aucun problème de réveil. Je teste sur le portable....
Edit: bon, ça se réveille normalement. Donne le retour de dmesg | grep sleep et de dmesg | grep wakeup
Voici le mien:
[steph@Dell ~]$ dmesg |grep slleep [steph@Dell ~]$ dmesg |grep sleep [ 461.131895] PM: Preparing system for sleep (mem) [ 461.973843] ACPI: Preparing to enter system sleep state S3 [ 462.006901] cache: parent cpu1 should not be sleeping [ 462.009280] ACPI: Waking up from system sleep state S3 [ 477.672969] PM: Preparing system for sleep (mem) [ 478.337399] ACPI: Preparing to enter system sleep state S3 [ 478.366549] cache: parent cpu1 should not be sleeping [ 478.368985] ACPI: Waking up from system sleep state S3 [steph@Dell ~]$ dmesg |grep wake-up [steph@Dell ~]$ dmesg |grep wakeup [ 0.405096] pci 0000:00:1a.0: System wakeup disabled by ACPI [ 0.405389] pci 0000:00:1a.1: System wakeup disabled by ACPI [ 0.405717] pci 0000:00:1a.7: System wakeup disabled by ACPI [ 0.406061] pci 0000:00:1b.0: System wakeup disabled by ACPI [ 0.407002] pci 0000:00:1c.2: System wakeup disabled by ACPI [ 0.407607] pci 0000:00:1d.0: System wakeup disabled by ACPI [ 0.407901] pci 0000:00:1d.1: System wakeup disabled by ACPI [ 0.408190] pci 0000:00:1d.2: System wakeup disabled by ACPI [ 0.408515] pci 0000:00:1d.7: System wakeup disabled by ACPI [ 461.955992] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI [ 461.956095] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI [ 461.956164] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI [ 461.956244] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI [ 461.956703] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI [ 461.956887] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI [ 461.956934] uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI [ 462.014865] uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI [ 462.014982] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI [ 462.015967] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI [ 462.016001] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI [ 462.016130] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI [ 462.030479] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI [ 462.031002] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI [ 462.059391] rtc_cmos 00:01: System wakeup disabled by ACPI [ 462.059446] ene_ir 00:04: System wakeup disabled by ACPI [ 463.303938] PM: Finishing wakeup. [ 478.322314] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI [ 478.322321] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI [ 478.322435] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI [ 478.322532] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI [ 478.322946] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI [ 478.323130] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI [ 478.323162] uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI [ 478.380365] uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI [ 478.380526] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI [ 478.381317] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI [ 478.381482] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI [ 478.381512] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI [ 478.396893] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI [ 478.396915] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI [ 478.428119] rtc_cmos 00:01: System wakeup disabled by ACPI [ 478.428174] ene_ir 00:04: System wakeup disabled by ACPI [ 479.672582] PM: Finishing wakeup. [steph@Dell ~]$
Noyau récent MANJARO x86_64 bits: 64 Xfce 4.16
ASUSTeK model: PRIME B350M-A v: Rev X.0x
6-Core: AMD Ryzen 5 2600X
AMD Baffin [Radeon RX 460/560D / Pro
driver: amdgpu v: kernel
Display: x11 server: X.Org driver: amdgpu,ati unloaded: modesetting
OpenGL: renderer: Radeon RX 560 Series
Arch en Dual. Aucun lien publicitaire ne saurait être toléré dans la signature!
Pas vu de différence notable... C'est quoi déjà le logiciel pour comparer des fichiers textes ? (j'avais vu passé ça pour la gestion des pacnew)
dmesg | grep sleep [ 534.158624] PM: Preparing system for sleep (mem) [ 534.880149] ACPI: Preparing to enter system sleep state S3 [ 534.909326] cache: parent cpu1 should not be sleeping [ 534.910750] ACPI: Waking up from system sleep state S3 [13376.450994] PM: Preparing system for sleep (mem) [13377.248854] ACPI: Preparing to enter system sleep state S3 [13377.268096] cache: parent cpu1 should not be sleeping [13377.269511] ACPI: Waking up from system sleep state S3
dmesg | grep wakeup [ 0.386084] pci 0000:00:1a.1: System wakeup disabled by ACPI [ 0.386368] pci 0000:00:1a.7: System wakeup disabled by ACPI [ 0.386657] pci 0000:00:1b.0: System wakeup disabled by ACPI [ 0.388197] pci 0000:00:1d.0: System wakeup disabled by ACPI [ 0.388429] pci 0000:00:1d.1: System wakeup disabled by ACPI [ 0.388662] pci 0000:00:1d.2: System wakeup disabled by ACPI [ 0.388946] pci 0000:00:1d.7: System wakeup disabled by ACPI [ 0.400600] pci 0000:04:00.0: System wakeup disabled by ACPI [ 0.433353] pci 0000:05:00.0: System wakeup disabled by ACPI [ 534.806329] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI [ 534.818501] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI [ 534.830083] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI [ 534.841586] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI [ 534.853774] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI [ 534.864225] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI [ 534.917749] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI [ 534.918163] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI [ 534.918250] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI [ 534.918278] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI [ 534.933943] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI [ 534.933992] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI [ 534.990074] rtc_cmos 00:03: System wakeup disabled by ACPI [ 537.363725] PM: Finishing wakeup. [13377.175520] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI [13377.195355] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI [13377.205354] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI [13377.215350] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI [13377.225381] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI [13377.234307] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI [13377.274956] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI [13377.275450] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI [13377.275529] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI [13377.275547] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI [13377.288799] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI [13377.292340] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI [13377.335065] rtc_cmos 00:03: System wakeup disabled by ACPI [13379.735792] PM: Finishing wakeup.
Manjaro gnome 0.8.13
Dernière modification par GimenezAntoineil y a 7 ans, modifié au total 2 fois.
lemust83 a écrit :Je pense que c'est Lightdm qui qui nous emm de. J'ai viré tout gestionnaire de connexion sur la tour étant le seul utilisateur avec un seul DM (Xfce). Je n'ai aucun problème de réveil.
Ouais, en fouillant sur le forum j'avais vu ton post sur la suppression du gestionnaire de connexion. Malgré systemctl suspend qui foire aussi, tu penses quand même que ça vient de lightDM ?
Non, je pense maintenant que c'est un bug Intel/Acpi mais je ne sais comment résoudre ce problème. J'ai lu quelques part que la rupture de la connexion filaire pouvait sur certaines machine provoquer ce comportement. As tu le moyen de modifier des paramètres dans le Bios genre ACPI S1 vers S3 ?
Noyau récent MANJARO x86_64 bits: 64 Xfce 4.16
ASUSTeK model: PRIME B350M-A v: Rev X.0x
6-Core: AMD Ryzen 5 2600X
AMD Baffin [Radeon RX 460/560D / Pro
driver: amdgpu v: kernel
Display: x11 server: X.Org driver: amdgpu,ati unloaded: modesetting
OpenGL: renderer: Radeon RX 560 Series
Arch en Dual. Aucun lien publicitaire ne saurait être toléré dans la signature!
Bon ben ça marche pas mieux ! Je vais essayer de creuser autour de cette piste ça me semble cohérent... Mais je suis preneur de toute idée parce que c'est super pénible !