Hello.
I'm trying to get nvram-wakeup working. My motherboard is supported with the latest CVS nvram-wakeup: Following DMI entries found: nvram-wakeup: - Mainboard vendor: "SHUTTLE INC" nvram-wakeup: - Mainboard type: "FX43" nvram-wakeup: - Mainboard revision: "" nvram-wakeup: - BIOS vendor: "Phoenix Technologies, LTD" nvram-wakeup: - BIOS version: "6.00 PG" nvram-wakeup: - BIOS release: "12/30/2003" nvram-wakeup: Using infowriter "shuttle_sk43g" (automatically detected) nvram-wakeup: Using following bios info:
but the clock seems to be set to hour (0xFF) and can't be set from nvram-wakeup : [root@media nvram-wakeup]# nvram-wakeup --directisa <snip> nvram-wakeup: Opening /dev/rtc in O_RDONLY mode... nvram-wakeup: Hardware clock: 2005-06-10 14:19:05 nvram-wakeup: rtc.tm_isdst : 1 nvram-wakeup: rtc.tm_gmtoff: 3600 nvram-wakeup: diff : 3600 nvram-wakeup: RTC is running in UTC/GMT! nvram-wakeup: Test (this should be the current time of the hardware clock): Fri Jun 10 14:19:05 2005 <snip> nvram-wakeup: value of the addr_stat byte is: 0x9F. nvram-wakeup: value of the addr_day byte is: 0xFF. nvram-wakeup: value of the addr_hour byte is: 0xFF. nvram-wakeup: value of the addr_min byte is: 0xFF. nvram-wakeup: value of the addr_sec byte is: 0xFF. nvram-wakeup: value of the addr_chk_h byte is: 0x1A. nvram-wakeup: value of the addr_chk_l byte is: 0x74. nvram-wakeup: Checksum is: 0x1A74. nvram-wakeup: WakeUp Hour value (31) not correct. [root@media nvram-wakeup]# nvram-wakeup --directisa -s $((`date +%s` + 20 * 60)) nvram-wakeup: WakeUp Hour value (31) not correct.
Any ideas?
On Fri, 10 Jun 2005, Simon Baxter (SB) wrote:
SB> nvram-wakeup: value of the addr_stat byte is: 0x9F. SB> nvram-wakeup: value of the addr_day byte is: 0xFF. SB> nvram-wakeup: value of the addr_hour byte is: 0xFF. SB> nvram-wakeup: value of the addr_min byte is: 0xFF. SB> nvram-wakeup: value of the addr_sec byte is: 0xFF. SB> nvram-wakeup: value of the addr_chk_h byte is: 0x1A. SB> nvram-wakeup: value of the addr_chk_l byte is: 0x74. SB> nvram-wakeup: Checksum is: 0x1A74. SB> nvram-wakeup: WakeUp Hour value (31) not correct.
Please go into your BIOS Setup, enable the wakeup and _change_ every value (day, hour, minute, second) of the wakeup time.
Then try running nvram-wakeup again.
On some boards this procedure will "initialize" the stored values to values which make sense.
Sergei
Thanks.
I changed the values in the BIOS, which seemed to work for that error.
Now I get :
WakeUp Second value (63) not correct
But there's no "second value" in the BIOS?? ----- Original Message ----- From: "Sergei Haller" Sergei.Haller@math.uni-giessen.de To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Friday, June 10, 2005 4:24 PM Subject: Re: [vdr] nvram-wakeup problems
On Fri, 10 Jun 2005, Simon Baxter (SB) wrote:
SB> nvram-wakeup: value of the addr_stat byte is: 0x9F. SB> nvram-wakeup: value of the addr_day byte is: 0xFF. SB> nvram-wakeup: value of the addr_hour byte is: 0xFF. SB> nvram-wakeup: value of the addr_min byte is: 0xFF. SB> nvram-wakeup: value of the addr_sec byte is: 0xFF. SB> nvram-wakeup: value of the addr_chk_h byte is: 0x1A. SB> nvram-wakeup: value of the addr_chk_l byte is: 0x74. SB> nvram-wakeup: Checksum is: 0x1A74. SB> nvram-wakeup: WakeUp Hour value (31) not correct.
Please go into your BIOS Setup, enable the wakeup and _change_ every value (day, hour, minute, second) of the wakeup time.
Then try running nvram-wakeup again.
On some boards this procedure will "initialize" the stored values to values which make sense.
Sergei-- -------------------------------------------------------------------- -?) eMail: Sergei.Haller@math.uni-giessen.de /\ -------------------------------------------------------------------- __V Be careful of reading health books, you might die of a misprint. -- Mark Twain
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.6 - Release Date: 08/06/2005
On Fri, 10 Jun 2005, Simon Baxter (SB) wrote:
SB> Thanks. SB> SB> I changed the values in the BIOS, which seemed to work for that error. SB> SB> Now I get : SB> SB> WakeUp Second value (63) not correct SB> SB> But there's no "second value" in the BIOS??
so you can't enter wakeup seconds in the BIOS setup, right?
please try this configuration file:
addr_stat = 0xD2 shift_stat = 5 addr_day = 0xD8 addr_hour = 0xD9 addr_min = 0xDA addr_chk_h = 0xDE addr_chk_l = 0xDF
upper_method = VT8235_37 need_reboot = ON_STAT
and let me know if it works.
Sergei
On Fri, 10 Jun 2005, Simon Baxter (SB) wrote:
SB> Thanks. SB> SB> I changed the values in the BIOS, which seemed to work for that error. SB> SB> Now I get : SB> SB> WakeUp Second value (63) not correct SB> SB> But there's no "second value" in the BIOS??
so you can't enter wakeup seconds in the BIOS setup, right?
please try this configuration file:
addr_stat = 0xD2 shift_stat = 5 addr_day = 0xD8 addr_hour = 0xD9 addr_min = 0xDA addr_chk_h = 0xDE addr_chk_l = 0xDF
upper_method = VT8235_37 need_reboot = ON_STAT
and let me know if it works.
Thanks Sergei
My mistake - I'd not set the Seconds value in the BIOS. Set that, and now nvram-wakeup works fine - apart from the time being wrong (daylight saving, so the system time is an hour behind the actual time)
How do I now integrate it with VDR? The WIKI isn't very useful! http://www.linuxtv.org/vdrwiki/index.php/Nvram_wakeup#Installation
[root@media ~]# nvram-wakeup --directisa
All values are displayed as they are stored in the nvram/rtc. (and do not correspond necessarily to the system date/time)
WakeUp : Enabled (0xBF) Day : 10 (0x0A) Hour : 21 (0x15) Minute : 45 (0x2D) Second : 10 (0x0A) Checksum: 0x16EE
[root@media ~]# date Fri Jun 10 22:56:07 BST 2005 [root@media ~]#
On Fri, 10 Jun 2005, Simon Baxter (SB) wrote:
SB> SB> Thanks Sergei SB> SB> My mistake - I'd not set the Seconds value in the BIOS. Set that, and now SB> nvram-wakeup works fine - apart from the time being wrong (daylight saving, SB> so the system time is an hour behind the actual time) SB> SB> How do I now integrate it with VDR?
just pass the script vdrshutdown (in the VDR directory of nvram-wakeup) to the option -s of vdr. E.g.,
vdr -s /path/to/vdrshutdown ...
Sergei
-
Sergei Haller -
Simon Baxter