Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04
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.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.


Messages In This Thread
EDID / HDMI Handshake workaround - by Ney - 2014-10-29, 13:58
Thank you! - by Sta11ion - 2015-01-02, 01:51
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - by fritsch - 2015-04-25, 09:21
Logout Mark Read Team Forum Stats Members Help
VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.0416