Re: vdr not working in Raspbian 10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



El 29/11/20 a les 22:13, Helmut Binder ha escrit:
> On Sun, 29 Nov 2020 17:53:27 +0100
> Narcis Garcia <debianlists@xxxxxxxxx> 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@xxxxxxxxx> 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-frontend-devices/&postID=1308966#post1308966
>>>>
>>>>
>>>> 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.


_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux