Kodi Community Forum
v17 debugging on Radeon OSS drivers - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: v17 debugging on Radeon OSS drivers (/showthread.php?tid=269200)



debugging on Radeon OSS drivers - locomot1f - 2016-04-14

Greetings,

Been trying to get Kodi 17 (Krypton) working properly on my Linux build.

Following the debugging methods used during the Radeon OSS w/ vdpau thread:

dmesg
http://paste.ubuntu.com/15822577/
cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/15822589/
cat /var/log/Xorg.0.log | pastebinit
http://paste.ubuntu.com/15822595/
DISPLAY=:0 vdpauinfo | pastebinit
http://paste.ubuntu.com/15822602/
dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/15822606/

just getting a lot of tearing;
here's my advancedsettings.xml
http://paste.ubuntu.com/15822622/


RE: debugging on Radeon OSS drivers - fritsch - 2016-04-14

Sadly not a kodi debug log. While at it: Use the default skin and remove those scripts that cause errors in your log


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-14

http://paste.ubuntu.com/15830746/

i hope this is a bit better.

i removed all my addons to give a more "fresh" look at the files.
so there should be no unusual scripts running to cause errors.

hope this helps. looking forward to any advice.


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-14

also,

If I leave the GUI on one screen (doesn't seem to matter which: Main, Settings, TV Shows, etc)
it will appear just fine after a few seconds. Then after about a minute of being on that screen, my screen goes black, until i try to navigate again.


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-14

hmmm..


using ppa:oibaf/graphics-drivers
seems to have helped.
not getting any tearing. video look good.
no drops or skips so far.

are there any drawbacks to keep this PPAHuh


RE: debugging on Radeon OSS drivers - wsnipex - 2016-04-15

Yes, its breaking regularly, since it contains blleeding edge code


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-15

anything I can do to help getting the new Krypton working without using this bleeding edge technology?


RE: debugging on Radeon OSS drivers - fritsch - 2016-04-15

If you want - verify with an Ubuntu 16.04 installation, cause we will drop for 14.04 soon.


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-16

okay, so I tried to upgrade to 16.04

everything seemed to go okay. using systemd
then when I tried to run Kodi, it failed.

reading the log -- http://paste.ubuntu.com/15870908/
i'm now getting errors saying "Can't Open Display"
when I run xrandr, i get "Can't Open Dislpay

then i read this -- http://www.omgubuntu.co.uk/2016/03/ubuntu-drops-amd-catalyst-fglrx-driver-16-04

am i missing something? i feel like i'm missing a package.


RE: debugging on Radeon OSS drivers - fritsch - 2016-04-16

Most likely: http://forum.kodi.tv/showthread.php?tid=231955&pid=2310818#pid2310818


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-16

yeah!!! :-D

thanks, @fritsch! that did it.

now, ?uestion number 2
it seems that with the changes xrandr is broken, and Kodi will not hold the changes I make to the resolution.
what options do I have to make this stick?
i'm doing the research. just didn't know if maybe you have run into this as well.

thanks again!


RE: debugging on Radeon OSS drivers - fritsch - 2016-04-16

What means "xrandr" is broken?


RE: debugging on Radeon OSS drivers - locomot1f - 2016-04-16

okay, broken is a bad choice of words.
https://launchpad.net/ubuntu/xenial/+source/xrandr

it seems to ignore my xrandr command, and always defaults back to the original settings.
still playing around with it.
but at least I have my TV back! :-D
----------------------------------------------------

nevermind... my kodi.service was pointing to the wrong file.

cheers! and thanks again.