muxes - will not start
Added by Thomas Schmidt over 4 years ago
Hi!
I've configured the basics of tvheadend and just wanted to do a first scan of the channels/services.
No services found for over an hour.
I changed the network-setting with 'creating bouquet = yes' just to see if there is a change.
You can see my settings in the attached files...
Is there something going wrong? Any hints?
1 - TV-Adapter.png (17.6 KB) 1 - TV-Adapter.png | |||
2 - Netzwerk.png (78.6 KB) 2 - Netzwerk.png | |||
3 - Muxes.png (158 KB) 3 - Muxes.png |
Replies (10)
RE: muxes - will not start - Added by Thomas Schmidt over 4 years ago
24h later still no service - nothing changed...
I can hit the force scan button as much as I want...
If my question is just plain stupid, let me know, please.
RE: muxes - will not start - Added by Hiro Protagonist over 4 years ago
I don't know if I can be much help here but...
Try opening the log view on the Muxes tab [use the double ^ button at the bottom RHS].
Then select one mux, click 'Scan Status' and change to 'Active', then click 'Save'.
See if any useful log messages are output.
RE: muxes - will not start - Added by Thomas Schmidt over 4 years ago
Hi Hiro Protagonist!
I've unintalled tvheadend and set it up again, as I could not see any solution. There wasn't even a systemctl stop tvheadend possible...
RE: muxes - will not start - Added by saen acro over 4 years ago
Is tuner work aka drivers signal etc.
RE: muxes - will not start - Added by Thomas Schmidt over 4 years ago
According to this kernel messages, the tuner is up and running:
sudo dmesg | grep ddbridge [ 6.754855] ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH [ 6.764297] ddbridge 0000:03:00.0: detected Digital Devices Octopus CI [ 6.764322] ddbridge 0000:03:00.0: HW 0101000c REGMAP 00010005 [ 6.781232] ddbridge 0000:03:00.0: Port 0: Link 0, Link Port 0 (TAB 1): NO MODULE [ 6.782280] ddbridge 0000:03:00.0: Port 1: Link 0, Link Port 1 (TAB 2): NO MODULE [ 6.782283] ddbridge 0000:03:00.0: Port 2: Link 0, Link Port 2 (TAB 3): CI internal [ 6.782286] ddbridge 0000:03:00.0: Port 3: Link 0, Link Port 3 (TAB 4): CI internal
Is there any log to have a look at signals the tuner is receiving?
sudo systemctl status tvheadend.service [sudo] Passwort für tom: ● tvheadend.service - Tvheadend - a TV streaming server and DVR Loaded: loaded (/usr/lib/systemd/system/tvheadend.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2020-02-29 14:51:40 CET; 20min ago Main PID: 34021 (tvheadend) Tasks: 34 (limit: 16702) Memory: 17.6M CGroup: /system.slice/tvheadend.service └─34021 /usr/bin/tvheadend -f -p /var/run/tvheadend.pid -u hts -g video -6 --http_port 9981 --htsp_port > Feb 29 14:56:25 Halut-NAS tvheadend[34021]: linuxdvb: dvbca0-0: CAM slot 0 status changed to module init Feb 29 14:56:26 Halut-NAS tvheadend[34021]: linuxdvb: dvbca0-0: CAM slot 0 status changed to module connected Feb 29 14:56:27 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00030041/0002: CAM supported CAIDs: 1838 (NagraV> Feb 29 14:56:27 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00030041/0002: CAM supported CAIDs: 1762 (BetaCr> Feb 29 14:56:27 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00030041/0002: CAM supported CAIDs: 0100 (Seca) > Feb 29 14:56:27 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00030041/0002: CAM supported CAIDs: 0D95 (Crypto> Feb 29 14:56:27 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00030041/0002: CAM supported CAIDs: 0919 (NDS) 0> Feb 29 14:56:27 Halut-NAS tvheadend[34021]: linuxdvb: dvbca0-0: CAM slot 0 status changed to module ready Feb 29 14:56:28 Halut-NAS tvheadend[34021]: en50221: dvbca1-slot0-app00020041/0004: CAM INFO: AlphaCrypt, 01, 4A20, 4> Feb 29 15:01:19 Halut-NAS systemd[1]: /usr/lib/systemd/system/tvheadend.service:9: PIDFile= references a path below l>
1 - TV-Adapter.png (9.43 KB) 1 - TV-Adapter.png | |||
2 - Netzwerk.png (78.6 KB) 2 - Netzwerk.png | |||
4 - Services.png (27.6 KB) 4 - Services.png | |||
3 - Muxes.png (124 KB) 3 - Muxes.png | |||
5 - log.png (73.3 KB) 5 - log.png |
RE: muxes - will not start - Added by saen acro over 4 years ago
Someone is forgot to put power to tuner
dmesg |grep TAB [ 11.985145] ddbridge 0000:04:00.0: Port 0: Link 0, Link Port 0 (TAB 1): NO MODULE [ 11.986109] ddbridge 0000:04:00.0: Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 [ 11.987113] ddbridge 0000:04:00.0: Port 2: Link 0, Link Port 2 (TAB 3): CI [ 11.988263] ddbridge 0000:04:00.0: Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE [ 12.520907] ddbridge 0000:05:00.0: Port 0: Link 0, Link Port 0 (TAB 1): NO MODULE [ 12.522665] ddbridge 0000:05:00.0: Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-C/T [ 12.524430] ddbridge 0000:05:00.0: Port 2: Link 0, Link Port 2 (TAB 3): DUAL DVB-C/T [ 12.525408] ddbridge 0000:05:00.0: Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE [ 13.811309] ddbridge 0000:07:00.0: Port 0: Link 0, Link Port 0 (TAB 1): CI [ 13.812209] ddbridge 0000:07:00.0: Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 [ 13.813207] ddbridge 0000:07:00.0: Port 2: Link 0, Link Port 2 (TAB 3): CI [ 13.814401] ddbridge 0000:07:00.0: Port 3: Link 0, Link Port 3 (TAB 4): DUAL DVB-S2
RE: muxes - will not start - Added by Thomas Schmidt over 4 years ago
Holy...
I just installed the new driver 0.9.37. I assumed, that the support for kernel 5.4 and newer is implemented. The driver 0.9.36 didn't work and I was told, that I had to use another branch until 'the new driver is realesed'. For me 0.9.37 was this 'new driver'.
Once again, thank you @saen acro!
RE: muxes - will not start - Added by saen acro over 4 years ago
Put floppy cable to card.
Also see if flat cable from tuner to bridge is connected corectly.
It's important to say some information about hardware in feature, fortune teller with crystal ball is on vacation.
RE: muxes - will not start - Added by Thomas Schmidt over 4 years ago
Everything is up and running. Installed the driver from other branch and services are found.
Right now, there are 299 services, should be over 500... I will have a look at the muxes. Using the preconfigured (Unitymedia) ones.
Hardware is DD Max M4 and Octopus CI with Alphacrypt Light module.
1 - TV-Adapter.png (74.9 KB) 1 - TV-Adapter.png |
RE: muxes - will not start - Added by saen acro over 4 years ago
Thomas Schmidt wrote:
Right now, there are 299 services, should be over 500... I will have a look at the muxes. Using the preconfigured (Unitymedia) ones.
Forget about preconfigured, they are outdated, try network scan or manually set frequency's.