Posts by gert

    Thanks for that, and for your patch ;)

    Option 3 is the easy way out, but until the patch makes it to the Raspbian Kernel, I'm stuck with a non-working device. Who know how long I'll have to wait...

    Previously, my DVBSky adapters were attached to a VM running Debian.

    AFAIK the kernel I was using there doesn't include the DVSKy drivers, so I had to built my own drivers.

    So, I should be able to get option 2 working.

    I hadn't noticed yet that the patch made it to the media tree.

    The Raspberry does kernel include the drivers. Wil the driver that I build myself overrule the supplied one?

    I suppose it will ...

    Option 1 sounds more scary, as I haven't done anything like that before. But, I am willing to give it a try. Probably this is the option where I can learn the most :)

    Since I have 3 rpi + dvbsky, I think I'll fix 2 of them with new drivers and use the 3rd one to experiment with the kernel.

    Incorrect. The problem occurs on my Generic x86_64 HTPC (Acer Revo 3700). I have the DVBSky S960. I am currently using the Generic v4.8 kernel builds supplied by smp earlier in this thread and this resolves the problem.

    That's fascinating, since I am using exactly the same DVB equipment: DVBSky S960.

    As far as I'm concerned:

    * RPI2 + DVBSky S960 -> no problems with 4.4 or 4.8, problems with 4.9

    * 2x Linux VM Debian 9 + DVBSky S960 -> -> no problems

    * 2x Linux VM Debian 9 + Terratec H7 -> no problems

    * 1x Linux VM Debian 8 + TBS5980 QBox -> no problems

    The kernel for Debian 9 =

    [email protected]:/home/gert# uname -a

    Linux caladan 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux

    and for Debian 8 =

    [email protected]:/home/gert# uname -a

    Linux jed 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux

    For both the DVBSky and the Terratec I have 2 of them. Each time that's 1 VM that has been upgraded from Debian 8 to 9, and 1 freshly installed with 9.

    I have never had any problems on any of my Virtual Machines.

    We need someone who can reproduce the issue on a PC and a good linux skills. Otherwise this will never be fixed.

    Building images with downgraded kernel becoming less useful, especially for Rpi2/3.

    As far as I can tell, this problem only exists on RPi, not on "regular" Linux?

    I have several Virtual Machines with Linux (Debian 8 and Debian 9) and no such problems there.

    2 of those use exactly the same DVB-adapter as my RPi.

    UPDATE 1: The reverted 4.8-kernel also works as expected: 2 recordings, 0 errors.

    UPDATE 2:

    1. [email protected]:~ $ uname -a
    2. Linux thuban 4.8.13-v7+ #937 SMP Fri Dec 9 17:45:13 GMT 2016 armv7l GNU/Linux
    3. [email protected]:~ $ sudo rpi-update bcc6146e102d85b1aa214855ad7aae278d3bd269
    4. [email protected]:~ $ sudo reboot
    5. [email protected]:~ $ uname -a
    6. Linux thuban 4.9.0-v7+ #939 SMP Thu Dec 15 18:07:48 GMT 2016 armv7l GNU/Linux

    And now the errors are back.

    I think my situation is clear: There's nothing wrong with my hardware or config, just something weird in the 4.9 kernel.

    This is also another confirmation that the problem is not in Kodi or LibreElec.

    I can confirm everything works at it should with the RPi with kernel 4.4 (original Raspbian)

    Next test: I have connected the DVBSky to the other RPi (with kernel reverted to 4.8) and have scheduled some recordings on it.

    Results will be in tomorrow around noon. It's past midnight here, and I have to call it a day (night) for now.

    Alright :)

    I just wanted to clarify what I did (and did not) to get to 4.9 since there seemed to be some confusion how I (and someone else) got there.

    I'll get back here in a few hours with some results of the tests on one or both of my RPIs.

    If you want to narrow this down, can you back up your sdcard and try reverting the kernel.

    Sure, no problem.

    No need to backup the card though. I am preparing a second RPi which I was planning to use anyway.

    I now have 2 RPIs which I can use for testing:

    * one is the original one, with kernel 4.9, and the continuity errors.

    * another one with a fresh raspbian image, currently at kernel 4.4

    The first one is the one with the continuity errors. It is not currently connected to the DVB-adapter but it is still on my network, so I can already prepare it:

    1. [email protected]:/usr/local/etc $ uname -a
    2. Linux thuban 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux
    3. [email protected]:/usr/local/etc $ sudo apt-get install rpi-update
    4. [email protected]:/usr/local/etc $ sudo rpi-update 7a47836821b92efa569500b3382b1812082e42d3
    5. [email protected]:/usr/local/etc $ sudo reboot
    6. [email protected]:~ $ uname -a
    7. Linux thuban 4.8.13-v7+ #937 SMP Fri Dec 9 17:45:13 GMT 2016 armv7l GNU/Linux

    The TVHeadend install and config is still intact, so when I am back home and connect the DVBSky to it, I can start testing right away.

    The second one is a new install, which I planned to keep at 4.4 or 4.8

    That one is currently connected to the DVBSky. I was hoping to get the install of TVHeadend done during the breaks at workand have it up-and-running when I got home.

    That would give me a second chance of testing.

    Currently the kernel is still at 4.4

    1. [email protected]:~ $ uname -a
    2. Linux raspberrypi 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux

    I did not use rpi-update to update the kernel to 4.9, since I didn't even known that command before I read it here.

    I am fairly certain I just did apt-get update && apt-get upgrade (or maybe: apt-get dist-upgrade)

    I'll first check if I can make realiable recordings on both RPIs in the state they are in now (one reverted to 4.8, the other at 4.4) and then upgrade both to 4.9 to see what happens?

    Thank you for this interesting topic.

    I don't have any issues on my LibreElec system (still an older build, on a Intel x86-64 PC), but I have similar problems on one of my Raspberry Pi systems.

    I have a RPi2 installed with Raspbian Lite (CLI only), running TVHeadend (compiled form source) and using a DVBSky S960 as DVB-adapter.

    I use this setup only to record programs (on my NAS) and watch them afterwards on my TV or on the LibreElec system.

    Hence no need for LibreElec or Kodi or ... on my RPi2.

    The RPi2 has worked flawlessly for about 2 years, until it suddenly began to produce Continuity Counter Errors.

    To try and solve this, I tried the following things to no avail:

    * upgrade TVHeadend to the latest build
    * replace the RPi2 with another RPi2

    * replace the SD card and reinstall everything from scratch (re-downloaded raspbian image etc...)

    * swap the DVBSky S960 with an identical S960

    * replace the USB cable

    After reading this topic, I checked my RPi2 kernel and:

    [email protected]:~ $ uname -a

    Linux thuban 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux

    So, I think I have the same issues, but even though I have a Linux 4.9 kernel and a DVBSky S960, I do not have LibreElec on this machine.

    Like someone else mentioned before, the Raspbian kernel is 4.4, yet mine is 4.9.24

    I do not recall upgrading the kernel on purpose, but it is possible it got upgraded during my install procedure.

    I do not have my notes at hand (at work), but I will try from scratch again with a vanilla Raspbian image and go from there.
    I have a good hope that staying away from 4.9 will solve my problem.

    I also hope this can help you to locate your problems, since mine has nothing to do with LibreElec itself but seems very similar if not the same.


    My other recording machines are Debian VMs on my ESXi-server in the basement. Since they all use an older kernel, they don't have this issue.

    (And that's where I got the other DVBSky adapter)

    [email protected]:~$ uname -a

    Linux dziban 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux