maniac@maniac-envy:~$ uname -a
Linux maniac-envy 3.1.0-030100rc10-generic #201110200610 SMP Thu Oct 20 10:11:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
The behavior is the same.
I also looked into /var/log and it appears three files consistently have new messages upon *opening* the lid, but nothing on closing:
auth.log:
Oct 21 11:18:24 maniac-envy su[3099]: Successful su for maniac by root
Oct 21 11:18:24 maniac-envy su[3099]: + ??? root:maniac
Oct 21 11:18:24 maniac-envy su[3099]: pam_unix(su:session): session opened for user maniac by (uid=0)
Oct 21 11:18:25 maniac-envy su[3099]: pam_unix(su:session): session closed for user maniac
syslog and kern.log:
Oct 21 11:18:24 maniac-envy kernel: [ 390.672734] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
Another small observation is that the screen itself switches off in the closed state but it's probably a purely hardware switch…
Running the new kernel:
maniac@ maniac- envy:~$ uname -a 0-generic #201110200610 SMP Thu Oct 20 10:11:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Linux maniac-envy 3.1.0-030100rc1
The behavior is the same.
I also looked into /var/log and it appears three files consistently have new messages upon *opening* the lid, but nothing on closing:
auth.log:
Oct 21 11:18:24 maniac-envy su[3099]: Successful su for maniac by root su:session) : session opened for user maniac by (uid=0) su:session) : session closed for user maniac
Oct 21 11:18:24 maniac-envy su[3099]: + ??? root:maniac
Oct 21 11:18:24 maniac-envy su[3099]: pam_unix(
Oct 21 11:18:25 maniac-envy su[3099]: pam_unix(
syslog and kern.log:
Oct 21 11:18:24 maniac-envy kernel: [ 390.672734] [drm:ironlake_ update_ pch_refclk] *ERROR* enabling SSC on PCH
Another small observation is that the screen itself switches off in the closed state but it's probably a purely hardware switch…