CTVDR 4 + NVRAM - kein Runterfahren nach Reboot
Hallo, ich habe mich vor 2 Wochen an den CTVDR4 rangetraut. Installation hat auch mit einigen Holpereien geklappt.
Sogar NVRAM lief mit meinem alten Board. Es brauchte keinen Reboot und er ist brav mit meiner alten conf aufgewacht.
Nun habe ich seit dem Wochenende ein Board, dass einen Reboot für NVRAM benötigt und nach 4 Tagen Sucherei gebe ich jetzt auf und brauche HILFE.
Also... ich habe:
VDR: Board ASRock K7VT4APro mit AMD Sempron 2400+, 512 MB RAM, 40 + 160 GB HD
**************************************
* c't VDR Übersicht *
**************************************
c't VDR: 1.2.6-34
Kernel : 2.4.30-ct-1
Patches:
--------------------------------------
recordings-0.0.2
disableDoubleEpgEntries-0.6
elchiaio4d
fix-black-square
ac3overdvb-0.2.4
wareagleicons_elchi
ttxtsubs_ac3
switchtimer-0.0.4-wareagle
jumpplay-0.5
8bitcolor
osdpip-0.0.3
Plugins:
( N = Native Plugin )
( ! = Falscher Patchlevel )
--------------------------------------
vdr-plugin-streamdev-server (0.3.1-4)
vdr-plugin-autotimeredit (0.1.4-1)
vdr-plugin-burn (0.0.5-3)
vdr-plugin-femon (0.0.7-3)
vdr-plugin-mp3 (0.9.12-2)
vdr-plugin-mplayer (0.9.12-2)
vdr-plugin-osdpip (0.0.6-2)
vdr-plugin-remote (0.3.3-2)
vdr-plugin-timeline (0.9.0-1)
vdr-plugin-undelete (0.0.2-1)
vdr-plugin-vcd (0.0.6c-3)
vdr-plugin-vdrrip (0.3.0-4)
vdr-plugin-dvd (0.3.4-rc10-5)
vdr-plugin-dvdselect (0.7a-4)
vdr-plugin-solitaire (0.0.1-2)
Addon Packages:
--------------------------------------
vdr-addon-icons (0.5)
vdr-addon-noad (0.6.0-1)
vdr-addon-schemes (0.3)
vdr-addon-tosvcd (0.9-6)
vdr-addon-tvmovie2vdr (0.5.3-1)
vdr-addon-vdrconvert (0.1.1-6)
**************************************
NVRAM ist "enabled"
nach guess-helper ist folgende conf ausgespuckt worden
einige Zeilen habe ich bereits auskommentiert und need_reboot aus einem anderen K7VT4A Board übernommen.
################################################
## Mainboard autodetection information:
##
## - Mainboard vendor: "ASRock"
## - Mainboard type: "K7VT4APro"
## - Mainboard revision: "1.0x"
## - BIOS vendor: "American Megatrends Inc."
## - BIOS version: "P1.10"
## - BIOS release: "12/08/2004"
need_reboot = ON_ANY_CHANGE
addr_stat = 0x57
#shift_stat = 5
addr_day = 0x58
addr_hour = 0x59
addr_min = 0x5A
addr_sec = 0x5B
#addr_stat = 0x6F # but differs somewhere else
rtc_day = 0x6F
reset_day = ON
#rtc_sec = 0x73
#rtc_min = 0x75
#rtc_hour = 0x77
addr_chk_h = 0x30
addr_chk_l = 0x31
**********************************************
das ist der Auszug aus dem Messages-log:
Jul 27 07:50:25 localhost vdr-nvram-wakeup: /usr/sbin/nvram-wakeup -ls 1122445800 -C /etc/nvram-wakeup.conf
Jul 27 07:50:25 localhost kernel: Non-volatile memory driver v1.2
Jul 27 07:50:25 localhost nvram-wakeup[5387]:
Jul 27 07:50:25 localhost nvram-wakeup[5387]: All values are displayed as they are stored in the nvram/rtc.
Jul 27 07:50:25 localhost nvram-wakeup[5387]: (and do not correspond necessarily to the system date/time)
Jul 27 07:50:25 localhost nvram-wakeup[5387]:
Jul 27 07:50:25 localhost nvram-wakeup[5387]: WakeUp : Enabled (0x05)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Day : 27 (0x1B)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Hour : 05 (0x05)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Minute : 45 (0xAD)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Second : 00 (0x00)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: rtcDay : 00 (0x00)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Checksum: 0xABCE
Jul 27 07:50:25 localhost nvram-wakeup[5387]:
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Enabling (0x05) WakeUp-on-RTC in nvram.
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New Day : 27 (0x1B)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New Hour : 06 (0x06)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New Minute : 25 (0x99)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New Second : 00 (0x00)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New rtcDay : 27 (0x27)
Jul 27 07:50:25 localhost nvram-wakeup[5387]: New Checksum: 0xABBB
Jul 27 07:50:25 localhost nvram-wakeup[5387]:
Jul 27 07:50:25 localhost nvram-wakeup[5387]: Now really WRITING into /dev/nvram...
Jul 27 07:50:25 localhost nvram-wakeup[5387]: The changes to take effect, you must reboot your computer now.
Jul 27 07:50:25 localhost nvram-wakeup[5387]:
Jul 27 07:50:25 localhost vdr-nvram-wakeup: nvram-wakeup: everything ok - need to reboot first
*****************************************
er fährt runter, rebootet... und dann fährt der kleine Mistkerl nicht mehr runter.
Dieser Fehler wurde bereits von Berni123 für CTVDR3 gelöst, aber leider gibt es bei dem CTVDR4 kein lilo mehr *grrr* und jetzt habe ich keine Ahnung, wo ich ansetzen muß.
hier noch meine vdr-nvram-wakeup-conf - mit lilo hatte ich es zuerst probiert und dann einfach von der CT Seite den einzigen Hinweis auf die 4 reinkopiert...
#
# Configuration file for the VDR nvram-wakeup shutdown hook
#
# This is NOT the nvram-wakeup configuration file, which you can find in
# /etc/nvram-wakeup.conf and which must be set in COMMANDLINE (see below),
# if your mainboard ins not detected automatically.
#
# Set to "yes" to enable nvram-wakeup for VDR
#
ENABLED="yes"
# Here you can specify additional command line parameters, that will be passed
# to nvram-wakeup.
#
# i.e.:
# COMMANDLINE="-I ecs_k7s5au" # mainboard of type K7S5au
# COMMANDLINE="-C /etc/nvram-wakeup.conf" # use config file
#
# see "man nvram-wakeup"
#
COMMANDLINE="-I asrock_k7vt4a"
COMMANDLINE="-C /etc/nvram-wakeup.conf"
# If your mainboard needs to reboot before shutting down, set the command(s) to
# do this here. i.e.:
#
# SPECIALSHUTDOWN="lilo -R PowerOff ; shutdown -r now"
# SPECIALSHUTDOWN="savedefault --default=POSITION --once quit | /sbin/grub --batch; shutdown -r now"
#
SPECIALSHUTDOWN="savedefault --default=3 --once quit | /sbin/grub --batch; shutdown -r now"
# To force a reboot whenever nvram-wakeup sets the time, independently of
# whether a reboot is required, enable this option.
#
# FORCE_REBOOT="yes"
#
# If you want your VDR machine to wakeup in regular intervals (i.e. for
# updating EPG data), specify a day interval and a wakeup time:
#
#REGULAR_DAYS=0 # 0=disabled, 1=each day, 2=each 2'nd day, 3=...
#REGULAR_TIME=01:00 # HH:MM
*************************************************
und meine S90.nvram-wakeup:
#
# VDR shutdown hook for nvram-wakeup - Tobias Grimm <tg@e-tobi.net>
# ----------------------------------
#
# This shutdown hook sets the wakeup time for the next timer using
# nvram-wakeup. If necessary the shutdown command is modified to
# use a special shutdown strategy.
#
NVRAMCMD=/usr/sbin/nvram-wakeup
# read arguments for nvram-wakeup from conf-file
. /etc/vdr/vdr-nvram-wakeup.conf
# Defaults:
[ -z "$ENABLED" ] && export ENABLED="no"
[ -z "$COMMANDLINE" ] && export COMMANDLINE=""
[ -z "$SPECIALSHUTDOWN" ] && export SPECIALSHUTDOWN=""
[ -z "$REGULAR_DAYS" ] && export REGULAR_DAYS=0
[ -z "$REGULAR_TIME" ] && export REGULAR_TIME=0
[ -z "$FORCE_REBOOT" ] && export FORCE_REBOOT="no"
LOG="logger -t vdr-nvram-wakeup"
if [ $ENABLED = "no" ] ; then
$LOG "nvram-wakeup functionality is disabled"
exit 0
fi
request_reboot()
{
if [ -z "$SPECIALSHUTDOWN" ] ; then
$LOG "nvram-wakeup: A special shutdown strategy is required but not configured."
echo "ABORT_MESSAGE=\"no special shutdown configured\""
exit 1
else
echo "SHUTDOWNCMD=\"$SPECIALSHUTDOWN\""
exit 0
fi
}
# calculate, at what time the machine should be powered on:
TIMER=$1
if [ $REGULAR_DAYS -gt 0 ]; then
REGULAR_TIMER=$((`date -d "$REGULAR_TIME" +%s` + $REGULAR_DAYS * 24 * 60 * 60))
# when no vdr timer is set or vdr timer starts later than regular timer:
if [ $TIMER -eq 0 ] 
[ $TIMER -gt 0 -a $REGULAR_TIMER -lt $TIMER ] ; then
TIMER=$REGULAR_TIMER
fi
fi
# set wakeup time and check nvram-wakeup and check result:
$LOG "$NVRAMCMD -ls $TIMER $COMMANDLINE"
$NVRAMCMD -ls $TIMER $COMMANDLINE
case $PIPESTATUS in
0) # all went ok - new date and time set
$LOG "nvram-wakeup: everything ok"
if [ $FORCE_REBOOT = "yes" ] ; then
$LOG "nvram-wakeup: reboot not needed but forced"
request_reboot
fi
exit 0
;;
1) # all went ok - new date and time set.
#
# *** but we need to reboot. ***
#
# for some boards this is needed after every change.
#
# for some other boards, we only need this after changing the
# status flag, i.e. from enabled to disabled or the other way.
# For plan A - (Plan A is not supported anymore---see README)
#
# For plan B - (don't forget to install the modified kernel image first)
#
$LOG "nvram-wakeup: everything ok - need to reboot first"
request_reboot
;;
*) # something went wrong
# don't do anything - just exit with status 1
$LOG "nvram-wakeup: could not set time, shutdown will be aborted"
echo "ABORT_MESSAGE=\"nvram-wakeup could not set time\""
exit 1
;;
esac
************************************************
hat jemand noch eine Idee, wie ich nvram und grub dazu bringen kann vernünftig zu arbeiten.
Vielen Dank schon mal
Gruß Britta
