[vdr] [ANNOUNCE] VDR developer version 1.7.30

Klaus Schmidinger Klaus.Schmidinger at tvdr.de
Tue Sep 18 12:55:25 CEST 2012


On 17.09.2012 23:17, Mika Laitio wrote:
> On 09/10/2012 05:05 PM, Klaus Schmidinger wrote:
>> VDR developer version 1.7.30 is now available at
>
> I tried to use for a first time with VDR the HVR-4000's multible
> delivery systems under same frontend feature that was introduced in
> 1.7.23. (HVR-4000 has DVB-T and DVB-S/S2 in the same card but only one
> of these delivery systems can work at a time.) In addition I have normal
> hvr-1300 DVB-T only tuner. If I connect cable only to HVR-4000,
> I can not get DVB-T channels visible with VDR. (but dvb apps like scan
> will work from the command line).
>
> The error looks similar than somebody else reported at a time when
> 1.7.23 was released but now I would expect of having new enough kernel
> running. My system info and logs are following:
>
> 1) Kernel version:
> 	3.3.8-desktop-2.mga2
>
> DVB API version is 5.5 (grep DVB-API)
>
> 	include/linux/dvb/version.h:#define DVB_API_VERSION 5
> 	include/linux/dvb/version.h:#define DVB_API_VERSION_MINOR 5
>
> 2) tree /dev/dvb/
> /dev/dvb/
> ├── adapter0
> │   ├── demux0
> │   ├── dvr0
> │   ├── frontend0
> │   └── net0
> └── adapter1
>      ├── demux0
>      ├── demux1
>      ├── dvr0
>      ├── dvr1
>      ├── frontend0
>      ├── frontend1
>      ├── net0
>      └── net1
>
> 3) VDR log which indicates device or resource busy error for
> adapter1/fronend1 device.

[ kls: fixed wrapped log lines ]

> Sep 17 23:51:34 localhost vdr: [15256] VDR version 1.7.30 started
> Sep 17 23:51:34 localhost vdr: [15256] codeset is 'UTF-8' - known
> Sep 17 23:51:34 localhost vdr: [15256] found 28 locales in ./locale
> Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-xineliboutput.so.1.7.30
> Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-osdteletext.so.1.7.30
> Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-skinsoppalusikka.so.1.7.30
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/setup.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/sources.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/diseqc.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/scr.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/channels.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/timers.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/svdrphosts.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/remote.conf
> Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/keymacros.conf
> Sep 17 23:51:34 localhost vdr: [15257] video directory scanner thread started (pid=15256, tid=15257)
> Sep 17 23:51:34 localhost vdr: [15258] video directory scanner thread started (pid=15256, tid=15258)
> Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'A - ATSC'
> Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'C - DVB-C'
> Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'S - DVB-S'
> Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'T - DVB-T'
> Sep 17 23:51:34 localhost vdr: [15256] probing /dev/dvb/adapter0/frontend0
> Sep 17 23:51:34 localhost vdr: [15256] creating cDvbDevice
> Sep 17 23:51:34 localhost vdr: [15256] new device number 1
> Sep 17 23:51:34 localhost vdr: [15259] epg data reader thread started (pid=15256, tid=15259)
> Sep 17 23:51:34 localhost vdr: [15259] reading EPG data from /storagedisc/video/epg.data
> Sep 17 23:51:34 localhost vdr: [15258] video directory scanner thread ended (pid=15256, tid=15258)
> Sep 17 23:51:34 localhost vdr: [15256] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("Conexant CX22702 DVB-T")
> Sep 17 23:51:34 localhost vdr: [15256] probing /dev/dvb/adapter1/frontend0
> Sep 17 23:51:34 localhost vdr: [15256] creating cDvbDevice
> Sep 17 23:51:34 localhost vdr: [15256] new device number 2
> Sep 17 23:51:34 localhost vdr: [15261] tuner on frontend 0/0 thread started (pid=15256, tid=15261)
> Sep 17 23:51:34 localhost vdr: [15261] cTimeMs: using monotonic clock (resolution is 1 ns)
> Sep 17 23:51:34 localhost vdr: [15262] section handler thread started (pid=15256, tid=15262)
> Sep 17 23:51:34 localhost vdr: [15257] video directory scanner thread ended (pid=15256, tid=15257)
> Sep 17 23:51:34 localhost vdr: [15256] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Conexant CX24116/CX24118")
> Sep 17 23:51:34 localhost vdr: [15265] section handler thread started (pid=15256, tid=15265)
> Sep 17 23:51:34 localhost vdr: [15264] tuner on frontend 1/0 thread started (pid=15256, tid=15264)
> Sep 17 23:51:34 localhost vdr: [15259] epg data reader thread ended (pid=15256, tid=15259)
> Sep 17 23:51:39 localhost vdr: [15256] ERROR (dvbdevice.c,1058): /dev/dvb/adapter1/frontend1: Device or resource busy
> Sep 17 23:51:39 localhost vdr: [15256] found 2 DVB devices

If this device can only provide one delivery system at a time, they all need
to be provided through the *same* frontend.

 From the log I can see that the driver apparently makes DVB-S/DVB-S2 available
under adapter1/frontend0 and tries to provide DVB-T on adapter1/frontend1.
But if it does so, it tells the application that it can provide DVB-S/DVB-S2
*and* DVB-T at the *same* time - which apparently isn't the case.

Klaus



More information about the vdr mailing list