Tvheadend

stable-4.2 is based on release-4.2. It just contains fixes for issues between releases.

Hmmm…so probably release 4.2.4. will not “cure” my problem/bug, I posted in this thread:

[[https://forum.kodi.tv/showthread.php?tid=322803]]

Jef Bosk wrote:

Hmmm…so probably release 4.2.4. will not “cure” my problem/bug, I posted in this thread:

[[https://forum.kodi.tv/showthread.php?tid=322803]]

Do you still have this broken config by any chance?

No, I don't...do you want me to do something and report here if it happens again?
Could take some days, but I sure would. I believe it will happen again when I set up tvheadend again.
Waiting for instructions...

Jef Bosk wrote:

No, I don't...do you want me to do something and report here if it happens again?
Could take some days, but I sure would. I believe it will happen again when I set up tvheadend again.
Waiting for instructions...

If it happens again, open an issue (or post here) & attach any logs (cleaned of passwords/private info).

Hi Guys, it just happened again!! :(( Now the whole TV Inputs section is wiped out. Silly question...where do I find the log files under UBUNTU 16 for posting them here? Couldn't find any under /var/log/

What file should I look for and where??

Meanwhile I upload 3 screen-shots showing the config before and after the problem!!

This sounds like your tuners aren't ready when Tvheadend starts. You can tell this by restarting the tvh service - sudo service tvheadend restart - when there are no adaptors present, the restart will cause tvh to try and detect them again.

- edit - I goofed!

Attach DMESG with and without tuners.
Is tuners are TBS?

sudo service tvheadend restart doesn't help

The tuner is a Digital Devices CINE S2 v7.

lspci shows the "Multimedia controller: Digital Devices GmbH Cine V7"

Is this the dmesg output you wanted? Sorry I am not really Linux experienced

This output is without tuners
what is OS and kernel
is https://github.com/DigitalDevices/dddvb used?

saen acro wrote:

This output is without tuners
what is OS and kernel
is https://github.com/DigitalDevices/dddvb used?

This really sounds like kernel updates are wiping out the drivers - just like what happens on TBS cards!

I have installed the driver following this instructions:

[[http://support.digital-devices.eu/knowledgebase.php?article=151&language=English]]

and according to the given terminal commands, I installed dddvb release 0.9.32.

The output of cat /proc/version_signature is:

Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17

While waiting for your replies guys, I re-installed the dddvb driver and now the dvb inputs are back again, the TV in Kodi is also back, however the new output of dmesg | grep dvb is weird

[ 12.816283] dvb_core: loading out-of-tree module taints kernel.
[ 12.816378] dvb_core: module verification failed: signature and/or required key missing - tainting kernel

what the hell is going on?

Just a guess, but it looks like updates to the kernel (including auto-updates) is clearing the driver. You need to stop ubuntu from auto updating.

hmmm...turning off automatic updates shouldn't be the first option...UBUNTU updates usually make sense

On the other hand, if each kernel update wipes out the TV tuner drivers, since I switched to 16.04 I have had more than one kernel update... every time I would need to reinstall the tv tuner? This would be bloody ridiculous, wouldn't it?!

Let's wait for the reply of Digital Devices' support team....

Jef Bosk wrote:

hmmm...turning off automatic updates shouldn't be the first option...UBUNTU updates usually make sense ;)

They do make sense. But if you're using out-of-kernel drivers supplied by the manufacturer they need to be built and reinstalled on kernel upgrade.

On the other hand, if each kernel update wipes out the TV tuner drivers, since I switched to 16.04 I have had more than one kernel update... every time I would need to reinstall the tv tuner? This would be bloody ridiculous, wouldn't it?!

Let's wait for the reply of Digital Devices' support team....

Yes it is silly, but you can thank the manufacturer for not open-sourcing their drivers or offering DKMS drivers (sundtek devices do I believe). Non-OS drivers are usually the result of NDAs etc.

TBS are in the same boat, but thankfully they appear to be turning that around slowly.

Jef Bosk wrote:

While waiting for your replies guys, I re-installed the dddvb driver and now the dvb inputs are back again, the TV in Kodi is also back, however the new output of dmesg | grep dvb is weird

[ 12.816283] dvb_core: loading out-of-tree module taints kernel.
[ 12.816378] dvb_core: module verification failed: signature and/or required key missing - tainting kernel

what the hell is going on?

not signed modules there is not script for signing them, included in repo
very problematic in uefi systems
I send 2 month ago ticket to DD and no solution.

I have the reply from the very friendly and, so far IMO, very professional Digital Devices support...

The weird output of dmesg | grep dvb I posted:

[ 12.816283] dvb_core: loading out-of-tree module taints kernel.
[ 12.816378] dvb_core: module verification failed: signature and/or required key missing - tainting kernel

can be ignored, as it basically says that the driver is not deriving from the kernel and therefore it has not an "authenticated signature".

Additionally, the DD support informs me, that standby or hibernation under Linux is still quite "a pain in the ass". DD definitely recommends, before the PC enters standby or hibernation. to:

- stop tvheadend
- unload the tv tuner drivers
and after resume
- first load the drivers
- then start tvheadend

I will look for a script somewhere.

And regarding the kernel updates wiping the driver, yes, DD support confirmed this behaviour. As I now learned, DD does not provide any driver in DKMS packages who automatically build a new driver into the kernel once the kernel is updated. What I did not know before is that, contrarily to a windows "setup.exe", the "make install" command builds the drivers into the kernel which (of course) are wiped out once a new kernel is installed. Actually, I learned they are not wiped out, they are just chained into the previous kernel. I will now also have to look for a tutorial for how to build my dkms package with the latest DD driver. Alternatively, I could wait for kernel 4.14 as the support "revealed", the driver might be included in that ubuntu kernel onwards, but I would probably need to wait for ubuntu 18 lts

By the way, coming back to the original title of the theme (even if by now the subject should be changed to "TV Tuner and drivers gone after restart or resume" I can post myself a reply, yes, with the terminal command:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
echo "deb https://dl.bintray.com/tvheadend/deb xenial stable-4.2" | sudo tee -a /etc/apt/sources.list

I also achieved that tvheadend updated automatically, as the last update upgraded my tvheadend to version 4.24.

Cheers

This is why I try to avoid hardware that isn't mainlined!