[vdr] Wakeup On LAN

2007-03-02 Thread Bernd Juraschek
Hello, I'm trying to wakeup my Siemens Scaleo-T using WOL - but without success :-( The PC to wakeup: - Siemens Scaleo-T AMD64 with Onboard LAN (Tulip chip) - Linux 2.6.20 with ACPI enabled - Gentoo amd64 The router: - ASUS WL-500g Deluxe - OpenWrt White Russian - With X-Wrt Extensions RC6 - W

Re: [vdr] Wakeup On LAN

2007-03-02 Thread Bernd Juraschek
> >- BIOS: Wakeup controlled by BIOS and WOL enabled > >- Gentoo: echo -n PCI0 > /proc/acpi/wakeup ; halt > >- Router: wol -h PC-IP-Addr PC-MAC-Addr > > I use etherwake to send wol packet (it sends ethernet packets, not udp > one that doesn't work with my lan card). Now the PC gets pure ethernet

Re: [vdr] Wakeup On LAN

2007-03-02 Thread Bernd Juraschek
> Have you tried disabling "RC_DOWN_INTERFACE" in /etc/conf.d/rc ? Hmm - it was disabled already :-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Wakeup On LAN

2007-03-03 Thread Bernd Juraschek
Hi, > 1) Make sure that your Interface does not get down, when Linux shuts > down. Control this behavior, with the Links on your Switch or maybe there are > also light that must not turn off on your interface. The rc_down_interface is > perfect for this > 2) Have you set wake on lan

Re: [vdr] Wakeup On LAN

2007-03-03 Thread Bernd Juraschek
Hi! > Now I've patched my kernel with suspend2. Now after hibernating to > suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to > the poweroff mode disables WOL again. Is WOL never possible if the > PC is soft powered off? After powering off the PC per long-pressing the power button

Re: [vdr] Wakeup On LAN

2007-03-04 Thread Bernd Juraschek
Hi, it seems to be a problem with the Siemens D1605 board. WOL isn't working for ACPI S3 sleep mode. After Changing to S4 all is fine. But - I think yesterday it was working with S3 also. I will try it again after all recordings are done ... Greetings, Bernd

Re: [vdr] Wakeup On LAN

2007-03-04 Thread Bernd Juraschek
Hi, > Regarding waking up at a certain time: > Go to the wiki in read carefully about nvram-wakeup. This damn Siemens D1605 board is not supported by nvram-wakeup. First Siemens has some own checksum calculation and second guess-helper isn't able to guess the CMOS addresses for the alarm clock.

[vdr] How to identify timers

2007-08-22 Thread Bernd Juraschek
Hello list, I want to do some kind of offline modifying vdr timers, but I don't know how to identify timers. If I use the timer id to change or delete VDR timers, then this will go wrong if VDR has deleted some timers since the remote site has retrieved the timer list. Using timer properties is n

Re: [vdr] Problem with audio sync in playback - maybe caused by ntpd stepping local clock?

2006-10-17 Thread Bernd Juraschek
On Tue, Oct 17, 2006 at 12:51:33AM +0200, martin wrote: > Not sure, if this may relate to your problem, but .. > > I use xine plugin and every once in a while I had a short interruption of > sound. Today I was tail-ing -f syslog for another reason and there was this > little glitch again! Just a v

[vdr] VDR and system time setting

2006-10-17 Thread Bernd Juraschek
Hello, I've configured VDR to set the system time. But it's not possible to change the channel to use. I can switch the setting to another channel and vdr is saving setup.conf. But if I reenter the settings, I see the old channel again. The channel displayed on OSD is 126, but setup.conf contains

[vdr] Capabilities

2007-02-18 Thread Bernd Juraschek
Hello, I've problems with my statusleds plugin. If vdr is not running as root all capabilities are dropped - except the one for setting the system time. My plugin wants to set the keyboard leds with the ioctl KDSETLED on /dev/console. Unfortunately this ioctl requires one more capability. Is the

Re: [vdr] Capabilities

2007-02-18 Thread Bernd Juraschek
> Why not simply document this fact in the installation guide: > "The plugin must have write access to /dev/console." > This is similar to the dvd or vcd plugin which need read/write access to > /dev/dvd resp. /dev/cdrom. Hmm - this sounds like a good idea ... > On my machine, I added the vdr use