(2015-04-26, 00:04)fritsch Wrote: Suspend modes not working? Read: http://forum.kodi.tv/showthread.php?tid=165707&pid=1990182#pid1990182 carefully

(2015-04-25, 23:37)fritsch Wrote: 15.04 needs wsnipex ppa to get libva-driver-intel 1.5.1 - besides that, it runs fine.

(2015-04-26, 00:50)mattlach Wrote:

(2015-04-25, 23:37)fritsch Wrote: 15.04 needs wsnipex ppa to get libva-driver-intel 1.5.1 - besides that, it runs fine.

Ahh. Odd.

I had wsnipex ppa added, but still I was having the same vainfo output as a base install, but the version said 1.5.1pre1 or something like that (I have already zapped the partition.

Either way, I prefer being on an LTS. They tend to be more solid, and I won't be forced to do this all over again in 9 months :p

So I have restarted a 14.04 install. I went with the 4.0.0 vanilla kernel, hoping it will turn out OK.

Thank you very much for all your help, btw. You are quite possibly the most helpful developer in user forums I have ever come across!

Thanks for putting up with mine (and everyone else's) sometimes stupid questions

(2014-08-24, 14:53)fritsch Wrote:

Code:

fritsch@t440s:~$ vainfo
libva info: VA-API version 0.35.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.35 (libva 1.3.2.pre1)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 1.3.3.pre1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :    VAEntrypointVLD
      VAProfileMPEG2Simple            :    VAEntrypointEncSlice
      VAProfileMPEG2Main              :    VAEntrypointVLD
      VAProfileMPEG2Main              :    VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointEncSlice
      VAProfileH264Main               :    VAEntrypointVLD
      VAProfileH264Main               :    VAEntrypointEncSlice
      VAProfileH264High               :    VAEntrypointVLD
      VAProfileH264High               :    VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :    VAEntrypointVLD
      VAProfileH264MultiviewHigh      :    VAEntrypointEncSlice
      VAProfileH264StereoHigh         :    VAEntrypointVLD
      VAProfileH264StereoHigh         :    VAEntrypointEncSlice
      VAProfileVC1Simple              :    VAEntrypointVLD
      VAProfileVC1Main                :    VAEntrypointVLD
      VAProfileVC1Advanced            :    VAEntrypointVLD
      VAProfileNone                   :    VAEntrypointVideoProc
      VAProfileJPEGBaseline           :    VAEntrypointVLD
      VAProfileH264MultiviewHigh      :    VAEntrypointVLD
      VAProfileH264MultiviewHigh      :    VAEntrypointEncSlice
      VAProfileH264StereoHigh         :    VAEntrypointVLD
      VAProfileH264StereoHigh         :    VAEntrypointEncSlice

(2015-04-25, 09:21)fritsch Wrote: If you upgrade, you need to remove consolekit, pm-utils, upower

(2015-04-26, 09:17)fritsch Wrote: This thread is fully _not_ about Unity. It is about a minimal howto. If you want to start kodi from lightdm - every manual package installation hints does _not_ apply. Just install vaapi drivers and apt-get install kodi, then select it from lightdm.

(2015-04-26, 21:17)fritsch Wrote: No. This thread is about my howto I gave on the very first thread, which is about running standalone kodi. I basically don't care about DRM broken by design content, which netflix is.

Vaapi 1.5.0 has a bug when stopping playback which was fixed in 1.5.1.

(2015-04-25, 09:21)fritsch Wrote: Some changes, that are needed for Ubuntu 15.04, I did with daniel3 on irc yesterday:

Basic Software:

Code:

sudo apt-get update
sudo apt-get install ssh python-software-properties software-properties-common udisks xorg alsa-utils mesa-utils git-core librtmp1 lirc libmad0 lm-sensors libmpeg2-4 avahi-daemon libnfs4 libva1 vainfo libva-intel-vaapi-driver linux-firmware dbus-x11
sudo apt-get dist-upgrade

Changes:
Removed consolekit, pm-utils, upower
Name changed: libnfs4 librtmp1
New: dbus-x11

Wsnipex vaapi ppa is still needed(!), cause Vivid only ships libva 1.5.0

Policykit change (/etc/polkit-1/localauthority/50-local.d/custom-actions.pkla):

Code:

[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.udisks.*;org.freedesktop.login1.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Untrusted Upgrade]
Identity=unix-user:kodi
Action=org.debian.apt.upgrade-packages;org.debian.apt.update-cache
ResultAny=yes
ResultInactive=yes
ResultActive=yes

Changes: only freedesktop.login1 and udisks permissions are left. If you upgrade, you need to remove consolekit, pm-utils, upower

Now, we need a simple systemd upstart script (this one actively waits on network connection, see: network-online.target remove that if you don't need to wait)
Put it to: /etc/systemd/system/kodi.service

Code:

[Unit]
Description = kodi-standalone using xinit
After = systemd-user-sessions.service network.target sound.target network-online.target

[Service]
User = kodi
Group = kodi
Type = simple
PAMName=login
ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
Restart = on-abort

[Install]
WantedBy = multi-user.target

Fake display-manager.service to not make plymouth or something else complain.

Code:

sudo ln -s /etc/systemd/system/kodi.service /etc/systemd/system/display-manager.service

Something else: if you plan to install a 4.0 kernel - the network interface name changes again, back from e.g. p3p1 to eth0 - the boot will timeout after 2 minutes. You can have a look in /sys/class/net to find the new device name. This is no issue on Vivid as it ships 3.19.5

For standard users no kernel upgrade is needed anymore

Edit: Because of the /etc/security/limits.conf and cause of the fact systemd is modpam aware, no nice level needs to be specified.

(2015-04-27, 09:44)wsnipex Wrote: you can't run xrandr prior to starting X. Try ExecStartPost or use an autoexec.py from kodi.

Quote:Do you have any thoughts on what a good desktop to run Kodi on top of might be, or are you only willing to discuss running it as a session?