Login at Kodi Home

thwaller · (This post was last modified: 2017-02-24, 11:15 by thwaller.)

hmmm, thanks. My driver version looks nothing like that. It appears though that it is for the i965 whereas I have i915... which we all know already is old and outdated. I will see if there is compatibility there. I know my graphics will not run v17 well just to to its age, but maybe this can help with v16.1.

Thanks for the info.

UPDATE: when I try to install "i965-va-driver", it tells me...
"i965-va-driver is already the newest version (1.7.3-1)." Although vainfo did not confirm that, it appears it is installed.

**fritsch** · 2017-02-24, 12:36

What does vainfo say?

thwaller · (This post was last modified: 2017-02-24, 13:02 by thwaller.)

:~$ vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

I believe it may be due my graphics chip not supporting VAAPI.

spci -vnn

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01bd]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at eff00000 (32-bit, non-prefetchable) [size=512K]
I/O ports at eff8 [size=8]
Memory at d0000000 (32-bit, prefetchable) [size=256M]
Memory at efec0000 (32-bit, non-prefetchable) [size=256K]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel driver in use: i915
Kernel modules: i915, intelfb

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01bd]
Flags: bus master, fast devsel, latency 0
Memory at eff80000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2

**fritsch** · 2017-02-24, 13:02

Why not posting a Debug Log? And I could tell you right away. This here goes forwards, backwards and so on ...

Believes are something for church!

thwaller · (This post was last modified: 2017-02-24, 13:19 by thwaller.)

Sure, you want an entire log or just a portion of it?

http://pastebin.com/zNDPu88v

**fritsch** · 2017-02-24, 13:30

That's not even our kodi - yeah. But never the less. Jarvis does not run there, too - without GL_VERSION hacks ...

Quote:05:11:26 T:139673614089088 NOTICE: GL_RENDERER = Mesa DRI Intel® 945GM
05:11:26 T:139673614089088 NOTICE: GL_VERSION = 1.4 Mesa 13.0.2

thwaller · (This post was last modified: 2017-02-24, 14:01 by thwaller.)

Could you clarify... not even our kodi? I installed from either software center or package manager after the upgrade to 17 failed. It was the only way that worked to get back to v16.1 which works just fine as-is. I did a few other debs, but do you have a link to a deb for 16.1 for "your" kodi? And yes, I am aware as you pointed out earlier that the graphics are old on this setup causing issues with v17.

GL_VERSION hacks... I assume you mean what you had specified earlier in this post?
So, try if CPU only helps:
Code:
LIBGL_ALWAYS_INDIRECT=1 kodi

XOR the other way round:
Code:
MESA_GL_VERSION_OVERRIDE=3.0 kodi

**wsnipex** · 2017-02-24, 14:37

Starting Kodi from Debian (16.1 Debian package version: 16.1+dfsg1-2).

this is a debianized(patched) kodi, which we don't support

thwaller · 2017-02-25, 02:30

"this is a debianized(patched) kodi, which we don't support"
I understand. I was asking now if you have a method I can install Kodi from you, that is not patched. I did not realize there was a difference, I just selected it to install when the upgrade from the repository added v17 and killed everything. That was the only way I could fix it, the repository kept installing v17, I needed v16.1. I am more than happy to install what you support as I never intended not to. Hope you understand.

**wsnipex** · (This post was last modified: 2017-02-25, 07:04 by wsnipex.)

on debian you'd have to compile from source, since we only provide official builds for ubuntu.

edit: disregard, you are using ubuntu.
so simply add our PPA(see my sig)

thwaller · (This post was last modified: 2017-02-25, 07:16 by thwaller.)

No problem. Yes, I am using Ubuntu. I will try the PPA again... last time all it did is keep pushing v17 to me. If I can get on your build for v16.1, that would be nice. I would prefer to use your product without modifications as modifications can cause weird issues. Thanks!

edit:
apt-cache does not show v16.1 as available, just v17.

**wsnipex** · 2017-02-25, 07:16

what is the problem with v17?

v16 can still be found in https://launchpad.net/~team-xbmc/+archiv...u/kodi-old

thwaller · 2017-02-25, 07:22

The problem with v17 is it does not run good at all on this system. I posted the issue at the first post on this thread. I would have no issue using v17, but it won't work for me due to old hardware. I have no issues with v16.1 or other softwares like VLC and can view HD at 1080 without any issues, it is just Kodi v17 that gives the issue. fritsch has already explained that Kodi is designed to work only with the latest and best graphics chips, software and drivers. My setup runs all I need like InDesign, Illustrator, Kodi (at v16), photo editing, etc. Unfortunately, it does not make sense to upgrade only to use Kodi v17 when I can do everything just fine as long as Kodi v17 is not the software.

I will use the reference you provided. By looking at it, that is exactly what I need. Thanks Smile

I will do that install now.

thwaller · (This post was last modified: 2017-02-25, 07:59 by thwaller.)

Well, that was a bit of a mess, but it is all worked out. I do not mean your files, I mean getting rid of what was here and replacing with yours.

I am now looking at this, could you kindly confirm that this is correct for the most recent non-v17 release?
23:54:13 T:140308835016768 NOTICE: Starting Kodi (16.1 Git:c327c53). Platform: Linux x86 64-bit
23:54:13 T:140308835016768 NOTICE: Using Release Kodi x64 build
23:54:13 T:140308835016768 NOTICE: Kodi compiled Apr 25 2016 by GCC 5.3.1 for Linux x86 64-bit version 4.4.6 (263174)
23:54:13 T:140308835016768 NOTICE: Running on Ubuntu 16.10, kernel: Linux x86 64-bit version 4.8.0-39-generic
23:54:13 T:140308835016768 NOTICE: FFmpeg statically linked, version: 2.8.6-kodi-2.8.6-Jarvis-16.0

And if you do not mind, is there a fix for this:
23:54:20 T:140308835016768 ERROR: Unable to load libcec.so.3.0, reason: libcec.so.3.0: cannot open shared object file: No such file or directory
23:54:20 T:140308835016768 ERROR: Initialise - failed to initialise bus cec

**wsnipex** · 2017-02-25, 08:17

yes, this is our v16 build.
libcec 3 was never built for ubuntu 16.10, so there is no easy solution for that. If you don't need cec just ignore it.
Otherwise you'd have to compile it