See FAQS PowerReqs.
We started with a Raspbian 2017-11-29 lite, based on Debian Stretch. To have a minimal Kodi installation and support for the joystick, just install the following packages:
Kodi will not start automatically at boot, just execute kodi-standalone from the command line.
NOTICE: Raspbian based on Debian Stretch 9.11 uses two repositories:
The first repository provides Kodi 17.1 as per Debian Stretch. The second repository provided Kodi version 17.6 on December 2017, but it was upgraded to Kodi version 18 on february 2019. So beware of what packages you are installing, respect the right dependencies and be carefull with upgrades.
Our current installation uses these versions:
| kodi | 2:17.6-2~stretch |
|---|---|
| kodi-bin | 2:17.6-2~stretch |
| kodi-eventclients-common | 2:18.1-1~stretch |
| kodi-eventclients-kodi-send | 2:18.1-1~stretch |
| kodi-peripheral-joystick | 1.3.4-1~stretch |
| libkodiplatform17:armhf | 17.4.0~stretch |
To activate a joypad you have to go through Settings ⇒ System settings ⇒ Input ⇒ Configure attacched controllers.
There are several recipes on the internet to start Kodi on boot; we searched one with the following features:
So we want to execute kodi-standalone as kodi user. Create that user first, and assign him to the required groups:
adduser --disabled-password --gecos "User to run Kodi Media Center" kodi adduser kodi audio adduser kodi video adduser kodi plugdev adduser kodi input
Then we created a systemd unit file /etc/systemd/system/kodi.service to start Kodi as a service. Please do not use an old fashioned sysvinit start/stop script (e.g. /etc/init.d/kodi), because the new systemd can use it only in compatibility mode.
[Unit] Description = Kodi Media Center # if you don't need the MySQL DB backend, this should be sufficient After = systemd-user-sessions.service network.target sound.target # if you need the MySQL DB backend, use this block instead of the previous # After = systemd-user-sessions.service network.target sound.target mysql.service # Wants = mysql.service [Service] User = kodi Group = kodi Type = simple ExecStart = /usr/bin/kodi-standalone Restart = always RestartSec = 15 [Install] WantedBy = multi-user.target
To actually enable and start the service, run:
systemctl daemon-reload systemctl enable kodi.service systemctl start kodi.service
Now we have to solve a problem: the unprivileged Kodi user cannot perform reboot and poweroff actions: as you can se the exit menu of Kodi shows only the Exit item. We need a piece of software: policykit-1. This package contains the framework which handles the authorizations, according to the Freedesktop.org guidelines.
apt-get install policykit-1
We created the file /etc/polkit-1/localauthority/50-local.d/50-kodi.pkla, which allows the Kodi user to execute some privileged actions:
[Actions for kodi user] Identity=unix-group:kodi Action=org.freedesktop.upower.*;org.freedesktop.udisks.*;org.freedesktop.login1* ResultActive=yes ResultAny=yes ResultInactive=no
We got a severe problem trying to play some .webm video files: the audio starts but it freeze shortly, the video does not start at all. After that, all the Kodi interface was frozen and we need to reboot (ssh access still working). Into kodi.log we get the following error:
CMMALVideo::Open Failed to commit format for decoder
input port vc.ril.video_decode:in:0(VP8 ) (status=3 EINVAL)
To confirm that the video codec is VP8, we installed the mediainfo package an run the tool against the video; which actually uses the VP8 codec. The official Kodi Wiki says that VP8 is supported on the Raspberry Pi architecture, so we are searching for the problem somewhere else.
This post says that VP8 hardware (GPU) decoding is supported only if firmware start_x.elf is loaded: Note that GPU accelerated software codecs (and camera) are only available from start_x.elf. Add start_x=1 to config.txt (or use raspi-config and enable camera). This means that we have to add the following line in /boot/config.txt (The required file is already in the /boot directory):
start_x=1
See also the page Boot options in config.txt. We have also gpu_mem=128 in the same config file.
We keep all our media files (video, images, etc.) into an USB hard disk, connected through a powered USB hub. It can be possible that the Raspberry Pi will be started without the disk attached. In this case we want no Kodi service to be started. See this paragrph on how to configure systemd unit for that purpose.
The first attempt was an Amazon Basics USB 3.0 4 ports hub. Unfortunately it is based on the VIA Labs chips, which seems to have a bug, so it is uncompatibile with the Raspberry Pi.
The device is listed on the USB bus:
Bus 001 Device 005: ID 2109:2811 VIA Labs, Inc. Hub
but when you connect even a simple mouse, you get plenty of errors, and the device does not work:
usb 1-1.4.1: new low-speed USB device number 6 using dwc_otg usb 1-1.4.1: device descriptor read/64, error -71 usb 1-1.4.1: device descriptor read/64, error -71 usb 1-1.4.1: new low-speed USB device number 7 using dwc_otg usb 1-1.4.1: device descriptor read/64, error -71 usb 1-1.4.1: device descriptor read/64, error -71 usb 1-1.4.1: new low-speed USB device number 8 using dwc_otg usb 1-1.4.1: device not accepting address 8, error -71 usb 1-1.4.1: new low-speed USB device number 9 using dwc_otg usb 1-1.4.1: device not accepting address 9, error -71 usb 1-1.4-port1: unable to enumerate USB device
I tried several workarounds: leaving the hub unpowered, attaching an USB 3.0 external hard disk, adding the option dwc_otg.speed=1 into /boot/cmdline.txt. None of that gave a minimal benefit. I returned the hub back to Amazon.
Here are some web references: