Problems with DVBSky / TechnoTrend USB DVB-S2 tuners since LE8

No problems, im really just an end user with a little programming experience trying to fix this issue. I have 3 of these devices, so have a vested interest. I'm currently sticking with kernel 4.9 cos of this problem. Really needs one of the upstream devs to fix this.

I'm currently using kernel 4.19.7 with the "MUTEX_FLAG_HANDOFF 0x00" hack on a Raspberry Pi3 and it works well. Kernels 4.8 and 4.9 also work fine.

smp - I managed to find a couple of days to debug the driver on a 4.19 kernel and develop a patch.

BTW: your hint of unplugging the antenna was extremely useful in debugging.

Any chance you could test the proposed patch I've just posted over on the bugzilla thread:

199323 – DVBSky USB TV tuners do not work since 4.10 due to mutex issues

jahutchi I tested your patch with kernel 4.19.14 and I can confirm that it fixed the issue. Thank you!

Quote from smp

jahutchi I tested your patch with kernel 4.19.14 and I can confirm that it fixed the issue. Thank you!

Great news, thanks for testing.

If u could also post to that effect on the bugzilla thread that'd be ideal; as i reference the bugzilla url in the patch i plan to submit to the upstream devs.

The patch is good to go from my pov, if LE maintainers are interested in including in their builds/media_tree packages.

Will be submitting it 'as-is' to the upstream devs early next week.

This is excellent news, finally the problem with S960 should be fixed. Looking forward to the beta release.

Btw, will it be included in the LE9 nightly builds?

A stupid question maybe, but how can I apply this patch?

I am currently running raspbian on a few RPI3B+ with a DVBSky S960 adapter.

pi@rpi31:~ $ sudo uname -a
Linux rpi31 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

As far as I know, the patch has not been applied in raspbian itself so far.

What do I have to do to apply it to my RPI myself?

Quote from gert

What do I have to do to apply it to my RPI myself?

A few choices:

1) Compile & install your own kernel from the raspbian sources, with my patch applied: Kernel building - Raspberry Pi Documentation

2) My patch found it's way into media_tree just a couple of days ago: media_tree.git - Upstream media tree for Remote Controllers, V4L and DVB so you could to build and install the drivers yourself from media_tree to run within your existing kernel: https://www.linuxtv.org/wiki/index.php/how_to_obtain,_build_and_install_v4l-dvb_device_drivers

3) (If both above options are too scary), then wait until the patch filters it's way down to mainstream raspbian kernel.

Quote from jahutchi

A few choices:

1) Compile & install your own kernel from the raspbian sources, with my patch applied: Kernel building - Raspberry Pi Documentation

2) My patch found it's way into media_tree just a couple of days ago: media_tree.git - Upstream media tree for Remote Controllers, V4L and DVB so you could to build and install the drivers yourself from media_tree to run within your existing kernel: https://www.linuxtv.org/wiki/index.php/how_to_obtain,_build_and_install_v4l-dvb_device_drivers

3) (If both above options are too scary), then wait until the patch filters it's way down to mainstream raspbian kernel.

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.

Hi folks,

I updated my TVHeadend system from a Raspberry 2 with Raspbian 8 to a Raspberry Pi 3+ with Raspbian 9 (Stock Kernel 4.14.98).

While everything worked with the old hardware/software combination, the 4.14.98 kernel has the problem discussed here.

Of the three possibilities mentioned above, I tried variant 2.

However, this fails: the newly built module is not loadable.

The error is: "dvb_usb_v2: Unknown symbol rc_register_device (err -22)".

However, there is a fourth way, which is quite simple:

I've updated the kernel to a new version with "rpi-update" - currently this is 4.19.37.

Now TVHeadend runs stable for some time. The bug discussed here usually occurred after a few minutes. Therefore I assume that this bug is fixed.

Note: rpi-update does not install kernel headers or resources.

If you want to build more modules for this kernel, you should note this here:

Home · notro/rpi-source Wiki · GitHub

It is enough to get the source with rpi-source and run a "make oldconfig && make prepare" to build the source for the new module.

I tried it yesterday with an Ubuntu Kernel 4.19.5x... (18.04 LTS) Still does not work. Will try to integrate the patch later today.

Patch was merged in 4.19.47

changelog-4.19.47