So, also so schauts vor der Änderung in der runvdr aus:
linvdr:~# lsmod
Module Size Used by
lirc_serial 7648 1
dvb-ttpci 299956 4
evdev 4536 0 (unused)
ves1820 4216 0
stv0299 6548 0 (unused)
grundig_29504-491 3184 0
grundig_29504-401 3532 0
alps_tdlb7 4872 0
alps_tdmb7 3268 0
alps_bsrv2 3428 1
dvb-core 36644 15 [dvb-ttpci ves1820 stv0299 grundig_29504-491 grundig_29504-401 alps_tdlb7 alps_tdmb7 alps_bsrv2]
videodev 3936 1 [dvb-ttpci]
bcm4400 29324 1
nvram 4168 0 (unused)
keybdev 1680 0 (unused)
hid 12964 0 (unused)
input 3328 0 [dvb-ttpci evdev keybdev hid]
Hm, so wie ich das seh, ist nvram zwar installiert aber nicht aktiv, oder?
linvdr:~# nvram-wakeup --debug
nvram-wakeup: Printing debug messages enbled.
nvram-wakeup: $Id: nvram-wakeup.h,v 1.26 2003/08/07 17:14:40 bistr-o-math Exp $
nvram-wakeup: $Id: nvram-wakeup-mb.h,v 1.115 2003/03/18 13:44:04 bistr-o-math Exp $
nvram-wakeup: $Id: nvram-wakeup.c,v 1.60 2003/08/06 13:46:32 bistr-o-math Exp $
nvram-wakeup: Opening /dev/mem in O_RDONLY mode...
nvram-wakeup: _DMI_ table found: base: 0xF2CA0, size: 0x44E, count: 38
nvram-wakeup: Following DMI entries found:
nvram-wakeup: - Mainboard vendor: ASUSTeK Computer INC.
nvram-wakeup: - Mainboard type: P4S8L
nvram-wakeup: - Mainboard revision: REV 1.xx
nvram-wakeup: - BIOS vendor: Award Software, Inc.
nvram-wakeup: - BIOS version: ASUS P4S8L ACPI BIOS Revision 1005
nvram-wakeup: - BIOS release: 06/11/2003
nvram-wakeup: Using following bios info:
nvram-wakeup: need_reboot = 0
nvram-wakeup: addr_chk_h = 0x6B
nvram-wakeup: addr_chk_l = 0x6C
nvram-wakeup: addr_chk_h2 = 0x00
nvram-wakeup: addr_chk_l2 = 0x00
nvram-wakeup: addr_stat = 0x49
nvram-wakeup: addr_mon = 0x00
nvram-wakeup: addr_date = 0x49
nvram-wakeup: addr_wdays = 0x00
nvram-wakeup: addr_hour = 0x00
nvram-wakeup: addr_min = 0x00
nvram-wakeup: addr_sec = 0x00
nvram-wakeup: shift_stat = 1
nvram-wakeup: shift_mon = 0
nvram-wakeup: shift_date = 2
nvram-wakeup: shift_wdays = 0
nvram-wakeup: shift_hour = 0
nvram-wakeup: shift_min = 0
nvram-wakeup: shift_sec = 0
nvram-wakeup: rtc_time = 1
nvram-wakeup: rtc_date = 0x00
nvram-wakeup: rtc_mon = 0x00
nvram-wakeup: rtc_date_0_is_c0 = 0
nvram-wakeup: rtc_mon_0_is_c0 = 0
nvram-wakeup: reset_date = 0
nvram-wakeup: reset_mon = 0
nvram-wakeup: nr_stat = 1
nvram-wakeup: nr_mon = 4
nvram-wakeup: nr_date = 5
nvram-wakeup: nr_hour = 5
nvram-wakeup: nr_min = 6
nvram-wakeup: nr_sec = 6
nvram-wakeup: nr_rtc_date = 6
nvram-wakeup: nr_rtc_mon = 5
nvram-wakeup: nr_wdays = 7
nvram-wakeup: bcd = 0
nvram-wakeup: date_no_chk = 0
nvram-wakeup: date_hack = 0
nvram-wakeup: Opening /dev/rtc in O_RDONLY mode...
nvram-wakeup: Hardware clock: 2004-02-28 16:21:42
nvram-wakeup: rtc.tm_isdst : 0
nvram-wakeup: rtc.tm_gmtoff: 3600
nvram-wakeup: diff : -1
nvram-wakeup: RTC is running in localtime!
nvram-wakeup: Test (this should be the current time of the hardware clock): Sat Feb 28 16:21:41 2004
nvram-wakeup: Opening /dev/nvram in O_RDONLY mode...
nvram-wakeup: The size of /dev/nvram is 114 bytes.
nvram-wakeup: value of the addr_stat byte is: 0xEE.
nvram-wakeup: value of the addr_date byte is: 0xEE.
nvram-wakeup: value of the addr_chk_h byte is: 0x09.
nvram-wakeup: value of the addr_chk_l byte is: 0x14.
nvram-wakeup: Opening /dev/rtc in O_RDONLY mode...
nvram-wakeup: Checksum is: 0x0914.
All values are displayed as they are stored in the nvram/rtc.
(and do not correspond necessarily to the system date/time)
WakeUp : Enabled (0xEE)
Date : 27 (0xEE)
rtcHour : 21
rtcMin : 26
rtcSec : 38
Checksum: 0x0914
Und logread sagt:
linvdr:~# logread
Feb 28 16:19:12 linvdr syslog.info syslogd started: BusyBox v1.00-pre4 (2003.12.16-16:00+0000)
Feb 28 16:19:13 linvdr local0.info udhcpc[59]: client (v0.9.9-pre) started
Feb 28 16:19:13 linvdr local0.debug udhcpc[59]: Sending discover...
Feb 28 16:19:15 linvdr local0.debug udhcpc[59]: Sending discover...
Feb 28 16:19:17 linvdr syslog.info klogd: bcm4400: eth0 NIC Link is Up, 100 Mbps full duplex
Feb 28 16:19:17 linvdr local0.debug udhcpc[59]: Sending discover...
Feb 28 16:19:18 linvdr local0.debug udhcpc[59]: Sending select for 192.168.1.101...
Feb 28 16:19:18 linvdr local0.info udhcpc[59]: Lease of 192.168.1.101 obtained, lease time 86400
Feb 28 16:19:18 linvdr auth.info sshd[68]: Server listening on 0.0.0.0 port 22.
Feb 28 16:19:18 linvdr cron.notice crond[77]: crond 2.3.2 dillon, started, log level 8
Feb 28 16:19:19 linvdr daemon.info init: Starting pid 89, console /dev/tty1: '/sbin/getty'
Feb 28 16:19:19 linvdr daemon.info init: Starting pid 90, console /dev/tty2: '/sbin/getty'
Feb 28 16:19:19 linvdr daemon.info init: Starting pid 91, console /dev/tty3: '/sbin/getty'
Feb 28 16:19:19 linvdr daemon.info init: Starting pid 92, console /dev/tty4: '/sbin/getty'
Feb 28 16:19:19 linvdr syslog.info klogd: Linux video capture interface: v1.00
Feb 28 16:19:19 linvdr syslog.warn klogd: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3).
Feb 28 16:19:19 linvdr syslog.warn klogd: DVB: registering frontend 0:0 (Alps BSRV2)...
Feb 28 16:19:22 linvdr syslog.warn klogd: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261b
Feb 28 16:19:22 linvdr syslog.warn klogd: DVB: AV7111(0) - firmware supports CI link layer interface
Feb 28 16:19:22 linvdr syslog.warn klogd: av7110(0): adac type set to 0
Feb 28 16:19:22 linvdr syslog.warn klogd: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 0 has MAC addr = 00:d0:5c:5b:ad:ca
Feb 28 16:19:22 linvdr syslog.err klogd: lirc_serial: port 03f8 already in use, proceeding anyway
Feb 28 16:19:22 linvdr syslog.warn klogd: lirc_serial: compile the serial port driver as module and
Feb 28 16:19:22 linvdr syslog.warn klogd: lirc_serial: make sure this module is loaded first
Feb 28 16:19:23 linvdr syslog.info klogd: lirc_serial: auto-detected active low receiver
Feb 28 16:19:24 linvdr user.info vdr[122]: VDR version 1.2.6 started
Feb 28 16:19:24 linvdr user.info vdr[122]: loading plugin: /usr/lib/vdr/plugins/libvdr-mp3.so.1.2.6
Feb 28 16:19:24 linvdr user.info vdr[122]: loading plugin: /usr/lib/vdr/plugins/libvdr-mplayer.so.1.2.6
Feb 28 16:19:24 linvdr user.info vdr[122]: loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev.so.1.2.6
Feb 28 16:19:24 linvdr user.info vdr[122]: loading plugin: /usr/lib/vdr/plugins/libvdr-vcd.so.1.2.6
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/setup.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/sources.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/diseqc.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/channels.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/commands.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/reccmds.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/svdrphosts.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/ca.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/remote.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/keymacros.conf
Feb 28 16:19:24 linvdr user.debug vdr[122]: probing /dev/dvb/adapter0/frontend0
Feb 28 16:19:24 linvdr user.debug vdr[126]: EIT processing thread started (pid=126) - master
Feb 28 16:19:24 linvdr user.debug vdr[127]: tuner thread started on device 1 (pid=127)
Feb 28 16:19:24 linvdr user.debug vdr[122]: probing /dev/dvb/adapter1/frontend0
Feb 28 16:19:24 linvdr user.info vdr[122]: found 1 video device
Feb 28 16:19:24 linvdr user.info vdr[122]: initializing plugin: mp3 (0.8.2): A versatile audio player
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/plugins/mp3sources.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: initializing plugin: mplayer (0.8.2): A MPlayer calling plugin
Feb 28 16:19:24 linvdr user.info vdr[122]: loading /etc/vdr/plugins/mplayersources.conf
Feb 28 16:19:24 linvdr user.info vdr[122]: initializing plugin: streamdev (0.2.0): VTP Streaming Server and Client
Feb 28 16:19:24 linvdr user.info vdr[122]: initializing plugin: vcd (0.0.6c): VideoCD Player
Feb 28 16:19:24 linvdr user.info vdr[122]: setting primary device to 1
Feb 28 16:19:24 linvdr user.info vdr[122]: SVDRP listening on port 2001
Feb 28 16:19:24 linvdr user.info vdr[122]: starting plugin: mp3
Feb 28 16:19:24 linvdr user.info vdr[122]: starting plugin: mplayer
Feb 28 16:19:24 linvdr user.info vdr[122]: starting plugin: streamdev
Feb 28 16:19:24 linvdr user.info vdr[128]: Streamdev: Server thread started
Feb 28 16:19:24 linvdr user.info vdr[128]: Streamdev: Listening (HTTP) on port 3000
Feb 28 16:19:24 linvdr user.info vdr[122]: starting plugin: vcd
Feb 28 16:19:24 linvdr user.debug vdr[129]: LIRC remote control thread started (pid=129)
Feb 28 16:19:24 linvdr user.debug vdr[130]: KBD remote control thread started (pid=130)
Feb 28 16:19:24 linvdr user.debug vdr[122]: remote control LIRC - keys known
Feb 28 16:19:24 linvdr user.debug vdr[122]: remote control KBD - keys known
Feb 28 16:19:24 linvdr user.info vdr[122]: switching to channel 1
Feb 28 16:19:24 linvdr user.debug vdr[122]: setting watchdog timer to 900 seconds
Feb 28 16:19:30 linvdr user.info vdr[122]: connect from 127.0.0.1, port 32768 - accepted
Feb 28 16:19:30 linvdr user.info vdr[122]: closing SVDRP connection
Feb 28 16:19:31 linvdr user.debug vdr[122]: max. latency time 1 seconds
Feb 28 16:19:57 linvdr auth.info sshd[135]: Could not reverse map address 192.168.1.100.
Feb 28 16:19:59 linvdr auth.info sshd[135]: Accepted password for root from 192.168.1.100 port 1416 ssh2
Feb 28 16:19:59 linvdr auth.info sshd[135]: lastlog_get_entry: Error reading from /var/log/lastlog: Bad file descriptor
Feb 28 16:19:59 linvdr auth.info PAM_unix[135]: (ssh) session opened for user root by (uid=0)
Feb 28 16:19:59 linvdr auth.err PAM-env[135]: Unable to open config file: No such file or directory
Feb 28 16:19:59 linvdr auth.err PAM-env[136]: Unable to open config file: No such file or directory
Feb 28 16:20:01 linvdr cron.notice crond[77]: USER root pid 137 cmd convert.pl -q -s
Schaut das bei dir rell bzw. strgalt auch so aus?
Naja, ich muß jetzt leider mal für ne`Stunde weg, melde mich dann später nochmal,
Danke für eure Hilfe,
Schokko