vdr January 2006

vdr@linuxtv.org

153 participants
203 discussions

Re: [Klaus Schmidinger] [vdr] Process id in syslog
by Klaus Schmidinger 09 Jan '06

09 Jan '06

Francois-Xavier KOWALSKI wrote: > Hello Klaus, > > find below a tip upon Dominique's request. > >> Subject: >> [vdr] Process id in syslog >> From: >> Klaus Schmidinger <Klaus.Schmidinger(a)cadsoft.de> >> Date: >> Sat, 31 Dec 2005 15:12:24 +0100 >> To: >> vdr(a)linuxtv.org >> >> To: >> vdr(a)linuxtv.org >> >> >> Before the conversion to NPTL, the syslog entries showed >> the pid of each individual thread, so that it was easy to >> tell which thread had issued a particular message. >> >> Now, with NPTL, all VDR syslog entries have the same pid, >> which is that of the foreground thread. This is pretty >> useless, because in case of a problem it's important >> to know exactly which thread has issued which message. >> >> Since I couldn't find any information on this, maybe somebody >> here knows how openlog() needs to be called in order to have >> the individual thread pids displayed in syslog messages on >> an NPTL system. >> >> > Whatever pthread implementation is in use, the symlink /proc/self always > refers to the LWPID (Light-Weight Process ID, i.e. thread PID in your > case). I suggest -- this is what I do -- to stat(2) /proc/self refered > file & sscanf(3) it. Of course, this is better to be done & stored (e.g. > in TLS) at the thread startup & then re-used upon need. Well, this isn't exactly what I meant. I do have the right pids in my program. What I want is that a call like openlog("vdr", LOG_PID | LOG_CONS, LOG_USER); followed by syslog(LOG_INFO, "some log message"); writes to the log file Jan 7 12:25:52 video vdr[7457]: some log message where [7457] should be the pid of the actual thread, not that of the main thread. For instance, on a non-NPTL system, the log looks like this: Dec 10 14:38:51 video vdr[709]: VDR version 1.3.38 started Dec 10 14:38:51 video vdr[709]: loading /video/setup.conf ... Dec 10 14:38:51 video vdr[711]: video directory scanner thread started (pid=711, tid=711) while on an NPTL system I get: Jan 7 12:25:51 video vdr[7457]: VDR version 1.3.38 started Jan 7 12:25:51 video vdr[7457]: loading /video/setup.conf ... Jan 7 12:25:52 video vdr[7457]: video directory scanner thread started (pid=7457, tid=7459) As you can see, in the first case there is vdr[709] for the main thread and vdr[711] for the second thread. In the second case there is vdr[7457] for both threads, while I would like the second thread to show vdr[7459]. Here's a manually created example of how this should look: Jan 7 12:25:51 video vdr[7457]: VDR version 1.3.38 started Jan 7 12:25:51 video vdr[7457]: loading /video/setup.conf ... Jan 7 12:25:52 video vdr[7459]: video directory scanner thread started (pid=7457, tid=7459) Klaus

3 3

Intuix DVB-T stick
by tony 09 Jan '06

09 Jan '06

Hi, I found this on sale and wondered if anyone was using it successfully with VDR? TIA Tony -- Tony Grant www.tgds.net - vente d'ordinateurs mini-itx, hébergement: www.3continents.com - international film festival | www.chez-reine.com - gîte en Bretagne | www.haut-planty.com - Muscadet wine | www.loire-estuaire.org - GIP Loire Estuaire

2 2

rid and channels that have incorrect data
by Malcolm Caldwell 09 Jan '06

09 Jan '06

Hello, A few of the channels I can receive broadcast incorrect data. (Eg satellite data where nid is not unique across the whole satellite. I also have a terrestrial channel that does not broadcast the correct frequency). What I do in this situation is use rid. There is one problem: Even with rid!=0, the channel will still be updated by vdr. So, to fix the channel I have to have two versions. The first with rid=0 which vdr updates and installs the incorrect data. The second has rid=1 which vdr leaves alone. Now: given that rid!=0 will never be set by a scan, I think it would be better if vdr just left all rid!=0 channels alone. This way rid could indicate "don't auto update". This behaviour would not affect the other use of rid. Now, I know some people are going to say "get the broadcasters to fix it"..., but I don't think that is a reason not to make this change.

2 2

enAIO for 1.3.38
by hgm.bg 09 Jan '06

09 Jan '06

Hi Rolf, Usually you have your patch a few hours after the release of a new VDR ready :) Thanks for that. Today i can only find your ttxtsubs and other patches for 1.3.38. The version 2.8 of 1.3.37 gives me to much rejects. Any ETA ? Thanks anyway for your work.... /hgm.bg

2 2

Problems with VDR - no DVB device found
by Chris Miles 09 Jan '06

09 Jan '06

The card is installed and working as I can scan with the scanning utiliy provided with dvb-apps (downloaded and compiled from linuxtv CVS) Running vdr gives the following error within /var/log/messages Jan 9 00:16:23 localhost vdr[4771]: VDR version 1.2.6 started Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/sources.conf Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/diseqc.conf Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/channels.conf Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/svdrphosts.conf Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/ca.conf Jan 9 00:16:23 localhost vdr[4771]: loading /var/lib/vdr/keymacros.conf Jan 9 00:16:23 localhost vdr[4771]: no DVB device found lsmod output blackhole:~# lsmod | grep dvb/* dvb_ttpci 92060 0 l64781 7236 1 dvb_ttpci saa7146_vv 47168 1 dvb_ttpci saa7146 17992 2 dvb_ttpci,saa7146_vv ves1820 6340 1 dvb_ttpci stv0299 10408 1 dvb_ttpci dvb_core 81544 2 dvb_ttpci,stv0299 tda8083 5892 1 dvb_ttpci stv0297 7680 1 dvb_ttpci sp8870 7372 1 dvb_ttpci firmware_class 10816 2 dvb_ttpci,sp8870 ves1x93 6564 1 dvb_ttpci ttpci_eeprom 2720 1 dvb_ttpci i2c_core 21904 12 i2c_viapro,via686a,i2c_isa,dvb_ttpci,l64781,ves1820,stv0299,tda8083,stv0297,sp88 70,ves1x93,ttpci_eeprom dmesg output blackhole:~# dmesg | grep dvb saa7146: register extension 'dvb'. dvb-ttpci: gpioirq unknown type=0 len=0 dvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app 80002622 dvb-ttpci: firmware @ card 0 supports CI link layer interface dvb-ttpci: adac type set to 0 @ card 0 dvb-ttpci: found av7110-0. I have the firmware file in location... blackhole:~# ls -l /usr/lib/hotplug/firmware/ total 240 -rw-r--r-- 1 root root 239956 2006-01-08 22:52 dvb-ttpci-01.fw The contents of /dev/dvb are as follows. blackhole:~# ls -lR /dev/dvb /dev/dvb: total 0 drwxr-xr-x 2 root root 200 2006-01-09 00:16 adapter0 drwxr-xr-x 2 root root 200 2006-01-09 00:16 adapter1 drwxr-xr-x 2 root root 200 2006-01-09 00:16 adapter2 drwxr-xr-x 2 root root 200 2006-01-09 00:16 adapter3 /dev/dvb/adapter0: total 0 crw-rw---- 1 root video 212, 1 2006-01-09 00:16 audio0 crw-rw---- 1 root video 212, 6 2006-01-09 00:16 ca0 crw-rw---- 1 root video 212, 4 2006-01-09 00:16 demux0 crw-rw---- 1 root video 212, 5 2006-01-09 00:16 dvr0 crw-rw---- 1 root video 212, 3 2006-01-09 00:16 frontend0 crw-rw---- 1 root video 212, 7 2006-01-09 00:16 net0 crw-rw---- 1 root video 212, 8 2006-01-09 00:16 osd0 crw-rw---- 1 root video 212, 0 2006-01-09 00:16 video0 /dev/dvb/adapter1: total 0 crw-rw---- 1 root video 212, 65 2006-01-09 00:16 audio0 crw-rw---- 1 root video 212, 70 2006-01-09 00:16 ca0 crw-rw---- 1 root video 212, 68 2006-01-09 00:16 demux0 crw-rw---- 1 root video 212, 69 2006-01-09 00:16 dvr0 crw-rw---- 1 root video 212, 67 2006-01-09 00:16 frontend0 crw-rw---- 1 root video 212, 71 2006-01-09 00:16 net0 crw-rw---- 1 root video 212, 72 2006-01-09 00:16 osd0 crw-rw---- 1 root video 212, 64 2006-01-09 00:16 video0 /dev/dvb/adapter2: total 0 crw-rw---- 1 root video 212, 129 2006-01-09 00:16 audio0 crw-rw---- 1 root video 212, 134 2006-01-09 00:16 ca0 crw-rw---- 1 root video 212, 132 2006-01-09 00:16 demux0 crw-rw---- 1 root video 212, 133 2006-01-09 00:16 dvr0 crw-rw---- 1 root video 212, 131 2006-01-09 00:16 frontend0 crw-rw---- 1 root video 212, 135 2006-01-09 00:16 net0 crw-rw---- 1 root video 212, 136 2006-01-09 00:16 osd0 crw-rw---- 1 root video 212, 128 2006-01-09 00:16 video0 /dev/dvb/adapter3: total 0 crw-rw---- 1 root video 212, 193 2006-01-09 00:16 audio0 crw-rw---- 1 root video 212, 198 2006-01-09 00:16 ca0 crw-rw---- 1 root video 212, 196 2006-01-09 00:16 demux0 crw-rw---- 1 root video 212, 197 2006-01-09 00:16 dvr0 crw-rw---- 1 root video 212, 195 2006-01-09 00:16 frontend0 crw-rw---- 1 root video 212, 199 2006-01-09 00:16 net0 crw-rw---- 1 root video 212, 200 2006-01-09 00:16 osd0 crw-rw---- 1 root video 212, 192 2006-01-09 00:16 video0 many thanks

1 0

VDR 1.3.38: menu key no longer works
by Peter Bieringer 08 Jan '06

08 Jan '06

Hi, are there any changes if lirc and terminal are used in common? While menu key works on remote control, it no longer works on keyboard (I use F12 for that). 1.3.37 works fine. Any hints available? Thank you, Peter

2 10

Streamdev and Xine Client Not working
by Mlists 08 Jan '06

08 Jan '06

Hi all, I'm running vdr 1.3.37, I am currently using cvs version of streamdev. I'm running Xine 0.7.6. On the slave machine I start up vdr with ./vdr -P'xine -r' -Pstreamdev-client It starts up, connects to the backend no problem and gets the last channel it was on and shows video. So initial communication works. When I attempt to change channels, I no longer get video. I can see the channel flip on the backend but nothing on the client. 1) is there any way I can increase debugging output to tell me where exactly the problem seems to be? 2) Has anyone else seen this and got it resolved? My output is: SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 [vVMMMSetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 aA+7+8+12+14+15+17+19+22] buffered 21.5 frames SetPlayMode: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 vdr-xine: Client disconnected! SetPlayMode: 0

2 3

vdr-1.3.38 and ttxtsubs: menu not visbile in recording if teletext subtitles active
by Luca Olivetti 08 Jan '06

08 Jan '06

As per the subject, if the teletext subtitles are active during replay it's impossible to select the menu. The attached patch fixes it but I don't know it it may have other adverse effects (it doesn't seems so here). Bye -- - Yo también quiero una Europa libre de Patentes de Software - - I want a Software Patents Free Europe too! And you? - --------------------------------------------------------------- EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es

1 0

problem with timer and VPS
by Wolfgang Rohdewald 08 Jan '06

08 Jan '06

Hi, from my log: Jan 7 23:36:32 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') start Jan 7 23:36:32 mm vdr[3539]: record /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 00:02:22 mm vdr[3539]: replay /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 01:00:43 mm vdr[3544]: channel 1 (Das Erste) event 23:35 'James Bond 007 - Der Hauch des Todes' status 1 Jan 8 01:00:44 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') stop Jan 8 01:41:51 mm vdr[3544]: channel 1 (Das Erste) event 01:40 'Tagesschau' status 4 01:00 is about the time when the programm SHOULD have stopped. It SHOULD have started at 22:40, EPG said so. But it really started at 23:35. VPS start was correct, but the end went wrong, it stopped about 1 hour too early. Normally it seems the time between status 1 and the next status 4 is quite short, here it was 41 minutes. Would it be possible to change the messages status 1 etc into something more verbose? And maybe it would help not to stop a timer before the EPG length of the program has passed, no matter what the status says. -- Wolfgang

3 6

[ANNOUNCE] Channelscan Plugin 0.0.5a
by tinconn＠virgilio.it 08 Jan '06

08 Jan '06

Hi a new version of plugin channelscan has been released. Channelscan uses a transponders .ini file from win project like prog-DVB software for create a channels.conf The homepage of the plugin is at http://www.kikko77.altervista.org goto download page for the get it --------------------------------------------------------------------------------------------------------- 2006-01-08: Version 0.0.5a - Add finnish translaction (from www.gentoo.de) - Add menuitem patch (from www.gentoo.de) *** Thanks for all patch, but in future if anyone want to send me it, i release a new version of plugin, so all vdr user have a lot benefits. ***

1 0

← Newer
1
...
13
14
15
16
17
18
19
20
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2006