Login at Kodi Home

**fritsch** · 2015-09-27, 16:30

Nope - it's not broken. If you use Sync Playback to Display - Passthrough is automatically disabled ... to care for users not reading.

zoing · 2015-09-27, 16:37

(2015-09-27, 16:26)sunnyfunny Wrote: Hi Fritsch,

looks like passthrough is broken after Version of 22th September (Jarvis). With all newer Version i only get 5.1 PCM output. I will create a log later.

Did you disable "sync playback to display" ?

zoing · 2015-09-27, 16:52

(2015-09-27, 15:28)gurabli Wrote: OK. I still struggle with some settings. Maybe it is because I have a 720p display? Or if I turn off tv and leave for a while, and turn it on again, then something is not detected properly? Kodi is always running. I thought I managed to fix this by setting HDMI3 as default Monitor instead of Default in System Settings.

First set of logs when Kodi restarts:

http://paste.ubuntu.com/12590442/
http://paste.ubuntu.com/12590443/
http://paste.ubuntu.com/12590444/
http://paste.ubuntu.com/12590445/
http://paste.ubuntu.com/12590450/

And second set of logs when trying to play LiveTV, test pattern video, and getting fullscreen to work with entering into System Settings menu. By only entering there it works. And TV was also turned off, and turned back.

http://paste.ubuntu.com/12590558/
http://paste.ubuntu.com/12590561/
http://paste.ubuntu.com/12590562/
http://paste.ubuntu.com/12590564/
http://paste.ubuntu.com/12590567/

Any ideas?

It seems this is a bug in kernel drm driver. (https://bugs.freedesktop.org/show_bug.cgi?id=91629)
So you can install the latest kernel 4.3 for ubuntu (http://kernel.ubuntu.com/~kernel-ppa/mai...-unstable/). But be aware this kernel is still in development. Or you can check the Bios for an DVFS entry and enable it.

**fritsch** · 2015-09-27, 16:54

This is fixed in for example: http://fritsch.fruehberger.net/openelec/..._amd64.deb / http://fritsch.fruehberger.net/openelec/..._amd64.deb which I am running on my BSW.

gurabli · 2015-09-27, 17:26

I dont have any dvfs options in the bios. Will upgrade to kernel 4.3 once it is more stable.
Btw,how does this dvfs affects my system, Kodi?

**fritsch** · 2015-09-27, 17:28

The way you describe it, smarty?

zoing · 2015-09-27, 17:39

(2015-09-27, 17:26)gurabli Wrote: I dont have any dvfs options in the bios. Will upgrade to kernel 4.3 once it is more stable.
Btw,how does this dvfs affects my system, Kodi?

When you can playback video, music etc. there is no problem.

**fritsch** · 2015-09-27, 17:47

For me it happened most of the time when doing Refreshrate switching. I then went to #intel-gfx and asked the commiter of this patch about the issue. Yeah - they fixed it then :-) The other guy on the bugreport is Chris Wilson who is writing the intel drivers for xserver. So if that is fixed - everything will work out great :-)

gurabli · 2015-09-27, 18:23

(2015-09-27, 17:28)fritsch Wrote: The way you describe it, smarty?

?, what did I wrong?

**fritsch** · 2015-09-27, 18:25

Nothing - all fine. Sadly this patch is not that easy to be backported to a 4.1.x kernel ... so you can either try with the kernels I linked or with a mainline build of 4.3-rc.
On my system it only produced a "warning", but it was more sever on others ... so just try one of the two options and see if it gets better.

gurabli · 2015-09-27, 18:31

(2015-09-27, 18:25)fritsch Wrote: Nothing - all fine. Sadly this patch is not that easy to be backported to a 4.1.x kernel ... so you can either try with the kernels I linked or with a mainline build of 4.3-rc.
On my system it only produced a "warning", but it was more sever on others ... so just try one of the two options and see if it gets better.

So I probably have problems with limited and full range and refresh rate switching because of this dvfs problem?
I will try Kernel 4.3 RC latest. It is fixed there?

**fritsch** · 2015-09-27, 18:32

You try it, you tell us :-) Easy, isn't it? The DVFS problem is - yes.

**fritsch** · 2015-09-27, 18:33

Btw. don't confuse two things here. Whenever you poweroff the TV, it gets "disconnected" and intel looses the complete output. When you power it on again - the output device is reset to whatever is default. In such a case you need to rerun the full range command.

gurabli · 2015-09-27, 18:37

(2015-09-27, 18:33)fritsch Wrote: Btw. don't confuse two things here. Whenever you poweroff the TV, it gets "disconnected" and intel looses the complete output. When you power it on again - the output device is reset to whatever is default. In such a case you need to rerun the full range command.

This is what I wantwd to know. Is there a way to rerun set full rgb intel driver without restarting the system? Or in my case maybe it would be better to start Kodi with autostart set to limited instead of full? Does it make sense? As it looks the default is limited.

**fritsch** · 2015-09-27, 18:48

No it would not make sense ... see first post ... if you love double scaled colors ...

If you really cannot workaround this. Remove the xrandr command completely from the startup script (autostart) and keep Kodi on Full Range (enable Dithering to 8 bit). Then it won't harm "too much" as the driver will scale down again a dithered upscaled image ... i would not suggest this.

But you need more help with managing your system than with kodi ...