[mythtv-users] DVB-S2 IP tuner

[Stephen Worthington]

On Sat, 04 Jan 2020 18:26:29 +0000, you wrote:

>
> ---- On Sat, 04 Jan 2020 17:20:01 +0000 Stephen Worthington <stephen_agent at jsw.gen.nz> wrote ----
>
> > The kernel developers have a policy of not breaking existing devices.
> > So if a driver needs to be modified to keep working with later
> > kernels, the modification will be done.  Occasionally, something does
> > get broken in a new kernel, but if you report it, it should get fixed.
> > Especially if you are able to do a kernel bisection to find out
> > exactly which change caused the problem.
>
>
>looks like i might have to go through a bug report. just not sure who with.
>I went through compiling the TBS drivers manually from another suggestion in this thread but still no go. same symptoms where mythtv will report something along the lines of 'DiSEqC set FE Voltage error (5)' and a handful more similar DiSEqC errors, and dmesg reports failing firmware loading.
>These are identical issues with both the shipped Centos8 kernel (4.18 i think), and elrepo's kernel-ml 5.4.7 (which i believe elrepo are untainted images). 5.4.7 is the latest kernel so imo focus should be there.
>Centos7 comes with a 3.x so i need either to compile the TBS 6981 manually or use a later >=4.x kernel which is where i'm currently at; running elrepo 5.4.6 and it just works (once fw is placed in /lib/firmware).
>does seem specific to Centos8 regardless of what i do and that feels like the better angle to take the bug report to. guess there's no harm letting them decide how to handle and go from there.
>
>while i've installed centos8 to a usb3 hdd for testing, it's awkward finding a convenient time to boot to that env for further diags. mythtv is our primary system so evenings are typically off limits and WAF reduces at weekends when it's unavailable. at least she still has the Shield, Roku and tv-only broadcast signal.

Which TBS drivers are you compiling?  The older proprietary TBS code
does not seem to be being maintained on newer kernels for their older
tuners, so I would recommend trying the modified V4L drivers, which
are kept up to date with current kernels.  I posted the URL in my
previous post on this thread.  Is that the drivers you tried?