https://bugs.kde.org/show_bug.cgi?id=381828
Mauro Carvalho Chehab <mchehab+...@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
(In reply to Tuxo from comment #4)
> Hello Mauro, turns out it's my DVB-T usb Dongle, a "DigitalRise DVB-T USB
> 2.0 Ter Beetle " - this one still has some unfixed issues in kernel 4.9 (the
> kernel debian/stable uses).
Kernel 4.9 had an important change, meant to improve security that badly
affected USB drivers. Yet, if the device is tuning, the required bug fixes
should already have been backported. The vp7045 driver is really simple: all it
does is to send commands to the device's internal firmware, with is responsible
internally to talk with the frontend. So, it is up to the firmware to tune.
So, what I suspect is that just increasing the timeout should be enough to make
it work with such device.
> It seems to affect the quick tuning. I'm testing
> now with a Hauppauge WinTV HVR-900H dongle and the issues are all gone.
OK, that confirms that this isn't a Kaffeine issue.
> Switching off vdpau with VDPAU_DRIVER=none is a good idea anyway, my older
> asrock mainboard can't deinterlace mpeg-2 in hardware, it has to happen in
> software. Increasing the tuning timeout to 4500ms (3x) for the Beetle device
> did not help.
Well, from its driver, it internally uses a Zarlink MT352 tuner, with is a very
old frontend. Perhaps it doesn't lock well on channels with higher throughput,
or perhaps the hardware is showing its age ;)
>
> Please close this ticket, the problem is hardware related ...
OK, thanks for checking.
--
You are receiving this mail because:
You are watching all bug changes.
