DVB issue since LE switched to kernel 4.9.x

  • okay next try Index of /Test/dvbskys960/


    1.1-1.3 there are still more than enough commits between :/ but somewhere we have to begin


    I tried all 3 builds. However, these builds don't work whatsoever since Xorg fails to start with the following error in the logfile Xorg log: Failed to load /usr/lib/xorg/modules/drivers/nvidia_drv.so: /usr/lib/xorg/modules/drivers/nvidia_drv.so: cannot open shared object file: No such file or directory


  • I tried all 3 builds. However, these builds don't work whatsoever since Xorg fails to start with the following error in the logfile Xorg log: Failed to load /usr/lib/xorg/modules/drivers/nvidia_drv.so: /usr/lib/xorg/modules/drivers/nvidia_drv.so: cannot open shared object file: No such file or directory


    damn ...
    yea build error from my side

  • Subscribing, as I have the same problem with Rpi2 + DVBSky S960 and Tvh. I will try the 8.0 eith 4.8 kernel, no media build, as it looks to me that is working for everybody.


    Sent from Tapatalk from my Z5 Compact

  • What differences for media build and no media build? Which should I try for raspberry 2 and tevii s660 dvbs2 card?


    Wysłane z mojego SM-G920F przy użyciu Tapatalka


  • Hey, with the latest MR release, will this bring about the same issues we have as still using same kernel?


    Official 8.0.1 RPi2 is still unusable for me. That's why I did a custom 8.0.1 with kernel 4.8.
    I can only test the RPi2 builds. No idea what's going on with Generic builds, you will have to test those yourself.

    Edited once, last by smp ().


  • Official 8.0.1 RPi2 is still unusable for me. That's why I did a custom 8.0.1 with kernel 4.8.
    I can only test the RPi2 builds. No idea what's going on with Generic builds, you will have to test those yourself.


    I've been using the generic build you supplied without media build and it's working perfect for me. I did try the official 8.0.1 release straight after it was released but the continuity counter errors returned. Hopefully someone will figure out what's been broken in the kernel that's being shipped with the official builds.

  • I just tried a kernel 4.11-rc4 build and it is just as bad as 4.9/4.10. Looks like we'll be stuck with kernel 4.8 for a long, long time.

    Edited once, last by smp ().

  • so revert 1 is not working, revert 2 is working so the problem is somewhere between


    okay going to build some images :)


    Is it worth picking this back up? smp has confirmed that the issue is still present in kernel 4.11-rc4 so looks like it's not been fixed upstream.


    I'm happy to do some more testing to help pinpoint the dodgy commit.

  • we need someone who has the hardware and can bisect the kernel commit btw at least test if the same problem appears at Ubuntu with >4.9

  • without hardware i can't bisect the problem, would be nice to know at least if the same happens at latest ubuntu with kernel 4.9 (if someone could test this)

  • I'm pretty sure that the issue is RPi-specific. For whatever reason it simply perform worse with kernels newer than 4.8.

    I did some testing on Celeron J1800 board and I don't see any issues with Generic builds with any kernel.

  • Thanks for this thread - I've been having trouble with my RPi 2 and DVBSky S960 since upgrading to LibreELEC 8.0 (green unwatchable mess on most channels, countless continuity errors in tvheadend), but smp's build without media_build seems to be working well for me (media_build was better than 4.9 kernel, but some channels were still bad or only occasionally worked).


    However, I'm not sure this problem is RPi-specific. I tried the same setup with my tuner on an x86 laptop (i5-3340M) running LibreELEC 8.0.1 (official build) and was having the exact same problem - it was essentially unusable with the constant continuity errors in TVH, as even the bouquet/mux scan was failing (UK Freesat channels). Let me know if you want me to try any further testing.