Bonsoir à tous,
Je viens d’acquérir un nouveau laptop (un Toshiba R830). Je l’ai installé sous SID. Tout fonctionne super bien sauf le suspend to ram. Il ne se met pas en veille du tout quand je rabats l’écran, il vérouille juste la session. Sur mon Asus UX21 j’utilisais ce script pour décharger les modules USB :
EHCI_BUSES="0000:00:1a.0 0000:00:1d.0"
case "${1}" in
hibernate|suspend)
# Switch USB buses off
for bus in $EHCI_BUSES; do
echo -n $bus > /sys/bus/pci/drivers/ehci_hcd/unbind
done
;;
resume|thaw)
# Switch USB buses back on
for bus in $EHCI_BUSES; do
echo -n $bus > /sys/bus/pci/drivers/ehci_hcd/bind
done
;;
esac
J’ai tenté de le réutiliser mais rien n’y fait. Je ne sais pas quoi faire d’autre. Voici ce que dit le syslog lors de la tentative de mise en veille :
[code]May 13 21:24:37 steelers NetworkManager[1623]: sleep requested (sleeping: no enabled: yes)
May 13 21:24:37 steelers NetworkManager[1623]: sleeping or disabling…
May 13 21:24:37 steelers NetworkManager[1623]: (eth0): now unmanaged
May 13 21:24:37 steelers NetworkManager[1623]: (eth0): device state change: unavailable -> unmanaged (reason ‘sleeping’) [20 10 37]
May 13 21:24:37 steelers NetworkManager[1623]: (eth0): cleaning up…
May 13 21:24:37 steelers NetworkManager[1623]: (eth0): taking down device.
May 13 21:24:37 steelers kernel: [ 3564.775837] CPU3: Package power limit notification (total events = 267)
May 13 21:24:37 steelers kernel: [ 3564.775841] CPU2: Package power limit notification (total events = 267)
May 13 21:24:37 steelers kernel: [ 3564.775845] CPU0: Package power limit notification (total events = 266)
May 13 21:24:37 steelers kernel: [ 3564.775848] CPU1: Package power limit notification (total events = 267)
May 13 21:24:37 steelers kernel: [ 3564.776255] CPU0: Package power limit normal
May 13 21:24:37 steelers kernel: [ 3564.776258] CPU3: Package power limit normal
May 13 21:24:37 steelers kernel: [ 3564.776260] CPU1: Package power limit normal
May 13 21:24:37 steelers kernel: [ 3564.776263] CPU2: Package power limit normal
May 13 21:24:37 steelers avahi-daemon[2063]: Interface eth0.IPv6 no longer relevant for mDNS.
May 13 21:24:37 steelers avahi-daemon[2063]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::eae0:b7ff:feab:7253.
May 13 21:24:37 steelers avahi-daemon[2063]: Withdrawing address record for fe80::eae0:b7ff:feab:7253 on eth0.
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): now unmanaged
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): device state change: activated -> unmanaged (reason ‘sleeping’) [100 10 37]
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): deactivating device (reason ‘sleeping’) [37]
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): canceled DHCP transaction, DHCP client pid 12215
May 13 21:24:37 steelers kernel: [ 3565.027589] wlan0: deauthenticating from 00:22:75:f4:ee:16 by local choice (reason=3)
May 13 21:24:37 steelers kernel: [ 3565.046615] wlan0: moving STA 00:22:75:f4:ee:16 to state 2
May 13 21:24:37 steelers kernel: [ 3565.046618] wlan0: moving STA 00:22:75:f4:ee:16 to state 1
May 13 21:24:37 steelers kernel: [ 3565.046620] wlan0: moving STA 00:22:75:f4:ee:16 to state 0
May 13 21:24:37 steelers kernel: [ 3565.078926] cfg80211: Calling CRDA to update world regulatory domain
May 13 21:24:37 steelers wpa_supplicant[1691]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
May 13 21:24:37 steelers avahi-daemon[2063]: Withdrawing address record for 192.168.0.240 on wlan0.
May 13 21:24:37 steelers avahi-daemon[2063]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.240.
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): cleaning up…
May 13 21:24:37 steelers avahi-daemon[2063]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 13 21:24:37 steelers NetworkManager[1623]: (wlan0): taking down device.
May 13 21:24:37 steelers kernel: [ 3565.086287] cfg80211: World regulatory domain updated:
May 13 21:24:37 steelers kernel: [ 3565.086290] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 13 21:24:37 steelers kernel: [ 3565.086293] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 13 21:24:37 steelers kernel: [ 3565.086296] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 13 21:24:37 steelers kernel: [ 3565.086299] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 13 21:24:37 steelers kernel: [ 3565.086301] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 13 21:24:37 steelers kernel: [ 3565.086304] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 13 21:24:37 steelers avahi-daemon[2063]: Interface wlan0.IPv6 no longer relevant for mDNS.
May 13 21:24:37 steelers avahi-daemon[2063]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::9eb7:dff:fe72:6f40.
May 13 21:24:37 steelers avahi-daemon[2063]: Withdrawing address record for fe80::9eb7:dff:fe72:6f40 on wlan0.
May 13 21:24:37 steelers dbus[1575]: [system] Activating service name=‘org.freedesktop.nm_dispatcher’ (using servicehelper)
May 13 21:24:37 steelers dbus[1575]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher’
May 13 21:24:39 steelers NetworkManager[1623]: wake requested (sleeping: yes enabled: yes)
May 13 21:24:39 steelers NetworkManager[1623]: waking up and re-enabling…
May 13 21:24:39 steelers NetworkManager[1623]: (eth0): now managed
May 13 21:24:39 steelers NetworkManager[1623]: (eth0): device state change: unmanaged -> unavailable (reason ‘managed’) [10 20 2]
May 13 21:24:39 steelers NetworkManager[1623]: (eth0): bringing up device.
May 13 21:24:39 steelers kernel: [ 3566.626407] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
May 13 21:24:39 steelers NetworkManager[1623]: (eth0): preparing device.
May 13 21:24:39 steelers NetworkManager[1623]: (eth0): deactivating device (reason ‘managed’) [2]
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): now managed
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): device state change: unmanaged -> unavailable (reason ‘managed’) [10 20 2]
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): bringing up device.
May 13 21:24:39 steelers kernel: [ 3566.681622] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
May 13 21:24:39 steelers kernel: [ 3566.682418] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): preparing device.
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): deactivating device (reason ‘managed’) [2]
May 13 21:24:39 steelers kernel: [ 3566.700093] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): supplicant interface state: starting -> ready
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): device state change: unavailable -> disconnected (reason ‘supplicant-available’) [20 30 42]
May 13 21:24:39 steelers NetworkManager[1623]: (wlan0): supplicant interface state: ready -> inactive
May 13 21:24:39 steelers NetworkManager[1623]: Trying to remove a non-existant call id.
[/code]
Il semble que dbus réveille de suite le portable.
Si quelqu’un pouvait m’indiquer une piste ou deux car c’est plutôt génant …
Qui plus est j’ai fait quelques recherches, et mis à part le souci avec la luminosité, ça a l’air de fonctionner.