[vdr] Wakeup On LAN
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 - WOL-Software: wol What I've done: - 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've configured the router to start wol periodically. On the PC wireshark is now showing incoming UDP packets to the UDP port 4. The packet contains the ethernet frame, the IP header, the UDP header and the magic data (6x 0xff and 16x MAC-Addr). It seems all ok - but the PC will not be started. What's going wrong? Should I use some ACPI sleep mode? Is this supported by the DVB drivers? Is the Siemens PC not usable for WOL? Thanks for help, Bernd -- Obwohl das Weltall expandiert, findet man nirgendwo Parkplätze. -- BR Space night ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
> >- 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 frames containing the magic packet. But nothing happens ... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
> 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
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 with ethtools? -> I do it every boot: > /usr/sbin/ethtool -s eth0 wol g Ethtool currently doesn't support the tulip on board LAN. But the BIOS should enable WOL. echo -n PCI0 > /proc/acpi/wakeup reenables PCI wakeup, which is required for WOL. And the interface is confugured to not going down on shutdown. > 3) The magic packet must be sent to the broadcast address, since ARP > requests do not work! -> my /sbin/wol-htpc script > > wol --ipaddr=192.168.0.255 00:13:d4:1e:94:73 Now I'm using etherwake and the packets are right. 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? Another problem: I would like to use alarm ACPI wakeup for booting the PC before the next recording starts. I've not tried this with hibernate, but with poweroff this also doesn't work. Is this the same problem? Some strange effect is also: --- # echo "2007-03-03 12:00:00" > /proc/acpi/alarm # cat /proc/acpi/alarm 2007-03-00 12:00:00 # --- Thanks for another idea, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
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 WOL works perfectly. The normal shutdown seems to disable wakeup :-( Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
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. Thinking about using ACPI wakeup, cat /proc/acpi/alarm tells me "2007-03-00 19:03:00" with 00 for the day - regardless of the value written into. But - I've not tested this with S4 mode. Alarm wakeup is not urgent for me because I use my router to wakeup the PC the right time. The PC safes the time into the router before it hibernats. The router uses this time to wakeup the PC per WOL. Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to identify timers
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 not a solution because the user can change timers also locally using OSD. Is there another way to distinguish timers (or channels, recordings, ...)? I think it would be useful to assign some UUID to VDR objects. This ID must not be changed while modifying the object. Is there any chance to insert somewhat like this in future VDR versions - specially without breaking current plugins and applications using the SVDRP interface? Greetings, Bernd -- !!! Reality corrupted !!! Reboot Universe? [Y/n] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with audio sync in playback - maybe caused by ntpd stepping local clock?
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 very short interruption with no sound. I spent > several weekends to find out, why xine always tells me, that "fixing sound > card drift". I was p***ed by my hardware, but now I found out, what cause > the problem. It's my ntpd, that steps the clock on my VDR hardware. To fix > this, I now start ntpd with the "-x" option. > > For Reference from man ntpd: > -x Ordinarily, if the time is to be adjusted more than 128 ms, it > is stepped, not gradually slewed. This option forces the > time > to be slewed in all cases. Hmm - I've configured VDR to adjust the system time. Possibly this is causing the same problem. Should VDR doing the same as "ntpd -x"? Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR and system time setting
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 "TimeTransponder = 113". What's going on? Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Capabilities
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 there any way to get this capability? Should we extend the plugin interface with a possibility for the plugins to specify needed caps? Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Capabilities
> 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 user to the cdrom group. For > /dev/console, this might be a bit trickier: I would have to add vdr to > group tty AND give /dev/console rw-permissions for the group, but that > should suffice. > > I don't know much about linux capabilities, but my feeling is, that they > are meant for things not represented by devices (which use the simpler > file-permissions model). On my system /dev/console has r/w access for anyone but this is not sufficient. I take a look into the kernel sources and there a two ways to get the right to modify terminals with ioctl(): - the modified terminal is the controlling terminal for the process or - the user has the capability to modify terminal settings What can we do now? Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
