clone 555712 -1 retitle 555712 "wrong status for can-hibernate" retitle -1 "wrong status for lid-is-present" thanks
On mer., 2009-11-11 at 16:04 +0100, Michael Biebl wrote: > Yves-Alexis Perez wrote: > > This is on a ThinkPad T61 which indeed has a LID and can hibernate > just fine > > (even if I have problems at resume but that's not the point). Not > sure if it's > > related but I use full disk encryption using dm-crypt/luks (as > proposed by > > d-i, so the swap is inside). I saw in #551797 that encrypted swap > leaded to > > impossible hibernate but I don't think it's true (since I can > hibernate just > > fine using direct commands or hal). > > hal or pm-suspend do not check for encrypted swap. > > See the following commit > http://cgit.freedesktop.org/DeviceKit/DeviceKit-power/commit/?id=ea6eb > d1a526653bb9d59d5143d844c0f7557a351 Well, the main point of having encrypted swap is for hibernation. It doesn't really make sense to disable hibernate in those case. > > So the output of /proc/swaps and /proc/crypttab would probably be > helpful. /proc/swap: ---- Filename Type Size Used Priority /dev/mapper/hidalgo-swap_1 partition 1048568 117996 -1 ---- /etc/crypttab: ---- sda5_crypt /dev/sda5 none luks ---- > > Also, the lid state should be handled in a separate bug and not mixed > into this > one. It is most certainly a kernel bug, as DK-power just reads the > sysfs values > via libudev. Ok, I cloned the bug so we can track it separately. Thanks for your time, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
