Kaum ist eine Baustelle geschlossen, tut sich schon die nächste auf:
nvram schreibt nicht mehr die korrekten Werte ins Bios! An den configs habe ich vorher nichts verändert. Gebe ich die Werte direkt über die Konsole ein, werden die Daten aber richtig ins Bios eingetragen, und der PC fährt hoch:
Das seltsame ist, das in den logs nichts negatives steht:
Code
Oct 23 00:02:59 debian vdr: [3544] confirm: System herunterfahren?
Oct 23 00:02:59 debian vdr: [3544] warning: System herunterfahren?
Oct 23 00:02:59 debian vdr: [3544] confirmed
Oct 23 00:02:59 debian vdr: [3544] executing command '/usr/bin/poweroffvdr'
Oct 23 00:03:01 debian vdr: [3544] connect from 127.0.0.1, port 36686 - accepted
Oct 23 00:03:01 debian vdr: [3544] Power button pressed
Oct 23 00:03:01 debian vdr: [3544] next timer event at Mon Oct 23 00:45:00 2006
Oct 23 00:03:01 debian vdr: [3544] confirm: Taste drücken, um Ausschalten abzubrechen
Oct 23 00:03:01 debian vdr: [3544] warning: Taste drücken, um Ausschalten abzubrechen
Oct 23 00:03:01 debian vdr: [3544] closing SVDRP connection
Oct 23 00:03:07 debian vdr: [3544] confirmed
Oct 23 00:03:07 debian vdr: [3544] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1161557100 2513 4 "Das Nachrichtenjournal" 1'
Oct 23 00:03:07 debian vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S10.hwclock as shell script
Oct 23 00:03:07 debian vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.noad as shell script
Oct 23 00:03:07 debian vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Oct 23 00:03:07 debian vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Oct 23 00:03:07 debian vdr-nvram-wakeup: /usr/sbin/nvram-wakeup -ls 1161557100 --directisa -C /etc/nvram-wakeup.conf
Oct 23 00:03:07 debian nvram-wakeup[3623]:
Oct 23 00:03:07 debian nvram-wakeup[3623]: All values are displayed as they are stored in the nvram/rtc.
Oct 23 00:03:07 debian nvram-wakeup[3623]: (and do not correspond necessarily to the system date/time)
Oct 23 00:03:07 debian nvram-wakeup[3623]:
Oct 23 00:03:07 debian nvram-wakeup[3623]: WakeUp : Enabled (0x5E)
Oct 23 00:03:07 debian nvram-wakeup[3623]: Hour : 23 (0x17)
Oct 23 00:03:07 debian nvram-wakeup[3623]: Minute : 59 (0x3B)
Oct 23 00:03:07 debian nvram-wakeup[3623]: Second : 27 (0x9B)
Oct 23 00:03:07 debian nvram-wakeup[3623]: rtcDay : 11 (0x11)
Oct 23 00:03:07 debian nvram-wakeup[3623]: rtcHour : 23
Oct 23 00:03:07 debian nvram-wakeup[3623]: rtcMin : 59
Oct 23 00:03:07 debian nvram-wakeup[3623]: rtcSec : 27
Oct 23 00:03:07 debian nvram-wakeup[3623]: Checksum: 0xFF36
Oct 23 00:03:07 debian nvram-wakeup[3623]:
Oct 23 00:03:07 debian nvram-wakeup[3623]: Enabling (0x5E) WakeUp-on-RTC in nvram.
Oct 23 00:03:07 debian nvram-wakeup[3623]: New Hour : 00 (0x00)
Oct 23 00:03:07 debian nvram-wakeup[3623]: New Minute : 40 (0x28)
Oct 23 00:03:07 debian nvram-wakeup[3623]: New Second : 00 (0x80)
Oct 23 00:03:07 debian nvram-wakeup[3623]: New rtcDay : 23 (0x23)
Oct 23 00:03:07 debian nvram-wakeup[3623]: New rtcHour : 00
Oct 23 00:03:07 debian nvram-wakeup[3623]: New rtcMin : 40
Oct 23 00:03:07 debian nvram-wakeup[3623]: New rtcSec : 00
Oct 23 00:03:07 debian nvram-wakeup[3623]: New Checksum: 0xFEF1
Oct 23 00:03:07 debian nvram-wakeup[3623]:
Oct 23 00:03:07 debian nvram-wakeup[3623]: Now really WRITING into /dev/nvram...
Oct 23 00:03:07 debian nvram-wakeup[3623]: And setting RTC alarm into /dev/rtc...
Oct 23 00:03:07 debian nvram-wakeup[3623]:
Oct 23 00:03:07 debian vdr-nvram-wakeup: nvram-wakeup: everything ok
Oct 23 00:03:07 debian shutdown[3626]: shutting down for system halt
Oct 23 00:03:07 debian init: Switching to runlevel: 0
Alles anzeigen
Und in meiner nvram-wakeupf.conf sieht auch alles normal aus:
Code
ENABLED="yes"
COMMANDLINE="--directisa -C /etc/nvram-wakeup.conf"
SPECIALSHUTDOWN="poweroff"
REGULAR_DAYS=0 # 0=disabled, 1=each day, 2=each 2'nd day, 3=...
REGULAR_TIME=01:00 # HH:MM
Was ist da nur los? Händisch läuft es, automatisch aber nicht?