Say you've got something like a Raspberry Pi, and you wanna use it for Kodi. The official wiki page for this sort of thing is at https://kodi.wiki/view/HOW-TO:HOW-TO:Autostart_Kodi_for_Linux, which points to https://github.com/graysky2/kodi-standalone-service. You could also just use something like OpenELEC (I hate it, personally), but here's some modified takes on the official-ish instructions. This presumes you're running Ubuntu 19.04 on a Pi 3, or have a similar setup to that. == Step 1, Variant A: Kodi from the main repos, using X11 == Install Kodi and xinit with `apt install kodi xinit xserver-xorg`. Create `/etc/systemd/system/kodi.service` with the contents as ``` lang=ini, name=/etc/systemd/system/kodi.service [Unit] Description=Kodi standalone (X11) After=systemd-user-sessions.service network-online.target sound.target mysqld.service Requires=network-online.target Conflicts=getty@tty1.service [Service] User=kodi Group=kodi PAMName=login TTYPath=/dev/tty1 ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :0 -nolisten tcp vt1 Restart=on-abort StandardInput=tty [Install] WantedBy=graphical.target ``` == Step 1, Variant B: Kodi customized with hardware acceleration, using GBM == Either [[ documentation/kodi/standalone/compile/ | compile it yourself ]] or [[ https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=246837 | grab a package ]]. Make sure to set the following in `config.txt` (may be either `/boot/config.txt` or `/boot/firmware/config.txt`, depending on the distro): ``` lang=ini, name=config.txt dtoverlay=vc4-fkms-v3d gpu_mem=256 ``` Then use the following service file (changing the path used by `ExecStart` if you've [[ documentation/kodi/standalone/compile/ | compiled it yourself ]] and installed to a different path): ``` lang=ini, name=/etc/systemd/system/kodi-rpi4.service [Unit] Description=Kodi standalone (GBM) After=systemd-user-sessions.service network.target network-online.target sound.target upower.service mysqld.service Requires=graphical.target Wants=network.target network-online.target Conflicts=getty@tty1.service [Service] User=kodi Group=kodi PAMName=login TTYPath=/dev/tty1 Environment=WINDOWING=gbm ExecStart=/usr/bin/kodi-standalone Restart=on-abort StandardInput=tty [Install] WantedBy=graphical.target ``` == Step 2 == ``` lang=bash # Add the group sudo addgroup kodi # Add the user, giving it no login shell and with /var/lib/kodi as its home directory sudo useradd -c 'kodi user' -u 420 -g kodi -G audio,input,uucp,video -d /var/lib/kodi -s /usr/sbin/nologin kodi # Not sure why this is necessary frankly, since the shell is set to nologin anyways sudo passwd -l kodi > /dev/null # Actually make the home directory we're using, and set ownership correctly sudo mkdir /var/lib/kodi sudo chown -R kodi:kodi /var/lib/kodi # Now, enable and start the service; use kodi-rpi4.service instead if you used Variant B above sudo systemctl enable kodi.service sudo systemctl start kodi.service ```

Say you've got something like a Raspberry Pi, and you wanna use it for Kodi. There are a few options: # Use [[ https://libreelec.tv/ | LibreELEC ]]. It's a fast, optimised just-enough OS setup for Kodi, and tends to get the fastest support for hardware acceleration since it's largely the Kodi devs themselves developing it. ## If you want to do more with it, see [[documentation/kodi/standalone/libreelec]] here on this wiki. # Use a "real" Linux distro like Debian or Ubuntu. See [[documentation/kodi/standalone/debian]] for instructions. # As an in-between measure, you could use something like [[ https://osmc.tv/ | OSMC ]], which is stripped down and set up for Kodi but is a full Debian-derived distro underneath with `apt` and all that.

Say you've got something like a Raspberry Pi, and you wanna use it for Kodi. The official wiki page for this sort of thing is at https://kodi.wiki/view/HOW-TO:HOW-TO:Autostart_Kodi_for_Linux, which points to https://github.com/graysky2/kodi-standalone-service. You could also just use something like OpenELEC (I hate it, personally), but here's some modified takes on the official-ish instructions. This presumes you're running Ubuntu 19.04 on a Pi 3, or have a similar setup to that. == Step 1, Variant A: Kodi from the main repos, using X11 == Install Kodi and xinit with `apt install kodi xinit xserver-xorg`. Create `/etc/systemd/system/kodi.service` with the contents as ``` lang=ini, name=/etc/systemd/system/kodi.service [Unit] Description=Kodi standalone (X11) After=systemd-user-sessions.service network-online.target sound.target mysqld.service Requires=network-online.target Conflicts=getty@tty1.service [Service] User=kodi Group=kodi PAMName=login TTYPath=/dev/tty1 ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :0 -nolisten tcp vt1 Restart=on-abort StandardInput=tty [Install] WantedBy=graphical.target ``` == Step 1, Variant B: Kodi customized with hardware acceleration, using GBM == Either [[ documentation/kodi/standalone/compile/ | compile it yourself ]] or [[ https://www.raspberrypi.org/forums/viewtopic.php?f=38&t=246837 | grab a package ]]. Make sure to set the following in `config.txt` (may be either `/boot/config.txt` or `/boot/firmware/config.txt`, depending on the distro): ``` lang=ini, name=config.txt dtoverlay=vc4-fkms-v3d gpu_mem=256 ``` Then use the following service file (changing the path used by `ExecStart` if you've [[ documentation/kodi/standalone/compile/ | compiled it yourself ]] and installed to a different path): ``` lang=ini, name=/etc/systemd/system/kodi-rpi4.service [Unit] Description=Kodi standalone (GBM) After=systemd-user-sessions.service network.target network-online.target sound.target upower.service mysqld.service Requires=graphical.target Wants=network.target network-online.target Conflicts=getty@tty1.service [Service] User=kodi Group=kodi PAMName=login TTYPath=/dev/tty1 Environment=WINDOWING=gbm ExecStart=/usr/bin/kodi-standalone Restart=on-abort StandardInput=tty [Install] WantedBy=graphical.target ``` == Step 2 == ``` lang=bash # Add the group sudo addgroup kodi # Add the user, giving it no login shell and with /var/lib/kodi as its home directory sudo useradd -c 'kodi user' -u 420 -g kodi -G audio,input,uucp,video -d /var/lib/kodi -s /usr/sbin/nologin kodi # Not sure why this is necessary frankly, since the shell is set to nologin anyways sudo passwd -l kodi > /dev/null # Actually make the home directory we're using, and set ownership correctly sudo mkdir /var/lib/kodi sudo chown -R kodi:kodi /var/lib/kodi # Now, enable and start the service; use kodi-rpi4.service instead if you used Variant B aboveThere are a few options: sudo systemctl enable kodi.service # Use [[ https://libreelec.tv/ | LibreELEC ]]. It's a fast, optimised just-enough OS setup for Kodi, and tends to get the fastest support for hardware acceleration since it's largely the Kodi devs themselves developing it. sudo systemctl start ## If you want to do more with it, see [[documentation/kodi.service/standalone/libreelec]] here on this wiki. ``` # Use a "real" Linux distro like Debian or Ubuntu. See [[documentation/kodi/standalone/debian]] for instructions. # As an in-between measure, you could use something like [[ https://osmc.tv/ | OSMC ]], which is stripped down and set up for Kodi but is a full Debian-derived distro underneath with `apt` and all that.