Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data. Tried with two clients Kodi software with its VDR plugin (screen interface) and with vdradmin-am (web interface).
What can I check to find the problem?
Notes: - TV dongle works; if I stop vdr service and use GUI applicacion Kaffeine, I can watch all TV channels. - I see VDR service attending TCP ports 34890 (VNSI), 6419 and 2010
Thank you.
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
_________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
El 28/11/20 a les 17:44, Narcis Garcia ha escrit:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
WHEN I JUST START SERVICE:
$ sudo systemctl status vdr ● vdr.service - Video Disk Recorder Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-11-28 17:31:10 CET; 13s ago Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh commands (code=exited, status=0/SUCCESS) Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh reccmds (code=exited, status=0/SUCCESS) Main PID: 30508 (vdr) Status: "Ready" Tasks: 9 (limit: 3748) CGroup: /system.slice/vdr.service └─30508 /usr/bin/vdr
de nov. 28 17:31:10 raspberrypi vdr[30508]: [30508] ERROR: no OSD provider available - using dummy OSD! de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] loading /var/cache/vdr/cam.data de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] switching to channel 1 T-0-17-155 (mega) de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] setting watchdog timer to 60 seconds de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP server handler thread started (pid=30508, tid=32663, prio=low) de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi opening port 6419/tcp de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi listening on port 6419/tcp de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] OSD size changed to 720x480 @ 1 de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] ERROR: no OSD provider available - using dummy OSD! de nov. 28 17:31:21 raspberrypi vdr[30508]: [30508] max. latency time 1 seconds
AFTER A MINUTE OF RUNNING SERVICE (I was trying to switch TV channel from a client):
$ sudo systemctl status vdr ● vdr.service - Video Disk Recorder Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-11-28 17:31:10 CET; 2min 21s ago Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh commands (code=exited, status=0/SUCCESS) Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh reccmds (code=exited, status=0/SUCCESS) Main PID: 30508 (vdr) Status: "Ready" Tasks: 9 (limit: 3748) CGroup: /system.slice/vdr.service └─30508 /usr/bin/vdr
de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:16 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:18 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:24 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:25 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586
On 28.11.20 17:55, Narcis Garcia wrote:
... de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586
Maybe a bad cable/connector?
Klaus
El 28/11/20 a les 23:01, Klaus Schmidinger ha escrit:
On 28.11.20 17:55, Narcis Garcia wrote:
... de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586
Maybe a bad cable/connector?
Klaus
Should not, because Kaffeine app lets watch TV (with VDR stopped). Narcís.
El 29/11/20 a les 9:42, Narcis Garcia ha escrit:
El 28/11/20 a les 23:01, Klaus Schmidinger ha escrit:
On 28.11.20 17:55, Narcis Garcia wrote:
... de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost lock on channel 23 (Telecinco), tp 586 de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0 regained lock on channel 23 (Telecinco), tp 586
Maybe a bad cable/connector?
Klaus
Should not, because Kaffeine app lets watch TV (with VDR stopped). Narcís.
I've used "VDR Live" to restart service while tracking log with "journalctl -xef -u vdr"
*LOG:*
de nov. 29 11:29:47 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support
El 29/11/20 a les 11:44, Klaus Schmidinger ha escrit:
On 29.11.20 11:33, Narcis Garcia wrote:
... de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR (dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o recurs es troba ocupat
If this error message was given in English I might be able to interpret it.
Klaus
"Device or resource is busy"
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
You need to select correct frontend like this:
#!/bin/bash
var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')
echo 'A0 Second frontend is ' $var
if [ $var == 'MN88473' ]; then
echo 'A0 frontend is ' $var
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2 mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0 mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1
fi
var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')
if [ $var == 'MN88473' ]; then
dvb-fe-tool -a0 -f0 -d DVBT2
dvb-fe-tool -a0 -f0 -g |grep DELIVERY
fi
************************ Second frontend with this adapter can handle DVBC/ANNEX_A too.
Vdr should know both frontends and use correct one and setup delivery system either by setup parameter or trying which one is working and prefer DVBT2. With satelite channnels it knows when to use S2. W_scan can handle this too.
Other version of this device can have CXD2837ER as second frontend name.
Timo
Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
You need to select correct frontend like this:
#!/bin/bash
var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')
echo 'A0 Second frontend is ' $var
if [ $var == 'MN88473' ]; then
echo 'A0 frontend is ' $var
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2 mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0 mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1
fi
var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')
if [ $var == 'MN88473' ]; then
dvb-fe-tool -a0 -f0 -d DVBT2
dvb-fe-tool -a0 -f0 -g |grep DELIVERY
fi
Second frontend with this adapter can handle DVBC/ANNEX_A too.
Vdr should know both frontends and use correct one and setup delivery system either by setup parameter or trying which one is working and prefer DVBT2. With satelite channnels it knows when to use S2. W_scan can handle this too.
Other version of this device can have CXD2837ER as second frontend name.
Timo
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
More info:
http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.htm...
Timo
Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I didn't know about. As an external tool, that now tunes DVB-T2 HD channels for me at last - the only thing outside VDR itself that works so far :-)
Richard
On 29/11/2020 2:16 pm, Timo Helkiö wrote:
Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
The project sources repository (sadly in a proprietary platform):
https://github.com/stefantalpalaru/w_scan2
Narcis Garcia
El 30/11/20 a les 19:47, Richard F ha escrit:
Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I didn't know about. As an external tool, that now tunes DVB-T2 HD channels for me at last - the only thing outside VDR itself that works so far :-)
Richard
On 29/11/2020 2:16 pm, Timo Helkiö wrote:
Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote: > Hello, > > I've installed vdr from Raspbian packages, to use it with Kodi. > I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV > channels are found. > > But I try to watch some channel and I get no data.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
A simplified alternative to w_scan2:
https://github.com/mighty-p/t2scan/
Narcis Garcia
El 1/12/20 a les 8:50, Narcis Garcia ha escrit:
The project sources repository (sadly in a proprietary platform):
https://github.com/stefantalpalaru/w_scan2
Narcis Garcia
El 30/11/20 a les 19:47, Richard F ha escrit:
Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I didn't know about. As an external tool, that now tunes DVB-T2 HD channels for me at last - the only thing outside VDR itself that works so far :-)
Richard
On 29/11/2020 2:16 pm, Timo Helkiö wrote:
Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit: > On 28.11.20 17:30, Narcis Garcia wrote: >> Hello, >> >> I've installed vdr from Raspbian packages, to use it with Kodi. >> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV >> channels are found. >> >> But I try to watch some channel and I get no data. >
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
I cloned it and built it from that source on OpenSuSe 15.2, no problem (well quite a few warnings...!)
On 1/12/2020 7:50 am, Narcis Garcia wrote:
The project sources repository (sadly in a proprietary platform):
https://github.com/stefantalpalaru/w_scan2
Narcis Garcia
El 30/11/20 a les 19:47, Richard F ha escrit:
Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I didn't know about. As an external tool, that now tunes DVB-T2 HD channels for me at last - the only thing outside VDR itself that works so far :-)
Richard
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
$ ps -A -o user,group,cmd | grep -ie vdr vdradmi+ vdradmi+ vdradmind pi pi grep --color=auto -ie vdr vdr vdr /usr/bin/vdr
$ groups vdr vdr : vdr video
I'm trying now with vdr-plugin-live : Same unsuccess result.
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
You need to select correct frontend like this:
#!/bin/bash
var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')
echo 'A0 Second frontend is ' $var
if [ $var == 'MN88473' ]; then
echo 'A0 frontend is ' $var
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2 mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0 mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1
fi
var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')
if [ $var == 'MN88473' ]; then
dvb-fe-tool -a0 -f0 -d DVBT2
dvb-fe-tool -a0 -f0 -g |grep DELIVERY
fi
Second frontend with this adapter can handle DVBC/ANNEX_A too.
Vdr should know both frontends and use correct one and setup delivery system either by setup parameter or trying which one is working and prefer DVBT2. With satelite channnels it knows when to use S2. W_scan can handle this too.
Other version of this device can have CXD2837ER as second frontend name.
Timo
Not matching cases: Once I've installed dvb-tools to have dvb-fe-tool program: $ sudo systemctl stop vdr $ dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}' CXD2837ER $ dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}' RTL2832 $ sudo systemctl start vdr
This is the assembled device: https://osmc.tv/store/product/tv-dongle/
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
I've done this like a backport from next Raspbian version:
$ sudo apt -t bullseye install vdr
/[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7 libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus libreadline8 libtirpc-dev runit-helper/
/[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages manpages-dev openssh-client openssh-server openssh-sftp-server python3.7 python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
(...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
$ sudo systemctl stop vdr
$ sudo systemctl start vdr
$ sudo journalctl -xef -u vdr
de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support
On Sun, 29 Nov 2020 17:53:27 +0100 Narcis Garcia debianlists@actiu.net wrote:
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote:
Hello,
I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found.
But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
I've done this like a backport from next Raspbian version:
$ sudo apt -t bullseye install vdr
/[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7 libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus libreadline8 libtirpc-dev runit-helper/
/[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages manpages-dev openssh-client openssh-server openssh-sftp-server python3.7 python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
(...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
$ sudo systemctl stop vdr
$ sudo systemctl start vdr
$ sudo journalctl -xef -u vdr
de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd
-- Support: https://www.debian.org/support
-- A start job for unit vdr.service has begun execution.
-- The job identifier is 867922. de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] VDR version 2.4.1 started de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] switched to user 'vdr' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] codeset is 'UTF-8' - known de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] found 28 locales in /usr/share/locale de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] [live] INFO: validating server ip '0.0.0.0' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: INFO: validating live server ip '0.0.0.0' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/setup.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/sources.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/diseqc.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/scr.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/channels.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/timers.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/commands.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/reccmds.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/svdrphosts.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/keymacros.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26843] video directory scanner thread started (pid=26842, tid=26843, prio=low) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'A - ATSC' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] epg data reader thread started (pid=26842, tid=26844, prio=high) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'C - DVB-C' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'S - DVB-S' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] reading EPG data from /var/cache/vdr/epg.data de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'T - DVB-T' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26843] video directory scanner thread ended (pid=26842, tid=26843) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] detected /dev/dvb/adapter0/frontend0 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] epg data reader thread ended (pid=26842, tid=26844) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] probing /dev/dvb/adapter0/frontend0 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] creating cDvbDevice de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] new device number 1 (card index 1) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] DVB API version is 0x050B (VDR was built with 0x050B) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("Realtek RTL2832 (DVB-T)") de nov. 29 17:41:32 raspberrypi vdr[26842]: [26842] frontend 0/1 provides DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Sony CXD2837ER DVB-T/T2/C demodulator") de nov. 29 17:41:33 raspberrypi vdr[26842]: [26895] frontend 0/0+1 tuner thread started (pid=26842, tid=26895, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26896] device 1 section handler thread started (pid=26842, tid=26896, prio=low) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26895] cTimeMs: using monotonic clock (resolution is 1 ns) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] cTimeMs: using monotonic clock (resolution is 1 ns) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] found 1 DVB device de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: femon (2.4.0): DVB Signal Information Monitor (OSD) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: live (2.3.1): Live Interactive VDR Environment de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: osdserver (0.1.3): Server for remote OSD clients de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: vnsiserver (1.8.0): VDR-Network-Streaming-Interface (VNSI) Server de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] setting primary device to 1 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] device 1 has no MPEG decoder de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] assuming manual start of VDR de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] setting current skin to "lcars" de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/themes/lcars-default.theme de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: femon de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: live de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] LIVE: initial file cache has 82 entries and needs 377394 bytes of data! de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: osdserver de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: vnsiserver de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: Starting vnsi server at port=34890 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: VNSI Server started de nov. 29 17:41:33 raspberrypi systemd[1]: Started Video Disk Recorder. -- Subject: A start job for unit vdr.service has finished successfully -- Defined-By: systemd
-- Support: https://www.debian.org/support
-- A start job for unit vdr.service has finished successfully.
-- The job identifier is 867922. de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: Channel streaming timeout: 10 seconds de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] VNSI Server thread started (pid=26842, tid=26899, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] remote control LIRC
- learning keys
de nov. 29 17:41:33 raspberrypi vdr[26842]: [26898] osdserver thread started (pid=26842, tid=26898, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26901] VNSIStatus thread started (pid=26842, tid=26901, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26900] LIRC remote control thread started (pid=26842, tid=26900, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26897] [live] INFO: attempt to listen on ip = '0.0.0.0' de nov. 29 17:41:33 raspberrypi vdr[26842]: [26897] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): El fitxer o directori no existeix de nov. 29 17:41:33 raspberrypi vdr[26842]: [26902] VNSITimers thread started (pid=26842, tid=26902, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] VNSI: Client with ID 0 connected: 127.0.0.1:41572 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26910] VNSI Client 0->127.0.0.1:41572 thread started (pid=26842, tid=26910, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26910] VNSI: Welcome client 'XBMC Media Center' with protocol version '13' de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] loading /var/cache/vdr/cam.data de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] switching to channel 1 T-0-17-155 (mega) de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] setting watchdog timer to 60 seconds de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP server handler thread started (pid=26842, tid=26974, prio=low) de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP raspberrypi opening port 6419/tcp de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP raspberrypi listening on port 6419/tcp de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] OSD size changed to 720x480 @ 1 de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] max. latency time 1 seconds de nov. 29 17:41:47 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:47 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:51 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:51 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:53 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:54 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:55 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:57 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:57 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:01 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:01 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:04 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:04 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:07 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:07 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:10 raspberrypi vdr[26842]: [26842] switching to channel 1 T-0-17-155 (mega) de nov. 29 17:42:11 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:11 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:14 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:15 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:19 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:19 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:23 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:23 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:27 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:27 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:30 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:30 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:34 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:35 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:38 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:39 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:42 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:43 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:47 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:47 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:50 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:51 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:54 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:54 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:58 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:58 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:00 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:00 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:03 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:04 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:06 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:06 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:09 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:10 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:12 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:12 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:14 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:15 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:18 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:19 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:22 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:23 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538
Same behaviour from Kodi and from "VDR Live": No TV signal shown*.*
PD: This mailing list should be configured to allow HTML format (long lines, fixed-width...)
Can you receive any DVB-T2 Channels ? These would use frontend 0/1 with the CXD2837ER demodulator and you could compare the tuning. If not, rename frontend1 to frontend0, similar as in Timo's proposal:
- stop vdr
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/Xfrontend0" mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0"
- start vdr
Helmut
El 29/11/20 a les 22:13, Helmut Binder ha escrit:
On Sun, 29 Nov 2020 17:53:27 +0100 Narcis Garcia debianlists@actiu.net wrote:
El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
Helmut Binder kirjoitti 29.11.2020 klo 15.11:
On Sat, 28 Nov 2020 17:44:32 +0100 Narcis Garcia debianlists@actiu.net wrote:
I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
On 28.11.20 17:30, Narcis Garcia wrote: > Hello, > > I've installed vdr from Raspbian packages, to use it with Kodi. > I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV > channels are found. > > But I try to watch some channel and I get no data.
Does the user id under which you run VDR have access to the DVB devices?
Klaus
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
Helmut
I've done this like a backport from next Raspbian version:
$ sudo apt -t bullseye install vdr
/[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7 libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus libreadline8 libtirpc-dev runit-helper/
/[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages manpages-dev openssh-client openssh-server openssh-sftp-server python3.7 python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
(...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
$ sudo systemctl stop vdr
$ sudo systemctl start vdr
$ sudo journalctl -xef -u vdr
de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder... -- Subject: A start job for unit vdr.service has begun execution -- Defined-By: systemd
-- Support: https://www.debian.org/support
-- A start job for unit vdr.service has begun execution.
-- The job identifier is 867922. de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] VDR version 2.4.1 started de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] switched to user 'vdr' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] codeset is 'UTF-8' - known de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] found 28 locales in /usr/share/locale de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] [live] INFO: validating server ip '0.0.0.0' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: INFO: validating live server ip '0.0.0.0' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/setup.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/sources.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/diseqc.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/scr.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/channels.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/timers.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/commands.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/reccmds.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/svdrphosts.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/keymacros.conf de nov. 29 17:41:31 raspberrypi vdr[26842]: [26843] video directory scanner thread started (pid=26842, tid=26843, prio=low) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'A - ATSC' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] epg data reader thread started (pid=26842, tid=26844, prio=high) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'C - DVB-C' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'S - DVB-S' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] reading EPG data from /var/cache/vdr/epg.data de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source parameters for 'T - DVB-T' de nov. 29 17:41:31 raspberrypi vdr[26842]: [26843] video directory scanner thread ended (pid=26842, tid=26843) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] detected /dev/dvb/adapter0/frontend0 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] epg data reader thread ended (pid=26842, tid=26844) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] probing /dev/dvb/adapter0/frontend0 de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] creating cDvbDevice de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] new device number 1 (card index 1) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] DVB API version is 0x050B (VDR was built with 0x050B) de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("Realtek RTL2832 (DVB-T)") de nov. 29 17:41:32 raspberrypi vdr[26842]: [26842] frontend 0/1 provides DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Sony CXD2837ER DVB-T/T2/C demodulator") de nov. 29 17:41:33 raspberrypi vdr[26842]: [26895] frontend 0/0+1 tuner thread started (pid=26842, tid=26895, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26896] device 1 section handler thread started (pid=26842, tid=26896, prio=low) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26895] cTimeMs: using monotonic clock (resolution is 1 ns) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] cTimeMs: using monotonic clock (resolution is 1 ns) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] found 1 DVB device de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: femon (2.4.0): DVB Signal Information Monitor (OSD) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: live (2.3.1): Live Interactive VDR Environment de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: osdserver (0.1.3): Server for remote OSD clients de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] initializing plugin: vnsiserver (1.8.0): VDR-Network-Streaming-Interface (VNSI) Server de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] setting primary device to 1 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] device 1 has no MPEG decoder de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] assuming manual start of VDR de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] setting current skin to "lcars" de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] loading /var/lib/vdr/themes/lcars-default.theme de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: femon de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: live de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] LIVE: initial file cache has 82 entries and needs 377394 bytes of data! de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: osdserver de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] starting plugin: vnsiserver de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: Starting vnsi server at port=34890 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: VNSI Server started de nov. 29 17:41:33 raspberrypi systemd[1]: Started Video Disk Recorder. -- Subject: A start job for unit vdr.service has finished successfully -- Defined-By: systemd
-- Support: https://www.debian.org/support
-- A start job for unit vdr.service has finished successfully.
-- The job identifier is 867922. de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] VNSI: Channel streaming timeout: 10 seconds de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] VNSI Server thread started (pid=26842, tid=26899, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] remote control LIRC
- learning keys
de nov. 29 17:41:33 raspberrypi vdr[26842]: [26898] osdserver thread started (pid=26842, tid=26898, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26901] VNSIStatus thread started (pid=26842, tid=26901, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26900] LIRC remote control thread started (pid=26842, tid=26900, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26897] [live] INFO: attempt to listen on ip = '0.0.0.0' de nov. 29 17:41:33 raspberrypi vdr[26842]: [26897] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): El fitxer o directori no existeix de nov. 29 17:41:33 raspberrypi vdr[26842]: [26902] VNSITimers thread started (pid=26842, tid=26902, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf de nov. 29 17:41:33 raspberrypi vdr[26842]: [26899] VNSI: Client with ID 0 connected: 127.0.0.1:41572 de nov. 29 17:41:33 raspberrypi vdr[26842]: [26910] VNSI Client 0->127.0.0.1:41572 thread started (pid=26842, tid=26910, prio=high) de nov. 29 17:41:33 raspberrypi vdr[26842]: [26910] VNSI: Welcome client 'XBMC Media Center' with protocol version '13' de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] loading /var/cache/vdr/cam.data de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] switching to channel 1 T-0-17-155 (mega) de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] setting watchdog timer to 60 seconds de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP server handler thread started (pid=26842, tid=26974, prio=low) de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP raspberrypi opening port 6419/tcp de nov. 29 17:41:43 raspberrypi vdr[26842]: [26974] SVDRP raspberrypi listening on port 6419/tcp de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] OSD size changed to 720x480 @ 1 de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:43 raspberrypi vdr[26842]: [26842] max. latency time 1 seconds de nov. 29 17:41:47 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:47 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:51 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:51 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:53 raspberrypi vdr[26842]: [26842] ERROR: no OSD provider available - using dummy OSD! de nov. 29 17:41:54 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:55 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:41:57 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:41:57 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:01 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:01 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:04 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:04 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:07 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:07 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:10 raspberrypi vdr[26842]: [26842] switching to channel 1 T-0-17-155 (mega) de nov. 29 17:42:11 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:11 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:14 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:15 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:19 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:19 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:23 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:23 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:27 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:27 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:30 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:30 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:34 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:35 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:38 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:39 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:42 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:43 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:47 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:47 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:50 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:51 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:54 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:54 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:42:58 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:42:58 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:00 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:00 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:03 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:04 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:06 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:06 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:09 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:10 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:12 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:12 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:14 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:15 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:18 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:19 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538 de nov. 29 17:43:22 raspberrypi vdr[26842]: [26895] frontend 0/0 lost lock on channel 1 (mega), tp 538 de nov. 29 17:43:23 raspberrypi vdr[26842]: [26895] frontend 0/0 regained lock on channel 1 (mega), tp 538
Same behaviour from Kodi and from "VDR Live": No TV signal shown*.*
PD: This mailing list should be configured to allow HTML format (long lines, fixed-width...)
Can you receive any DVB-T2 Channels ? These would use frontend 0/1 with the CXD2837ER demodulator and you could compare the tuning. If not, rename frontend1 to frontend0, similar as in Timo's proposal:
- stop vdr
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/Xfrontend0" mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0"
- start vdr
Helmut
With w_scan2 (and also Kaffeine) I can tune both DVB-T and DVB-T2 channels. VDR is not playing anyone of them.
El 29/11/20 a les 22:13, Helmut Binder ha escrit:
Can you receive any DVB-T2 Channels ? These would use frontend 0/1 with the CXD2837ER demodulator and you could compare the tuning. If not, rename frontend1 to frontend0, similar as in Timo's proposal:
- stop vdr
mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/Xfrontend0" mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0"
- start vdr
Helmut
Tried this workaround several times, and last one resulted but in this order:
1. Tuned channels with devices/frontends "as is" 2. moved frontend1 to frontend0
I'm pending to do more testing and be sure this is the point for my case.
__________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 29/11/20 a les 14:11, Helmut Binder ha escrit:
$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 140 de nov. 28 15:57 . drwxr-xr-x 3 root root 60 de nov. 28 15:57 .. crw-rw----+ 1 root video 212, 4 de nov. 28 15:57 demux0 crw-rw----+ 1 root video 212, 5 de nov. 28 15:57 dvr0 crw-rw----+ 1 root video 212, 3 de nov. 28 15:57 frontend0 crw-rw----+ 1 root video 212, 19 de nov. 28 15:57 frontend1 crw-rw----+ 1 root video 212, 7 de nov. 28 15:57 net0
This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this patch from here: https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi...
I've just tried same device with Ubuntu 20.10 (it has VDR 2.4.1 on repositories) This is not fixed in this version. I had to do the frontend0 <-> frontend1 workaround to have it working (channels scan must be done without frontends swap). And no EPG. Same results as with Raspbian 10
-
Helmut Binder -
Klaus Schmidinger -
Narcis Garcia -
Richard F -
Timo Helkiö