vdr@xxxxxxxxxxxx(Alfred Zastrow) 29.05.05 07:28 >Rainer Zocholl schrieb: >[...] >> # nvram-wakeup -s $((`date +%s`+ 10 * 60)) >> >> Box does not wake up anymore. >> >> With 2.4.2x i had no such problem. >[...] >If you don't find a solution to get NVRAM-wakeup working try my >ACPI-wakeup. >The setup is pretty simple and with a little bit of luck your >motherboard is also able, to start on this way. >You can download it from here: >http://www.zastrow4u.de/download/acpi-wakeup-0.1.tar.bz2 Thanks for the and the informative readme. msi:~/video/nvram/acpi-wakeup-0.1# cat /proc/acpi/alarm 2005-**-29 18:36:05 That does not look good, or what is the meaning of "-**-" ? (i never used /proc/acpi/alarm before) instead of "echo "YYYY-MM-DD HH:MM:SS" >/proc/acpi/alarm" i used: date --date "+10 min" +"%F %T" >/proc/acpi/alarm #date --date "+10 min" +"%Y-%m-%d %H:%M:%S" or less transparent: # date --date "+10 min" +"%F %T" >/proc/acpi/alarm # cat /proc/acpi/alarm 2005-05-29 21:47:36 to set /proc/acpi/alarm with the seconds since 1970 as VDR delivers #date -d "1970-01-01 $1 sec -5 min" +"%Y-%m-%d %H:%M:%S" > /proc/acpi/alarm would be sufficient. ("-u" or "--utc" to make universal time) (Attention: write "-5" not "- 5") But attention: The line above might set the time in the past! nvram-wakeup does additional things: - It refuses to set a time below 10 Minutes in future - and it set the alaram 5 minutes before the expected time. That is done because a shutdown may last 5 minutes and a boot might last 5 minutes too (assume fsck!) - it checks if the RTC is running UTC or not. But anyhow: msi:~# date --date "+3 min" +"%F %T" >/proc/acpi/alarm ; cat /proc/acpi/alarm 2005-05-29 22:10:23 msi:~# halt Broadcast message from root (pts/0) (Sun May 29 22:06:38 2005): The system is going down for system halt NOW! box powers off. Box does not wake up. The alarm time does not show up in the BIOS. - Is the hardware clock touched from the shutdown scripts? (with hwclock?) -> comment out this lines Why? Hm, i saw that somewhere... msi:/etc/init.d# mv /etc/rc0.d/K25hwclock.sh /etc/rc0.d/_K25hwclock.sh msi:/etc/init.d# mv /etc/rc6.d/K25hwclock.sh /etc/rc6.d/_K25hwclock.sh too i disabled the alarm time in BIOS now And now: it wakes up! (but the BIOS still shows a wrong time) Wow! Is that maybe the reason why nvram-wakeup sometimes need a reboot to work? BTW: Is there anywhere a description of all "--date" formats? Rainer
