vdr June 2006

vdr@linuxtv.org

109 participants
101 discussions

Shutdown - vdr not cleaning up
by Tobias Grimm 11 Jun '06

11 Jun '06

Hi! Hanno Mueller figured out a problem with the VDR Debian package, causing the ALCD plugin to not turn off the display, when the system shuts down. The first obvious problem seemed to be, that the shutdown command passed to vdr did not return immediately. So I changed this to be started detached in the background. But there seems to be still a problem around. If I send SIGTERM to the vdr process manually, everything works fine. It cleans up, stops and destroys all plugins. But if I run "shutdown -h now" (which also sends SIGTERM to vdr and all other processes), the plugins destructors never get called. I've added a log message to every line in the exit code and you can see what I got at the end of this mail. To be sure, vdr doesn't get killed, because it takes too long to shut down gracefully, I also tried "telinit -t 120 0" which switches to runlevel 0 but gives processes 120 seconds to shutdown before sending SIGKILL. Same result - VDR does not fully clean up on exit. Unfortunately, the problem only appears, when switching to runlevel 0. Everything I tried to shutdown VDR without shutting down the whole system seems to work just fine. So there seems to be no way to inspect this in a debugger. Any ideas, why vdr doesn't shut down gracefully, when shutting down the system? Regards, Tobias Only vdr killed manually with killall vdr (I've added ctor/dtor messages to the podcatcher plugin, the messages after cSchedule::Cleanup(true) are skipped). This is how it is supposed to work. 12:26:12 vdr: [5642] ecmhandler 0 filter thread ended (pid=5642, tid=5642) 12:26:13 vdr: [5346] caught signal 15 12:26:13 vdr: [5346] PluginManager.StopPlugins() 12:26:13 vdr: [5346] stopping plugin: dvd 12:26:13 vdr: [5346] stopping plugin: trayopen 12:26:13 vdr: [5346] stopping plugin: podcatcher 12:26:13 vdr: [5346] stop() start 12:26:14 vdr: [5346] stop() end 12:26:14 vdr: [5346] stopping plugin: mp3 12:26:14 vdr: [5346] stopping plugin: radio 12:26:15 vdr: [5346] ERROR: radiocheck thread 5637 won't end (waited 1 seconds) - canceling it... 12:26:15 vdr: [5346] stopping plugin: dvdselect 12:26:15 vdr: [5644] logger 0 filter thread ended (pid=5644, tid=5644) 12:26:15 vdr: [5643] logger stats thread ended (pid=5643, tid=5643) 12:26:15 vdr: [5346] stopping plugin: burn 12:26:15 vdr: [5346] stopping plugin: extrecmenu 12:26:15 vdr: [5346] stopping plugin: skinsoppalusikka 12:26:15 vdr: [5346] cRecordControls::Shutdown() 12:26:15 vdr: [5346] cCutter::Stop() 12:26:15 vdr: [5346] delete Menu 12:26:15 vdr: [5346] cControl::Shutdown() 12:26:15 vdr: [5346] delete Interface 12:26:15 vdr: [5346] cOsdProvider::Shutdown() 12:26:15 vdr: [5346] Remotes.Clear() 12:26:15 lircd 0.7.1pre2[5160]: removed client 12:26:15 vdr: [5641] KBD remote control thread ended (pid=5641, tid=5641) 12:26:15 vdr: [5346] Audios.Clear() 12:26:15 vdr: [5346] delete RadioAudio 12:26:15 vdr: [5346] Skins.Clear() 12:26:15 vdr: [5346] Setup.CurrentChannel = cDevice::CurrentChannel() 12:26:15 vdr: [5346] Setup.CurrentVolume = cDevice::CurrentVolume() 12:26:15 vdr: [5346] Setup.Save() 12:26:15 vdr: [5346] saved setup to /var/lib/vdr/setup.conf 12:26:15 vdr: [5346] cDevice::Shutdown() 12:26:15 vdr: [5625] tuner on device 1 thread ended (pid=5625, tid=5625) 12:26:15 vdr: [5626] section handler thread ended (pid=5626, tid=5626) 12:26:15 vdr: [5628] tuner on device 2 thread ended (pid=5628, tid=5628) 12:26:15 vdr: [5629] section handler thread ended (pid=5629, tid=5629) 12:26:15 vdr: [5346] PluginManager.Shutdown(true) 12:26:15 vdr: [5346] deleting plugin: dvd 12:26:15 vdr: [5346] deleting plugin: trayopen 12:26:15 vdr: [5639] CDROM watch thread ended 12:26:15 vdr: [5639] cd drive watch thread thread ended (pid=5639, tid=5639) 12:26:15 vdr: [5346] deleting plugin: podcatcher 12:26:15 vdr: [5346] dtor() start 12:26:16 vdr: [5346] dtor() end 12:26:16 vdr: [5346] deleting plugin: mp3 12:26:16 vdr: [5346] deleting plugin: radio 12:26:16 vdr: [5346] deleting plugin: dvdselect 12:26:16 vdr: [5346] ln -nfs '/dev/dvd' '/var/cache/vdr/dvd' 2> /dev/null 12:26:16 vdr: [5346] deleting plugin: burn 12:26:16 vdr: [5346] deleting plugin: extrecmenu 12:26:16 vdr: [5346] deleting plugin: skinsoppalusikka 12:26:16 vdr: [5346] cSchedules::Cleanup(true) ... And this is what happens, when I shutdown the system with "shutdown -h now" from a console (not from within vdr): 12:36:04 shutdown[5654]: shutting down for system halt 12:36:05 init: Switching to runlevel: 0 12:36:10 lircd 0.7.1pre2[5164]: caught signal 12:36:10 vdr: [5570] ERROR: lircd connection broken, trying to reconnect every 3.0 seconds 12:36:10 mysqld[5092]: 060604 12:36:10 [Note] /usr/sbin/mysqld: Normal shutdown 12:36:10 mysqld[5092]: 12:36:10 mysqld[5092]: 060604 12:36:10 InnoDB: Starting shutdown... 12:36:12 mysqld[5092]: 060604 12:36:12 InnoDB: Shutdown completed; log sequence number 0 48986 12:36:12 mysqld[5092]: 060604 12:36:12 [Note] /usr/sbin/mysqld: Shutdown complete 12:36:12 mysqld[5092]: 12:36:12 mysqld_safe[5840]: ended 12:36:13 vdr: [5570] ERROR: /dev/lircd: Connection refused 12:36:13 lircd 0.7.1pre2[5874]: lircd(any) ready 12:36:16 vdr: [5570] reconnected to lircd 12:36:16 lircd 0.7.1pre2[5874]: accepted new client on /dev/lircd 12:36:16 vdr: [5572] ecmhandler 0 filter thread ended (pid=5572, tid=5572) 12:36:16 vdr: [5574] logger 0 filter thread ended (pid=5574, tid=5574) 12:36:17 vdr: [5383] caught signal 15 12:36:17 vdr: [5383] PluginManager.StopPlugins() 12:36:17 vdr: [5383] stopping plugin: dvd 12:36:17 vdr: [5383] stopping plugin: trayopen 12:36:17 vdr: [5383] stopping plugin: podcatcher 12:36:17 vdr: [5383] stop() start 12:36:18 vdr: [5383] stop() end 12:36:18 vdr: [5383] stopping plugin: mp3 12:36:18 vdr: [5383] stopping plugin: radio 12:36:19 vdr: [5383] ERROR: radiocheck thread 5554 won't end (waited 1 seconds) - canceling it... 12:36:19 vdr: [5383] stopping plugin: dvdselect 12:36:19 vdr: [5573] logger stats thread ended (pid=5573, tid=5573) 12:36:19 vdr: [5383] stopping plugin: burn 12:36:19 vdr: [5383] stopping plugin: extrecmenu 12:36:19 vdr: [5383] stopping plugin: skinsoppalusikka 12:36:19 vdr: [5383] cRecordControls::Shutdown() 12:36:19 vdr: [5383] cCutter::Stop() 12:36:19 vdr: [5383] delete Menu 12:36:19 vdr: [5383] cControl::Shutdown() 12:36:19 vdr: [5383] delete Interface 12:36:19 vdr: [5383] cOsdProvider::Shutdown() 12:36:19 vdr: [5383] Remotes.Clear() 12:36:19 lircd 0.7.1pre2[5874]: removed client 12:36:21 ntpd[5509]: ntpd exiting on signal 15 12:36:21 exiting on signal 15

2 2

Re: [vdr] xine-network patches
by CR 10 Jun '06

10 Jun '06

Anssi, > Anssi Hannula <anssi.hannula(a)gmail.com> writes: > > > Hi! > > > > Those who run vdr-xine with the network patches, what is the version of > > your libxine and which patches do you use for libxine and vdr-xine? You might want to try "xineliboutput" -- it's a plugin that includes network functionality WITHOUT having to apply any patches to xine/xinelib/xineui! You add any clients that need access to the svdrphosts.conf file . The package includes standalone front-end programs, so you don't have to use Xine-UI if you don't want to (make frontends on the frontend machine). You'll probably have to re-compile xinelib without any patches, but that shouldn't be a big deal. Here's the latest version: http://users.tkk.fi/~phintuka/vdr/vdr-xineliboutput/vdr-xineliboutput-0.99r… It should work on AMD64, though I only have a 32-bit machine. Regards, C.

4 4

upgraded to vdr 1.4.0-1, empty recording list
by Torgeir Veimo 10 Jun '06

10 Jun '06

How to rectify this problem? I upgraded from vdr-1.3.24, and now my recording list is empty after restart. If I start new recordings, they appear in the list, but are gone after a restart. They're still on the harddrive though. -- Torgeir Veimo <torgeir(a)pobox.com>

2 4

HD output from VDR
by Mikolaj Tutak 08 Jun '06

08 Jun '06

Hi! My goal is to setup VDR+Skystar2 DVB-S card to output signal on Radeon AGP card on DVI connector (for HDMI TV input). Desired resolution is 1366x768 or 720p. I found siutable vdr-xine and vdr-sotdevice plugins. Which one is better for HD output? Probabbly softdevice is simpler and less complicated. Which mode has best quality and performance - X11-XV, DirectFB, vidix? Maybe some one has reached similar goal and want to share his experience? -- regards Mikolaj Tutak

3 2

vdradmin-am division by zero
by Patrick Maier 08 Jun '06

08 Jun '06

Hi, I found a bug in vdradmin-am 3.4.6beta2 that always crashed my vdradmin.pl. In the "prog_summary" section, there is a calculation of how much percent of the event is already passed. But when the start-time and the end-time of that event are the same than the following code will result in an "Division by Zero": Line 3989 of vdradmin.pl: percent => int(($now - $event->{start})/($event->{stop} - $event->{start})*100), This should be checked like this: percent => ($event->{stop} - $event->{start} > 0) ? (int(($now - $event->{start})/($event->{stop} - $event->{start})*100)) : 0, here is a patch: ============= patch begin ============== @@ -3986,7 +3986,7 @@ stop => my_strftime("%H:%M", $event->{stop}), event_start => $event->{start}, show_percent => $event->{start} <= $now && $now <= $event->{stop} ? "1" : undef, - percent => int(($now - $event->{start}) / ($event->{stop} - $event->{start}) * 100), + percent => ($event->{stop} - $event->{start} > 0) ? (int(($now - $event->{start}) / ($event->{stop} - $event->{start}) * 100)) : 0, elapsed_min => int(($now - $event->{start}) / 60), length_min => int(($event->{stop} - $event->{start}) / 60), title => $displaytitle, ============= patch end ============== Greets Patrick -- There are only 10 kind of people who understand binary digits: Those who do - Those who don't...

1 0

Hispasat and PowerVu
by Marco Goebenich 08 Jun '06

08 Jun '06

Hi! I'd like to recieve some stations from Hispasat, they are encrypted with PowerVu. Does anybody know a PowerVu CAM, usable with vdr? Regards Marco -- vierzehn Bahnhofstr. 27 Telefon 0 26 32 / 98 98 - 120 public relations 56626 Andernach Telefax 0 26 32 / 98 98 - 111 GmbH & Co. KG E-Mail: mg(a)vierzehn.com

1 0

AW: Re: [vdr] GRAB image failed
by dominik＠die-strassers.de 07 Jun '06

07 Jun '06

>Ok this explains why my GRAB broked few months ago when updated v4l-dvb >driver. > >Does the vdrportal article have any solutions? I don't speak german so it's >pretty useless for me. Antti, basically it says that it works with the latest drivers from HG. Regards Dominik (who set this off telling the author of jvdr that it didn't work any more) > > >On Wed, Jun 07, 2006 at 05:40:47PM +0200, Juergen Judt wrote: >> I have the same problems with the DVB HG driver from ~May, with the actual >driver it works now! >> >> See some posts on the VDR portal >> http://www.vdr-portal.de/board/thread.php?postid=470654#post470654 >> >> Bye, >> Juergen >> >> >> On Mi, Juni 7, 2006 14:17, Peter Juszack wrote: >> > Hi list, >> > >> > >> > I wonder if the svdrp GRAB command does not work any more. I >> > realized that my remote GUI JVdr >> > is not able to get an image any more after upgrading to 1.4.0 >> > >> > I connected manually via >> > >> > peter@fontina:~ telnet localhost 2001 >> > ... >> > GRAB - >> > 451 Grab image failed >> > GRAB test.jpg >> > 550 Grabbing to file not allowed (use "GRAB -" instead) >> > QUIT >> > >> > I restartet vdr with a valid -g option but: >> > >> > peter@fontina:~ telnet localhost 2001 >> > ... >> > GRAB - >> > 451 Grab image failed >> > GRAB test.jpg >> > 451 Grab image failed >> > QUIT >> > >> > >> > I studied http://www.cadsoft.de/vdr/changelog.htm but could not find any >> > hints. >> > >> > No other problems. >> > >> > Thanks for help >> > >> > Peter >> > >> > >> > _______________________________________________ >> > vdr mailing list >> > vdr(a)linuxtv.org >> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> > >> >> >> >> _______________________________________________ >> vdr mailing list >> vdr(a)linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > >_______________________________________________ >vdr mailing list >vdr(a)linuxtv.org >http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

1 0

GRAB image failed
by Peter Juszack 07 Jun '06

07 Jun '06

Hi list, I wonder if the svdrp GRAB command does not work any more. I realized that my remote GUI JVdr is not able to get an image any more after upgrading to 1.4.0 I connected manually via peter@fontina:~ telnet localhost 2001 ... GRAB - 451 Grab image failed GRAB test.jpg 550 Grabbing to file not allowed (use "GRAB -" instead) QUIT I restartet vdr with a valid -g option but: peter@fontina:~ telnet localhost 2001 ... GRAB - 451 Grab image failed GRAB test.jpg 451 Grab image failed QUIT I studied http://www.cadsoft.de/vdr/changelog.htm but could not find any hints. No other problems. Thanks for help Peter

3 5

lirc improvement suggestion
by Joerg Riechardt 06 Jun '06

06 Jun '06

I used to use the usbremote plugin, now I switched to lirc, because I wanted to play with irexec. Since then vdr didn´t react to my remote control as I was used to any more. I had sometimes double reactions on one keypress as other people have described and the speed of the reactions was weird. After investigating I found following solution, which makes me 100% happy. Maybe other people like it too? Btw. the count´s provided by lirc are not reliably incoming to the lirc part of vdr, meaning if I press a key for a long time instead of going up continously, they start from time to time at zero, sometimes even all are zero. That is not catched by this patch. Some more background information: I compared the remote plugin for the FF cards with the usbremote plugin for the igorplug (which was taken from the remote plugin) and the lirc part of vdr. My remote (OFA URC 7541) with RC5 codes on each key toogles the RC5 code on each key press. (I suppose all RC5 remotes do(?)). The firmware of the driver for the FF cards changes that to key down/key up (AFAIR). The usbremote plugin receives the codes as they are sent. Lirc changes the toogled codes into counts starting from zero. With the igorplug the counts sometimes start at zero again, with a serial receiver it does always count up. The lirc part of vdr however has a problem here. I observed that sometimes all counts are zero with the igorplug, with the serial driver this is much better, but happens sometimes as well.The remote plugin and the usbremote plugin work very well, the lirc-vdr didn´t for me. I don´t know how the RCU processes the RC5 code, and hence don´t understand the rcu code. The rcu code was taken for lirc in vdr (some adaptations were made in time). I put a lot of printf´s to see how the code logic operates and what actually happens on key presses. The improved code, which is basically just taken from the remote plugin, works perfectly for me. Jörg --- lirc.c.orig.c 2006-01-27 16:59:47.000000000 +0100 +++ lirc.c.new.c 2006-05-26 22:40:26.000000000 +0200 @@ -13,9 +13,9 @@ #include <netinet/in.h> #include <sys/socket.h> -#define REPEATLIMIT 20 // ms #define REPEATDELAY 350 // ms -#define KEYPRESSDELAY 150 // ms +#define REPEATFREQ 100 // ms +#define REPEATTIMEOUT 500 // ms #define RECONNECTDELAY 3000 // ms cLircRemote::cLircRemote(const char *DeviceName) @@ -94,8 +94,8 @@ continue; } if (count == 0) { - if (strcmp(KeyName, LastKeyName) == 0 && FirstTime.Elapsed() < KEYPRESSDELAY) + if (strcmp(KeyName, LastKeyName) == 0 && FirstTime.Elapsed() < REPEATDELAY) continue; // skip keys coming in too fast if (repeat) Put(LastKeyName, false, true); strcpy(LastKeyName, KeyName); @@ -104,8 +104,10 @@ timeout = -1; } else { - if (FirstTime.Elapsed() < REPEATDELAY) - continue; // repeat function kicks in after a short delay + if (LastTime.Elapsed() < REPEATFREQ) + continue; // repeat function kicks in after a short delay (after last key instead of first key) + if (FirstTime.Elapsed() < REPEATDELAY) + continue; // skip keys coming in too fast (for count != 0 as well) repeat = true; timeout = REPEATDELAY; } @@ -113,7 +115,7 @@ Put(KeyName, repeat); } else if (repeat) { // the last one was a repeat, so let's generate a release - if (LastTime.Elapsed() >= REPEATDELAY) { + if (LastTime.Elapsed() >= REPEATTIMEOUT) { Put(LastKeyName, false, true); repeat = false; *LastKeyName = 0;

3 5

Too many open files?
by Gavin Hamill 06 Jun '06

06 Jun '06

Hi - I am trying a vanilla 1.3.37 (same issue with 1.4.0) with a USB DVB-T stick (a Freecom-branded Wideview 220 clone) which works perfectly with vlc, dvbstream, Kaffeine, etc. If I run vdr, and then just try to record the current channel, I get this: Jun 5 13:48:59 telly vdr: [11315] switching device 1 to channel 21 Jun 5 13:48:59 telly vdr: [11315] ERROR: can't open filter handle on '/dev/dvb/adapter0/demux0' Jun 5 13:48:59 telly vdr: [11315] timer 1 (21 1348-1648 '@TITLE EPISODE') start Jun 5 13:48:59 telly vdr: [11315] Title: 'BBC News' Subtitle: '(null)' Jun 5 13:48:59 telly vdr: [11315] record /video/(a)BBC_News/2006-06-05.13.48.50.99.rec Jun 5 13:48:59 telly vdr: [11315] creating directory /video/(a)BBC_News/2006-06-05.13.48.50.99.rec Jun 5 13:48:59 telly vdr: [11315] recording to '/video/(a)BBC_News/2006-06-05.13.48.50.99.rec/001.vdr' Jun 5 13:48:59 telly vdr: [11315] ERROR: /dev/dvb/adapter0/demux0: Too many open files Jun 5 13:48:59 telly vdr: [11315] ERROR (dvbdevice.c,673): Too many open files Jun 5 13:48:59 telly vdr: [11315] ERROR: can't set PID 640 on device 1 Jun 5 13:48:59 telly vdr: [11315] ERROR (dvbdevice.c,688): Bad file descriptor Jun 5 13:48:59 telly vdr: [11315] buffer stats: 0 (0%) used It would suggest that the number of PID filters on the device has been exceeded, but I know that there are 15 available, and VDR is only using nine: root@telly:~# lsof -n | grep adapter0.demux0 -c 9 BBC News 24 has a channels.conf entry of 754166670:C34D34M16B8T2G32Y0:T:0:640:641=eng:0:0:4415:9018:4104:0 so it's only using two PIDs. I have verified that the device truly does have 15 PID filters available thusly: dvbstream -f 754167 100 17 600 601 610 611 612 613 640 641 650 651 652 1013 1021 -i 127.0.0.1 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Setting filter for PID 100 Setting filter for PID 17 Setting filter for PID 600 Setting filter for PID 601 Setting filter for PID 610 Setting filter for PID 611 Setting filter for PID 612 Setting filter for PID 613 Setting filter for PID 640 Setting filter for PID 641 Setting filter for PID 650 Setting filter for PID 651 Setting filter for PID 652 Setting filter for PID 1013 Setting filter for PID 1021 Using 127.0.0.1:5004:2 version=2 Streaming 15 streams and adding another PID to the list gives: FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC FD 15: DEMUX DEVICE: : Too many open files Can anyone suggest why VDR might be receiving this error? Cheers, Gavin.

2 2

← Newer
1
...
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2006