reboot bei nvram

  • Hallo,


    mein nvram wakeup tut nicht ganz das was er soll. Statt sich schlafenzulegen wird einfach ein reboot durchgeführt.
    Im Log sieht das ganze so aus:



    Dec 4 16:05:18 hdvdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
    Dec 4 16:05:18 hdvdr vdr-nvram-wakeup: /usr/sbin/nvram-wakeup -ls 1291481880 -C /etc/nvram-wakeup.conf --directisa
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]:
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: All values are displayed as they are stored in the nvram/rtc.
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: (and do not correspond necessarily to the system date/time)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]:
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: WakeUp : Enabled (0xFF)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Day : 03 (0x03)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Hour : 16 (0x10)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Minute : 53 (0x75)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Second : 00 (0x03)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Checksum: 0x1AEE
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]:
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Enabling (0xFF) WakeUp-on-RTC in nvram.
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: New Day : 04 (0x04)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: New Hour : 16 (0x10)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: New Minute : 53 (0x75)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: New Second : 00 (0x03)
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: New Checksum: 0x1AEF
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]:
    Dec 4 16:05:18 hdvdr nvram-wakeup[2259]: Now really WRITING into /dev/nvram...
    Dec 4 16:05:18 hdvdr vdr-nvram-wakeup: nvram-wakeup: everything ok
    Dec 4 16:05:18 hdvdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
    Dec 4 16:05:18 hdvdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
    Dec 4 16:05:18 hdvdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
    Dec 4 16:05:56 hdvdr vdr-sxfe[1859]: [1859] [vdr-fe] caught signal 15
    Dec 4 16:05:58 hdvdr vdr: [2216] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE)
    Dec 4 16:05:58 hdvdr vdr: last message repeated 140 times
    Dec 4 16:05:58 hdvdr kernel: [80662.047399] nfsd: last server has exited, flushing export cache
    Dec 4 16:05:58 hdvdr vdr: [2216] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE)
    Dec 4 16:05:58 hdvdr vdr: last message repeated 53 times
    Dec 4 16:05:58 hdvdr vdr: [867] [xine..put] Closing connection 0
    Dec 4 16:05:59 hdvdr vdr: [867] [xine..put] cXinelibOsdProvider: shutting down !
    Dec 4 16:05:59 hdvdr vdr-sxfe[1859]: [1864] [vdr-fe] caught signal 13
    Dec 4 16:06:02 hdvdr kernel: Kernel logging (proc) stopped.
    Dec 4 16:06:02 hdvdr rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="941" x-info="http://www.rsyslog.com"] exiting on signal 15.
    Dec 4 16:06:35 hdvdr kernel: imklog 4.2.0, log source = /proc/kmsg started.



    ... irgendwelche gute Ideen?



    Danke!

    yavdr 0.6: Gigabyte GA H61M, Pentium 645, 4GB RAM, 1x3 TB, 1x64 GB SSD, 1x CineS2 V6, 1x Hauppauge S2-1600 , Nvidia GF210

    ansible@focal: Asrock Z370 Exteme4, Intel i3, 8GB RAM, 1x64GB SSD, 1x2TB HDD, 1xDVB Skystar 952, GF1030

  • Mal nach oben schieb und hoff...

    yavdr 0.6: Gigabyte GA H61M, Pentium 645, 4GB RAM, 1x3 TB, 1x64 GB SSD, 1x CineS2 V6, 1x Hauppauge S2-1600 , Nvidia GF210

    ansible@focal: Asrock Z370 Exteme4, Intel i3, 8GB RAM, 1x64GB SSD, 1x2TB HDD, 1xDVB Skystar 952, GF1030

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!