A friend (thanks FrodoBaggins!) suggested Bug#646429 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646429) may be the same problem. Indeed, the contents of /proc/driver/rtc look like this:
rtc_time : 02:30:46 rtc_date : 2011-12-29 alrm_time : 07:05:49 alrm_date : ****-02-30 alarm_IRQ : no alrm_pending : no 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : no DST_enable : no periodic_freq : 1024 batt_status : okay Indeed: stars. After entering "echo +300 > /sys/class/rtc/rtc0/wakealarm" a proper value is shown, but is instantly forgotten on reboot or powerdown. A couple of kernel-reloadings using kexec appear to show that updating the wakealarm makes the difference between kernel 3.1 booting or not. I haven't tried his patch, for two reasons: #1 I'm not very experienced with kernel compilation. #2 It would take approximately two eternities on the laptop in question. But assuming there's nothing totally wacky in the patch, it would most likely be the solution indeed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
