Posts by smp

I found a workaround for the mutex issue. It seem to be impossible to revert commit 9d659ae14b545c4296e812c70493bfdc999b5c1c in kernel 4.19, so here's a solution:

diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index 3f8a351..5878d8f 100644
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -59,7 +59,7 @@ EXPORT_SYMBOL(__mutex_init);
  * Bit2 indicates handoff has been done and we're waiting for pickup.
  */
 #define MUTEX_FLAG_WAITERS    0x01
-#define MUTEX_FLAG_HANDOFF    0x02
+#define MUTEX_FLAG_HANDOFF    0x00
 #define MUTEX_FLAG_PICKUP    0x04
 
 #define MUTEX_FLAGS        0x07

After applying this patch the random tuner failures are gone. Tested with DVBSky S960, kernel 4.19.7.

What is your gpu_mem setting?

Kernel 4.19.2 did not solve the problem described in the original post, I can still easily reproduce it. In 4.19.2/4.20-rc2 they reverted commit 7d95fb74 that made DVBsky devices non-functional since kernel 4.18 but that issue is completely unrelated.

Use WinSCP.

Copy /usr/share/kodi/addons/skin.estuary folder to /storage/.kodi/addons/

Edit the xml file (/storage/.kodi/addons/skin.estuary/xml/DialogSeekBar.xml).

Restart Kodi.

Quote from gent

Is this possible?

Yes. If you are using the default Estuary skin you will need to edit addons/skin.estuary/xml/DialogSeekBar.xml file.

<visible>Player.Seeking | Player.DisplayAfterSeek | [Player.Paused + !Player.Caching] | Player.Forwarding | Player.Rewinding | Player.ShowInfo | Window.IsActive(videoosd) | Window.IsActive(musicosd) | Window.IsActive(playerprocessinfo) | !String.IsEmpty(Player.SeekNumeric) | !String.IsEmpty(PVR.ChannelNumberInput)</visible>

Remove Player.DisplayAfterSeek | [Player.Paused + !Player.Caching].

Revert "media: dvbsky: use just one mutex for serializing device R/W … · torvalds/linux@9afc821 · GitHub

"This patch causes a bad effect on RPi. I suspect that the root cause is at the USB out of tree RPi driver, with uses high priority interrupts instead of normal ones. Anyway, as this patch is mostly a cleanup, better to revert it."

Actually, it broke it for all platforms including x86,

There is a buggy commit in dvbsky.c driver in kernel 4.18. It should be reverted to make DVBSky devices work again.

It is unwatchable here too. Kodi falls back to software decode but Rpi3 is not fast enough to decode this in software.

Quote

Bit depth : 10 bits

Rpi does not hardware decode 10-bit video. You can still PM me the sample file so I will test it on my Pi.

Kernel issue that was causing DVB stream corruption was fixed months ago.

DVBsky devices do have an unresolved issue with new kernels as described in this thread but this has nothing to do with continuity errors in tvh.

Quote from gurabli

What would you recommend?

Did it ever work without errors? Check if you have a good signal. Try a clean LE installation without any unnecessary addons. Make sure that there are no background processes that could interfere with the DVB stream.

Quote from jahutchi

Does the attached patch to revert this change for the m88ds3103 driver have any effect ?

No, same issue.

I didn't check dmesg. It failed like it always did with newer kernels - it works for a while but a brief signal disruption randomly triggers the failure. I'm now back to kernel 4.8.16 for everyday use.

Sadly, that patch didn't fix the issue. I was able to quickly reproduce it by disconnecting the antenna cable for 10 minutes and trying to tune to a bunch of transponders (when the cable was disconnected). When I reconnected the cable the device was unable to lock the transponders anymore until a reboot.

Quote from jahutchi

I've just posted a proposed patch here: 199323 – DVBSky USB TV tuners do not work since 4.10 due to mutex issues

Would be useful to know whether this resolves the issue.

I will test it with kernel 4.19.

Quote from kimbaz

I just got this information from the media info during the playback:

MediaInfo download | SourceForge.net

Try to increase the config_hdmi_b o o s t parameter in config.txt (the word b o o s t is censored on this forum for some reason, so no spaces)

You will probably need a drive with an RPC1 firmware.

Also, Kodi is not a great solution for DVD playback, especially on RPi (issues with menus, etc). Any standalone player will do a much better job.

Use the Whitelist (System-->Display-->Whitelist)