Se connecter avec
S'enregistrer | Connectez-vous
Votre question
Résolu

[Linux général] Problème de mise en veille (suspend to ram) portable CG ATI

Dernière réponse : dans Autres OS
Partagez
10 Mars 2012 15:06:50

Bonjour,

Le portable de ma femme étant en train de rendre l'àme pour cause de virus méchant (win32-Karl, 24mois) :homer: 

J'ai donc récupéré un superbe portable centrino à 1,6Ghz de 2006 pour remplacer son asthmatique portable double core de 2008 sous Vista et y est installé opensuse.
Jusque là, tout vas bien dans le meilleur des monde possible, plus de ralentissements, vidéos HD fluides, tout marche bien "out of the box" comme on dit.

Le seul point noir - à l'origine de ce post - c'est cette carte graphique Ati (une x700). Pourtant, dit-on, ati, c'est bien, il ont libéré les spec, blah-blah, mais les pilote proprio ne s'installent pas, et les pilotes libres, bien que fonctionnels, se gaufrent joyeusement à la reprise de la mise en veille.
Pour arranger les chose, j'ai choisi d'installer gnome 3, qui niveau configurabilité est au sommet de son art, la seule action possible du bouton power est la mise en veille (elf-karl est attiré par les boutons qui brillent). :peur: 

Donc, je vois plusieurs solutions dans l'ordre de préférence :

1/ Faire fonctionner la mise en veille de façon non plantogène.

2/ Action > /dev/null du bouton power

3/ Désactiver la mise en veille du System

Pour le 3, j'ai essayé de désinstaller les outils liés à la mise en veille (pm-utils), le problème c'est que networkmanager refuse de fonctionner sans ça.

Il peut y avoir d'autres solutions, c'est pourquoi je fait appel à votre sagesse légendaires.:jap: 
10 Mars 2012 17:42:20

Les logs qui vont bien :
Spoiler

  1. [ 59.944023] radeon 0000:01:00.0: Refused to change power state, currently in D0
  2. [ 59.944079] radeon 0000:01:00.0: power state changed by ACPI to D3
  3. [ 59.944123] PM: suspend of devices complete after 547.769 msecs
  4. [ 59.960114] PM: late suspend of devices complete after 15.985 msecs
  5. [ 59.960261] ACPI: Preparing to enter system sleep state S3
  6. [ 59.996244] PM: Saving platform NVS memory
  7. [ 59.996911] Disabling non-boot CPUs ...
  8. [ 59.996911] ACPI: Low-level resume complete
  9. [ 59.996911] PM: Restoring platform NVS memory
  10. [ 59.996911] Force enabled HPET at resume
  11. [ 59.996911] ACPI: Waking up from system sleep state S3
  12. [ 60.104088] pcieport 0000:00:01.0: restoring config space at offset 0xf (was 0x100, writing 0xc010a)
  13. [ 60.104096] pcieport 0000:00:01.0: restoring config space at offset 0x9 (was 0xfff0, writing 0xcff0c000)
  14. [ 60.104101] pcieport 0000:00:01.0: restoring config space at offset 0x8 (was 0xfff0, writing 0xb010b010)
  15. [ 60.104105] pcieport 0000:00:01.0: restoring config space at offset 0x7 (was 0xf0, writing 0x3030)
  16. [ 60.104109] pcieport 0000:00:01.0: restoring config space at offset 0x6 (was 0x0, writing 0x10100)
  17. [ 60.104115] pcieport 0000:00:01.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10008)
  18. [ 60.104119] pcieport 0000:00:01.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
  19. [ 60.104145] pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x4010a)
  20. [ 60.104155] pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x44b144a1)
  21. [ 60.104160] pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0x44904480)
  22. [ 60.104165] pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0x7070)
  23. [ 60.104170] pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x90900)
  24. [ 60.104176] pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810008)
  25. [ 60.104182] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
  26. [ 60.104214] pcieport 0000:00:1c.1: restoring config space at offset 0xf (was 0x200, writing 0x4020a)
  27. [ 60.104223] pcieport 0000:00:1c.1: restoring config space at offset 0x9 (was 0x10001, writing 0x44714461)
  28. [ 60.104228] pcieport 0000:00:1c.1: restoring config space at offset 0x8 (was 0x0, writing 0x44504440)
  29. [ 60.104233] pcieport 0000:00:1c.1: restoring config space at offset 0x7 (was 0x0, writing 0x6060)
  30. [ 60.104238] pcieport 0000:00:1c.1: restoring config space at offset 0x6 (was 0x0, writing 0xa0a00)
  31. [ 60.104245] pcieport 0000:00:1c.1: restoring config space at offset 0x3 (was 0x810000, writing 0x810008)
  32. [ 60.104251] pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
  33. [ 60.104283] pcieport 0000:00:1c.2: restoring config space at offset 0xf (was 0x40300, writing 0x4030b)
  34. [ 60.104292] pcieport 0000:00:1c.2: restoring config space at offset 0x9 (was 0x1fff1, writing 0x44314421)
  35. [ 60.104297] pcieport 0000:00:1c.2: restoring config space at offset 0x8 (was 0xfff0, writing 0x44104400)
  36. [ 60.104302] pcieport 0000:00:1c.2: restoring config space at offset 0x7 (was 0x200000f0, writing 0x5050)
  37. [ 60.104307] pcieport 0000:00:1c.2: restoring config space at offset 0x6 (was 0x200, writing 0x40200)
  38. [ 60.104315] pcieport 0000:00:1c.2: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
  39. [ 60.104342] uhci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
  40. [ 60.104353] uhci_hcd 0000:00:1d.0: restoring config space at offset 0x8 (was 0x1, writing 0x1801)
  41. [ 60.104364] uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2800000, writing 0x2800001)
  42. [ 60.104374] uhci_hcd 0000:00:1d.1: restoring config space at offset 0xf (was 0x200, writing 0x20b)
  43. [ 60.104385] uhci_hcd 0000:00:1d.1: restoring config space at offset 0x8 (was 0x1, writing 0x1821)
  44. [ 60.104396] uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2800000, writing 0x2800001)
  45. [ 60.104406] uhci_hcd 0000:00:1d.2: restoring config space at offset 0xf (was 0x300, writing 0x30b)
  46. [ 60.104416] uhci_hcd 0000:00:1d.2: restoring config space at offset 0x8 (was 0x1, writing 0x1841)
  47. [ 60.104427] uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800000, writing 0x2800001)
  48. [ 60.104437] uhci_hcd 0000:00:1d.3: restoring config space at offset 0xf (was 0x400, writing 0x40a)
  49. [ 60.104447] uhci_hcd 0000:00:1d.3: restoring config space at offset 0x8 (was 0x1, writing 0x1861)
  50. [ 60.104458] uhci_hcd 0000:00:1d.3: restoring config space at offset 0x1 (was 0x2800000, writing 0x2800001)
  51. [ 60.104474] ehci_hcd 0000:00:1d.7: restoring config space at offset 0xf (was 0x100, writing 0x10b)
  52. [ 60.104490] ehci_hcd 0000:00:1d.7: restoring config space at offset 0x4 (was 0x0, writing 0xb0000000)
  53. [ 60.104497] ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
  54. [ 60.104515] pci 0000:00:1e.0: restoring config space at offset 0xf (was 0x40000, writing 0x400ff)
  55. [ 60.104525] pci 0000:00:1e.0: restoring config space at offset 0x9 (was 0x1fff1, writing 0x43f14001)
  56. [ 60.104530] pci 0000:00:1e.0: restoring config space at offset 0x8 (was 0xfff0, writing 0xb020b020)
  57. [ 60.104535] pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x228000f0, writing 0x22804040)
  58. [ 60.104540] pci 0000:00:1e.0: restoring config space at offset 0x6 (was 0xd8070600, writing 0xd8080600)
  59. [ 60.104558] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0xf (was 0x100, writing 0x10a)
  60. [ 60.104569] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0x7 (was 0x0, writing 0xb0000400)
  61. [ 60.104574] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0x6 (was 0x0, writing 0xb0000800)
  62. [ 60.104579] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0x5 (was 0x1301, writing 0x1881)
  63. [ 60.104584] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0x4 (was 0x1201, writing 0x1c01)
  64. [ 60.104591] snd_intel8x0 0000:00:1e.2: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900003)
  65. [ 60.104605] snd_intel8x0m 0000:00:1e.3: restoring config space at offset 0xf (was 0x200, writing 0x20b)
  66. [ 60.104617] snd_intel8x0m 0000:00:1e.3: restoring config space at offset 0x5 (was 0x1501, writing 0x2001)
  67. [ 60.104622] snd_intel8x0m 0000:00:1e.3: restoring config space at offset 0x4 (was 0x1401, writing 0x2401)
  68. [ 60.104629] snd_intel8x0m 0000:00:1e.3: restoring config space at offset 0x1 (was 0x2900005, writing 0x2900001)
  69. [ 60.104665] ata_piix 0000:00:1f.1: restoring config space at offset 0xf (was 0x100, writing 0x1ff)
  70. [ 60.104676] ata_piix 0000:00:1f.1: restoring config space at offset 0x8 (was 0x1, writing 0x18c1)
  71. [ 60.104687] ata_piix 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2800000, writing 0x2880005)
  72. [ 60.104698] i801_smbus 0000:00:1f.3: restoring config space at offset 0xf (was 0x200, writing 0x20b)
  73. [ 60.104711] i801_smbus 0000:00:1f.3: restoring config space at offset 0x8 (was 0x1101, writing 0x20a1)
  74. [ 60.104735] radeon 0000:01:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10a)
  75. [ 60.104745] radeon 0000:01:00.0: restoring config space at offset 0x6 (was 0x0, writing 0xb0100000)
  76. [ 60.104750] radeon 0000:01:00.0: restoring config space at offset 0x5 (was 0x1, writing 0x3001)
  77. [ 60.104755] radeon 0000:01:00.0: restoring config space at offset 0x4 (was 0x8, writing 0xc0000008)
  78. [ 60.104760] radeon 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8)
  79. [ 60.104765] radeon 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
  80. [ 60.104793] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xf (was 0x34001ff, writing 0x5c0010b)
  81. [ 60.104799] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xe (was 0x0, writing 0x40fc)
  82. [ 60.104804] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xd (was 0x0, writing 0x4000)
  83. [ 60.104810] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xc (was 0x0, writing 0x44fc)
  84. [ 60.104815] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xb (was 0x0, writing 0x4400)
  85. [ 60.104821] yenta_cardbus 0000:06:01.0: restoring config space at offset 0xa (was 0x0, writing 0x4bfff000)
  86. [ 60.104827] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x9 (was 0x0, writing 0x48000000)
  87. [ 60.104832] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x8 (was 0x0, writing 0x43fff000)
  88. [ 60.104838] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x7 (was 0x0, writing 0x40000000)
  89. [ 60.104844] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x6 (was 0x0, writing 0xb0080706)
  90. [ 60.104850] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x4 (was 0x0, writing 0xb0216000)
  91. [ 60.104856] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x3 (was 0x820000, writing 0x82a810)
  92. [ 60.104863] yenta_cardbus 0000:06:01.0: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100007)
  93. [ 60.104896] firewire_ohci 0000:06:01.2: restoring config space at offset 0xf (was 0x4030100, writing 0x403010b)
  94. [ 60.104912] firewire_ohci 0000:06:01.2: restoring config space at offset 0x5 (was 0x0, writing 0xb0210000)
  95. [ 60.104918] firewire_ohci 0000:06:01.2: restoring config space at offset 0x4 (was 0x0, writing 0xb0217000)
  96. [ 60.104924] firewire_ohci 0000:06:01.2: restoring config space at offset 0x3 (was 0x800000, writing 0x802008)
  97. [ 60.104931] firewire_ohci 0000:06:01.2: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100016)
  98. [ 60.104949] tifm_7xx1 0000:06:01.3: restoring config space at offset 0xf (was 0x40701ff, writing 0x407010b)
  99. [ 60.104965] tifm_7xx1 0000:06:01.3: restoring config space at offset 0x4 (was 0x0, writing 0xb0214000)
  100. [ 60.104971] tifm_7xx1 0000:06:01.3: restoring config space at offset 0x3 (was 0x800000, writing 0x803908)
  101. [ 60.104978] tifm_7xx1 0000:06:01.3: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
  102. [ 60.104996] ipw2200 0000:06:03.0: restoring config space at offset 0xf (was 0x18030100, writing 0x1803010b)
  103. [ 60.105013] ipw2200 0000:06:03.0: restoring config space at offset 0x4 (was 0x0, writing 0xb0218000)
  104. [ 60.105018] ipw2200 0000:06:03.0: restoring config space at offset 0x3 (was 0x0, writing 0x2008)
  105. [ 60.105025] ipw2200 0000:06:03.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900016)
  106. [ 60.105066] tg3 0000:06:08.0: restoring config space at offset 0x1 (was 0x2b00012, writing 0x2b00006)
  107. [ 60.105254] PM: early resume of devices complete after 1.212 msecs
  108. [ 60.105389] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
  109. [ 60.105395] uhci_hcd 0000:00:1d.0: setting latency timer to 64
  110. [ 60.105417] usb usb2: root hub lost power or was reset
  111. [ 60.105429] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
  112. [ 60.105435] uhci_hcd 0000:00:1d.1: setting latency timer to 64
  113. [ 60.105454] usb usb3: root hub lost power or was reset
  114. [ 60.105465] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
  115. [ 60.105470] uhci_hcd 0000:00:1d.2: setting latency timer to 64
  116. [ 60.105490] usb usb4: root hub lost power or was reset
  117. [ 60.105500] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
  118. [ 60.105505] uhci_hcd 0000:00:1d.3: setting latency timer to 64
  119. [ 60.105525] usb usb5: root hub lost power or was reset
  120. [ 60.105536] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
  121. [ 60.105542] ehci_hcd 0000:00:1d.7: setting latency timer to 64
  122. [ 60.105581] pci 0000:00:1e.0: setting latency timer to 64
  123. [ 60.105590] snd_intel8x0 0000:00:1e.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
  124. [ 60.105595] snd_intel8x0 0000:00:1e.2: setting latency timer to 64
  125. [ 60.105621] snd_intel8x0m 0000:00:1e.3: PCI INT B -> GSI 20 (level, low) -> IRQ 20
  126. [ 60.105627] snd_intel8x0m 0000:00:1e.3: setting latency timer to 64
  127. [ 60.105660] ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
  128. [ 60.105665] ata_piix 0000:00:1f.1: setting latency timer to 64
  129. [ 60.105719] tifm_7xx1 0000:06:01.3: PCI INT A -> GSI 18 (level, low) -> IRQ 18
  130. [ 60.105734] eth1: Coming out of suspend...
  131. [ 60.105741] ipw2200 0000:06:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
  132. [ 60.225741] firewire_core: skipped bus generations, destroying all nodes
  133. [ 60.225911] radeon 0000:01:00.0: power state changed by ACPI to D0
  134. [ 60.225917] radeon 0000:01:00.0: power state changed by ACPI to D0
  135. [ 60.225923] radeon 0000:01:00.0: power state changed by ACPI to D0
  136. [ 60.225927] radeon 0000:01:00.0: power state changed by ACPI to D0
  137. [ 60.225933] radeon 0000:01:00.0: setting latency timer to 64
  138. [ 60.225942] radeon 0000:01:00.0: f5fab200 unpin not necessary
  139. [ 60.226799] tg3 0000:06:08.0: wake-up capability disabled by ACPI
  140. [ 60.226806] tg3 0000:06:08.0: PME# disabled
  141. [ 60.227807] ata2: port disabled--ignoring
  142. [ 60.228085] sd 0:0:0:0: [sda] Starting disk
  143. [ 60.234736] [drm] PCIE GART of 512M enabled (table at 0xC0040000).
  144. [ 60.234746] [drm] radeon: 2 quad pipes, 1 z pipes initialized.
  145. [ 60.234754] radeon 0000:01:00.0: WB enabled
  146. [ 60.234787] [drm] radeon: ring at 0x00000000A0001000
  147. [ 60.234810] [drm] ring test succeeded in 1 usecs
  148. [ 60.234847] [drm] ib test succeeded in 0 usecs
  149. [ 61.202104] firewire_core: rediscovered device fw0
  150. [ 61.532579] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
  151. [ 61.532584] ata1.01: ACPI cmd ef/03:41:00:00:00:b0 (SET FEATURES) filtered out
  152. [ 61.540438] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
  153. [ 61.540442] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
  154. [ 61.558256] ata1.00: configured for UDMA/100
  155. [ 61.572471] ata1.01: configured for UDMA/33
  156. [ 61.720194] PM: resume of devices complete after 1614.909 msecs
  157. [ 61.720538] PM: Finishing wakeup.
  158. [ 61.720540] Restarting tasks ... done.
  159. [ 61.736236] video LNXVIDEO:00: Restoring backlight state
  160. [ 62.076247] Disabling lock debugging due to kernel taint
  161. [ 62.083479] ndiswrapper version 1.56 loaded (smp=yes, preempt=no)
  162. [ 62.111838] usbcore: registered new interface driver ndiswrapper
  163. [ 62.135971] ADDRCONF(NETDEV_UP): eth1: link is not ready
  164. [ 62.412589] ADDRCONF(NETDEV_UP): eth0: link is not ready
  165. [ 63.429487] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
  166. [ 63.814183] EXT4-fs (sda5): re-mounted. Opts: acl,user_xattr,commit=0
  167. [ 63.826934] EXT4-fs (sda6): re-mounted. Opts: acl,user_xattr,commit=0
m
0
l
22 Mars 2012 13:15:43

Après recherche, la mise en veille ne marche toujours pas, en cause la carte ATI.
Je n'ai toujours pas trouvé comment empêcher gnome de mette en veille lors de l'appuis sur le bouton power.

Conclusion : ATI à éviter avec linux, préférez nvidia ou mieux intel (pilote libre), et gnome n'est pas configurable (ça c'est une révélation).

m
0
l

Meilleure solution

2 Mai 2012 20:20:42

Ça-y-est, j'ai trouvé (entre temps, je suis passé sur archlinux, mais ça doit marcher partout) ! C'est par là => » Gnome3 - disable suspend [solved]

Citation :

To disable suspend and hibernation, add a file named 50-admin.pkla to:
/etc/polkit-1/localauthority/50-local.d

full path as reference: /etc/polkit-1/localauthority/50-local.d/50-admin.pkla

Add the following text to the file and save it. Log out and back in. This will remove suspend and hibernate from the shut down menus

[disable suspend]
Identity=unix-user:*
Action=org.freedesktop.upower.suspend
ResultAny=no
ResultInactive=no
ResultActive=no

[disable hibernate]
Identity=unix-user:*
Action=org.freedesktop.upower.hibernate
ResultAny=no
ResultInactive=no
ResultActive=no


Il falais jouer avec policykit :-)
partage
a b 5 Linux
3 Mai 2012 11:29:16

and the winner is : tantal_fr
m
0
l
3 Mai 2012 15:29:37

Merci zeb :jap: , la concurrence était rude.
m
0
l
21 Juillet 2013 20:42:37

Plop,

Je déterre le topic car depuis le passage à systemd, la solution est différente (la solution via policy-kit ne fonctionne plus):

Citation :

systemd handles some power-related ACPI events. They can be configured via the following options from /etc/systemd/logind.conf:
HandlePowerKey: specifies which action is invoked when the power key is pressed.
HandleSuspendKey: specifies which action is invoked when the suspend key is pressed.
HandleHibernateKey: specifies which action is invoked when the hibernate key is pressed.
HandleLidSwitch: specifies which action is invoked when the lid is closed.

The specified action can be one of ignore,
poweroff,
reboot,
halt,
suspend,
hibernate,
hybrid-sleep,
lock or
kexec.

If these options are not configured, systemd will use its defaults: HandlePowerKey=poweroff,
HandleSuspendKey=suspend,
HandleHibernateKey=hibernate, and
HandleLidSwitch=suspend.

Source : https://wiki.archlinux.org/index.php/Systemd#ACPI_power...
  1. HandlePowerKey=ignore
  2. HandleSuspendKey=ignore
  3. HandleHibernateKey=ignore
  4. HandleLidSwitch=ignore

Pour tout désactiver dans /etc/systemd/logind.conf

Sinon, j'ai trouvé une solution pour mes problèmes de reprise de veille corrompue :
Citation :

I got resuming-from-suspend to work by installing app-laptop/radeontool and executing the following after resuming from a suspend:
radeontool light off
radeonreg regset 0x00000284 0x1bd34208
radeonreg regset 0x000002d0 0x003c00a1
radeonreg regset CL:03 0x001c0007
radeonreg regset CL:04 0x0002004a
radeonreg regset CL:05 0x0002004a
radeonreg regset CL:06 0x0002004a
radeontool light on

(You can find what those values probably should be while it's working with "radeonreg regmatch CL:03" etc.)

Source : rapport de bug : https://bugzilla.redhat.com/show_bug.cgi?id=541562

Pour moi, les valueurs de CL:03, 4, 5 et 6 étais 0x00020047.

J'ai mis un hook dans /usr/lib/systemd/system-sleep
  1. # cat /usr/lib/systemd/system-sleep/radeon.sh
  2. #!/bin/sh
  3. case $1/$2 in
  4. pre/*)
  5. echo "Going to $2..."
  6. ;;
  7. post/*)
  8. echo "Waking up from $2..."
  9. radeontool light off
  10. radeonreg regset 0x00000284 0x1bd34208
  11. radeonreg regset 0x000002d0 0x003c00a1
  12. radeonreg regset CL:03 0x001c0007
  13. radeonreg regset CL:04 0x00020047
  14. radeonreg regset CL:05 0x00020047
  15. radeonreg regset CL:06 0x00020047
  16. radeontool light on
  17. ;;
  18. esac


Finalement, tout est pour le mieux dans le meilleur des mondes possibles.

m
0
l
21 Juillet 2013 20:45:22

Plop,

Je déterre le topic car depuis le passage à systemd, la solution est différente (la solution via policy-kit ne fonctionne plus):

Citation :

systemd handles some power-related ACPI events. They can be configured via the following options from /etc/systemd/logind.conf:
HandlePowerKey: specifies which action is invoked when the power key is pressed.
HandleSuspendKey: specifies which action is invoked when the suspend key is pressed.
HandleHibernateKey: specifies which action is invoked when the hibernate key is pressed.
HandleLidSwitch: specifies which action is invoked when the lid is closed.

The specified action can be one of ignore,
poweroff,
reboot,
halt,
suspend,
hibernate,
hybrid-sleep,
lock or
kexec.

If these options are not configured, systemd will use its defaults: HandlePowerKey=poweroff,
HandleSuspendKey=suspend,
HandleHibernateKey=hibernate, and
HandleLidSwitch=suspend.

Source : https://wiki.archlinux.org/index.php/Systemd#ACPI_power...
  1. HandlePowerKey=ignore
  2. HandleSuspendKey=ignore
  3. HandleHibernateKey=ignore
  4. HandleLidSwitch=ignore

Pour tout désactiver dans /etc/systemd/logind.conf

Sinon, j'ai trouvé une solution pour mes problèmes de reprise de veille corrompue :
Citation :

I got resuming-from-suspend to work by installing app-laptop/radeontool and executing the following after resuming from a suspend:
radeontool light off
radeonreg regset 0x00000284 0x1bd34208
radeonreg regset 0x000002d0 0x003c00a1
radeonreg regset CL:03 0x001c0007
radeonreg regset CL:04 0x0002004a
radeonreg regset CL:05 0x0002004a
radeonreg regset CL:06 0x0002004a
radeontool light on

(You can find what those values probably should be while it's working with "radeonreg regmatch CL:03" etc.)

Source : rapport de bug : https://bugzilla.redhat.com/show_bug.cgi?id=541562

Pour moi, les valueurs de CL:03, 4, 5 et 6 étais 0x00020047.

J'ai mis un hook dans /usr/lib/systemd/system-sleep
  1. # cat /usr/lib/systemd/system-sleep/radeon.sh
  2. #!/bin/sh
  3. case $1/$2 in
  4. pre/*)
  5. echo "Going to $2..."
  6. ;;
  7. post/*)
  8. echo "Waking up from $2..."
  9. radeontool light off
  10. radeonreg regset 0x00000284 0x1bd34208
  11. radeonreg regset 0x000002d0 0x003c00a1
  12. radeonreg regset CL:03 0x001c0007
  13. radeonreg regset CL:04 0x00020047
  14. radeonreg regset CL:05 0x00020047
  15. radeonreg regset CL:06 0x00020047
  16. radeontool light on
  17. ;;
  18. esac


Finalement, tout est pour le mieux dans le meilleur des mondes possibles.

m
0
l
21 Juillet 2013 20:58:07

Plop,

Je déterre le topic car depuis le passage à systemd, la solution est différente (la solution via policy-kit ne fonctionne plus):

Citation :

systemd handles some power-related ACPI events. They can be configured via the following options from /etc/systemd/logind.conf:
HandlePowerKey: specifies which action is invoked when the power key is pressed.
HandleSuspendKey: specifies which action is invoked when the suspend key is pressed.
HandleHibernateKey: specifies which action is invoked when the hibernate key is pressed.
HandleLidSwitch: specifies which action is invoked when the lid is closed.

The specified action can be one of ignore,
poweroff,
reboot,
halt,
suspend,
hibernate,
hybrid-sleep,
lock or
kexec.

If these options are not configured, systemd will use its defaults: HandlePowerKey=poweroff,
HandleSuspendKey=suspend,
HandleHibernateKey=hibernate, and
HandleLidSwitch=suspend.

Source : https://wiki.archlinux.org/index.php/Systemd#ACPI_power...
  1. HandlePowerKey=ignore
  2. HandleSuspendKey=ignore
  3. HandleHibernateKey=ignore
  4. HandleLidSwitch=ignore

Pour tout désactiver dans /etc/systemd/logind.conf

Sinon, j'ai trouvé une solution pour mes problèmes de reprise de veille corrompue :
Citation :

I got resuming-from-suspend to work by installing app-laptop/radeontool and executing the following after resuming from a suspend:
radeontool light off
radeonreg regset 0x00000284 0x1bd34208
radeonreg regset 0x000002d0 0x003c00a1
radeonreg regset CL:03 0x001c0007
radeonreg regset CL:04 0x0002004a
radeonreg regset CL:05 0x0002004a
radeonreg regset CL:06 0x0002004a
radeontool light on

(You can find what those values probably should be while it's working with "radeonreg regmatch CL:03" etc.)

Source : rapport de bug : https://bugzilla.redhat.com/show_bug.cgi?id=541562

Pour moi, les valueurs de CL:03, 4, 5 et 6 étais 0x00020047.

J'ai mis un hook dans /usr/lib/systemd/system-sleep
  1. # cat /usr/lib/systemd/system-sleep/radeon.sh
  2. #!/bin/sh
  3. case $1/$2 in
  4. pre/*)
  5. echo "Going to $2..."
  6. ;;
  7. post/*)
  8. echo "Waking up from $2..."
  9. radeontool light off
  10. radeonreg regset 0x00000284 0x1bd34208
  11. radeonreg regset 0x000002d0 0x003c00a1
  12. radeonreg regset CL:03 0x001c0007
  13. radeonreg regset CL:04 0x00020047
  14. radeonreg regset CL:05 0x00020047
  15. radeonreg regset CL:06 0x00020047
  16. radeontool light on
  17. ;;
  18. esac


Finalement, tout est pour le mieux dans le meilleur des mondes possibles.

m
0
l
21 Juillet 2013 20:47:45

Plop,

Je déterre le topic car depuis le passage à systemd, la solution est différente (la solution via policy-kit ne fonctionne plus):

Citation :

systemd handles some power-related ACPI events. They can be configured via the following options from /etc/systemd/logind.conf:
HandlePowerKey: specifies which action is invoked when the power key is pressed.
HandleSuspendKey: specifies which action is invoked when the suspend key is pressed.
HandleHibernateKey: specifies which action is invoked when the hibernate key is pressed.
HandleLidSwitch: specifies which action is invoked when the lid is closed.

The specified action can be one of ignore,
poweroff,
reboot,
halt,
suspend,
hibernate,
hybrid-sleep,
lock or
kexec.

If these options are not configured, systemd will use its defaults: HandlePowerKey=poweroff,
HandleSuspendKey=suspend,
HandleHibernateKey=hibernate, and
HandleLidSwitch=suspend.

Source : https://wiki.archlinux.org/index.php/Systemd#ACPI_power...
  1. HandlePowerKey=ignore
  2. HandleSuspendKey=ignore
  3. HandleHibernateKey=ignore
  4. HandleLidSwitch=ignore

Pour tout désactiver dans /etc/systemd/logind.conf

Sinon, j'ai trouvé une solution pour mes problèmes de reprise de veille corrompue :
Citation :

I got resuming-from-suspend to work by installing app-laptop/radeontool and executing the following after resuming from a suspend:
radeontool light off
radeonreg regset 0x00000284 0x1bd34208
radeonreg regset 0x000002d0 0x003c00a1
radeonreg regset CL:03 0x001c0007
radeonreg regset CL:04 0x0002004a
radeonreg regset CL:05 0x0002004a
radeonreg regset CL:06 0x0002004a
radeontool light on

(You can find what those values probably should be while it's working with "radeonreg regmatch CL:03" etc.)

Source : rapport de bug : https://bugzilla.redhat.com/show_bug.cgi?id=541562

Pour moi, les valueurs de CL:03, 4, 5 et 6 étais 0x00020047.

J'ai mis un hook dans /usr/lib/systemd/system-sleep
  1. # cat /usr/lib/systemd/system-sleep/radeon.sh
  2. #!/bin/sh
  3. case $1/$2 in
  4. pre/*)
  5. echo "Going to $2..."
  6. ;;
  7. post/*)
  8. echo "Waking up from $2..."
  9. radeontool light off
  10. radeonreg regset 0x00000284 0x1bd34208
  11. radeonreg regset 0x000002d0 0x003c00a1
  12. radeonreg regset CL:03 0x001c0007
  13. radeonreg regset CL:04 0x00020047
  14. radeonreg regset CL:05 0x00020047
  15. radeonreg regset CL:06 0x00020047
  16. radeontool light on
  17. ;;
  18. esac


Finalement, tout est pour le mieux dans le meilleur des mondes possibles.

m
0
l
22 Juillet 2013 07:54:11

DISCLAIMER : Le forum partant en sucette, il semblerais que ma réponse soit en plusieurs exemplaire (nombreuses erreurs 500 + 404 + autres bug). Je re-post une dernière fois et demande solennellement au maître des lieux de supprimer les posts en trop au dessus de celui-ci.

Plop,

Je déterre le topic car depuis le passage à systemd, la solution est différente (la solution via policy-kit ne fonctionne plus):

Citation :

systemd handles some power-related ACPI events. They can be configured via the following options from /etc/systemd/logind.conf:
HandlePowerKey: specifies which action is invoked when the power key is pressed.
HandleSuspendKey: specifies which action is invoked when the suspend key is pressed.
HandleHibernateKey: specifies which action is invoked when the hibernate key is pressed.
HandleLidSwitch: specifies which action is invoked when the lid is closed.

The specified action can be one of ignore,
poweroff,
reboot,
halt,
suspend,
hibernate,
hybrid-sleep,
lock or
kexec.

If these options are not configured, systemd will use its defaults: HandlePowerKey=poweroff,
HandleSuspendKey=suspend,
HandleHibernateKey=hibernate, and
HandleLidSwitch=suspend.

Source : https://wiki.archlinux.org/index.php/Systemd#ACPI_power...
  1. HandlePowerKey=ignore
  2. HandleSuspendKey=ignore
  3. HandleHibernateKey=ignore
  4. HandleLidSwitch=ignore

Pour tout désactiver dans /etc/systemd/logind.conf

Sinon, j'ai trouvé une solution pour mes problèmes de reprise de veille corrompue :
Citation :

I got resuming-from-suspend to work by installing app-laptop/radeontool and executing the following after resuming from a suspend:
radeontool light off
radeonreg regset 0x00000284 0x1bd34208
radeonreg regset 0x000002d0 0x003c00a1
radeonreg regset CL:03 0x001c0007
radeonreg regset CL:04 0x0002004a
radeonreg regset CL:05 0x0002004a
radeonreg regset CL:06 0x0002004a
radeontool light on

(You can find what those values probably should be while it's working with "radeonreg regmatch CL:03" etc.)

Source : rapport de bug : https://bugzilla.redhat.com/show_bug.cgi?id=541562

Pour moi, les valueurs de CL:03, 4, 5 et 6 étais 0x00020047.

J'ai mis un hook dans /usr/lib/systemd/system-sleep
  1. # cat /usr/lib/systemd/system-sleep/radeon.sh
  2. #!/bin/sh
  3. case $1/$2 in
  4. pre/*)
  5. echo "Going to $2..."
  6. ;;
  7. post/*)
  8. echo "Waking up from $2..."
  9. radeontool light off
  10. radeonreg regset 0x00000284 0x1bd34208
  11. radeonreg regset 0x000002d0 0x003c00a1
  12. radeonreg regset CL:03 0x001c0007
  13. radeonreg regset CL:04 0x00020047
  14. radeonreg regset CL:05 0x00020047
  15. radeonreg regset CL:06 0x00020047
  16. radeontool light on
  17. ;;
  18. esac


Finalement, tout est pour le mieux dans le meilleur des mondes possibles.


m
0
l