Official Kodi Wiki - User contributions [en]

Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

2018-05-17T04:54:26Z

Wirerydr:

To [[User:Klojum|Klojum]] ([[User talk:Klojum|talk]]) - Thank you very much for the "kodi.service" changes re: gettys and plymouth. I did some testing with these changes, and with them I noticed I no longer get a tty login prompt when I do a "systemctl stop kodi". So for now I'm undo'ing your changes, but I will continue to look into this until I figure out what's wrong with the login prompt. Once I've sorted that out I will reinstate your changes accordingly. Thanks again for your contribution!

[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 12:30, 6 December 2016 (EST)

==Guide rewrite==
I am going to be revising a few sections soon.
#Firewall: You can leave it enabled and just open the following ports: TCP: 1151, 8080, and UDP: 1900, 9777
#Pulseaudio: Kodi is fully functional with pulseaudio installed and enabled.
#Systemd service: If you have GDM installed (and autologin enabled) you do not need any of the service script or other changes so it makes this guide much more simple. As the old saying goes: Keep It Simple Stupid.
:[[User:Mooninite|Mooninite]] ([[User talk:Mooninite|talk]]) 09:05, 8 April 2015 (EDT)

#Thanks for the firewall-related tips. I believe the port-list that should be opened will depend on individual circumstances. For example on my standalone setup the kodi.bin process is listening on ports TCP (8080, 1147) and UDP (9777, 1900). Were I to utilize miniDLNA I would have to add TCP port 8200. Airplay can potentially require TCP (80, 443, 554, 3689, 5297, 5289) and UDP (554, 5289, 5353). Given that this is a standalone environment and making custom adjustments to the firewall as services are enabled/disabled is an advanced topic, it seems much simpler to leave the firewall disabled - with the caveats already mentioned in the wiki.
#Pulseaudio still has some deficiencies, such has lacking support for TrueHD or DTS-MA, preventing use of Dolby Pro Logic II, etc. Refer to [[PulseAudio ]]for some further explanation. Actually, the only real advantage Pulseaudio offers is non-exclusive use of the audio subsystem, in cases where you'd like (for example) desktop sounds or other apps to co-exist with Kodi. Since this guide is strongly focused on creating a standalone Kodi environment, Pulseaudio makes little sense to utilize. Given its deficiencies and lack of countervailing advantages, there's no reason to utilize PulseAudio.
#Why would you want GDM to be installed? It's just an unnecessary layer of functionality that introduces complexity but offers little/no benefit. At the very least you'd then have to set up GDM-based auto-login, which is not only extra complexity but a potential security risk. The spirit of this guide is to create a standalone, lightweight installation of Kodi with minimal additional requirements. You are exactly right re: KISS, and introducing a dependency on an unnecessary software layer would seem to contravene this.
You made some earlier edits that removed the section on disabling SELinux. Kodi may have evolved to the point where it can properly function in an SELinux-Enforcing environment, but it used to have issues. I will test in an enforcing environment and update the wiki accordingly. However until I've tested it I will revert your changes to restore the SELinux section.

Thanks again for the tips!
:[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 12:03, 24 April 2015 (EDT)

Hope you don't mind that I added a section for CEC, it was a feature I needed and I thought it may be useful until libcec>=3.0.0 is put into the fedora repos and the rpm in rpmfusion is rebuilt.

:[[User:Slashnull|Slashnull]] ([[User talk:Slashnull|talk]]) 13:46, 15 January 2016 (EDT)

Don't mind at all Slashnull - TYVM for the contribution, and also for maintaining the existing look-and-feel. I may reorder things a bit to avoid CEC users from doing a double install of the generic and then CEC-enabled RPMs, but that's trivial.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 00:20, 18 January 2016 (EST)

Hi Spazticclown - thanks for the video-group contribution. In my experience this is not actually necessary in order to run Kodi as described in this HowTo - not on any version of Fedora from F19 through to the current F23, anyway. I believe as long as the user is in group 'wheel' (which it is as a result of [[HOW-TO:Install Kodi on Fedora 23 using RPMFusion packages#Starting_the_Installation_and_Creating_a_Kodi_User|step 3.3]]), that is sufficient. Just to be sure I took a look at my main kodi box running in my livingroom, and confirmed that user Kodi is not present in group 'video' (gid 39). As such I have reverted back to before your change, but I did want to thank you again for your contribution.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 23:51, 7 February 2016 (EST)

It seems to me that there are two different objectives, here. As you say, this is guide, at the moment, is about setting up a minimal dedicated Kodi machine. However, some people are going to want a machine that can also be used as a more-or-less vanilla Fedora Workstation. In this situation, you’d likely want to keep firewalld, PulseAudio and GDM, and I think it’s worth mentioning this in the guide if possible. I’d welcome Mooninite’s method being written up as a separate section of the guide.
:[[User:Mavit|Mavit]] ([[User talk:Mavit|talk]]) 09:37, 3 May 2018 (UTC)

== SELinux support, clean shutdown ==

I've been tweaking the startup on my Fedora/Kodi setup, and I have a simpler setup that:
* Supports shutdown/reboot etc w/o PolicyKit tweaks
* Allows for adding xrandr tweaks for "Broadcast RGB" etc
* Doesn't leave stray dbus processes
* Has X options for running w/o mouse and giving Kodi control of the screensaver
* Supported SELinux enforcing out of the box w/o any policy hacks
* Supports clean shutdown of Kodi on system shutdown/reboot

I've added this to the bottom of the page at [[HOW-TO:Install_Kodi_on_Fedora_26_using_RPMFusion_packages#ALTERNATIVE_Login_based_startup]]

== firewalld knows about Kodi, now ==

Kodi 18 will [https://github.com/xbmc/xbmc/pull/13845 include] service definitions for <code>firewalld</code>, which will allow the instructions for opening the firewall to be simplified slightly.
:[[User:Mavit|Mavit]] ([[User talk:Mavit|talk]]) 09:47, 3 May 2018 (UTC)

I haven't had the chance to test them yet, Mavit, but I like pretty-much all of the Alternative Startup aspects that you have added - thank you very much for investing in this Wiki. I'm especially interested to hear that Kodi v18 ships with Firewalld definitions - I've never been totally comfortable with disabling the firewall even on minimalistic installations. At this moment I do not see Kodi v18 (alpha) in the RPMFusion repositories. However as it happens I have a setup which utilizes Kodi built directly from the Master branch of the [https://github.com/xbmc/xbmc Kodi GitHub repo]. So I will test your alternative setup with Kodi 18, and prepare some Wiki changes to be rolled in whenever Kodi v18 gets released and appears in RPMFusion.

I personally lean towards the approach of presenting two separate guides: This (minimalistic) approach, and a separate guide explaining how to install/configure Kodi on a more regularized workstation-based installation of Fedora. That 2nd guide would presumably be much more straightforward in that most of the audio/visual things would have already been prepared for the user's specific environment at installation time. Crosslinks to each other could be added near the beginning of each guide enabling choice, and also to [[HOW-TO:Install Kodi for Linux#Fedora]] for the sake of completeness.

However, someone else (other than me) will have to step forward to create and maintain that 2nd guide, as I do not have any non-minimalistic Fedora installations with which to develop this guide.
:[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 04:53, 17 May 2018 (UTC)

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-31T00:10:16Z

Wirerydr: Updated Kodi from 17.3 to 17.4

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 26 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 26 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 26 Server (x86_64)]
|-
! Kodi
| [https://download1.rpmfusion.org/free/fedora/updates/26/x86_64/repoview/kodi.html Kodi v17.4 (Krypton)] from the [https://download1.rpmfusion.org/free/fedora/updates/26/x86_64/repoview/index.html rpmfusion-free] repository
|-
! Motherboard
| [https://www.gigabyte.com/Motherboard/GA-F2A88XM-D3H-rev-30#ov Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [https://www.amd.com/en-us/products/processors/desktop/a-series-apu# AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 460 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [https://www.wdc.com/en-um/products/internal-storage/wd-black-desktop.html Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [https://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [https://usa.denon.com/us/product/hometheater/receivers/avr3808ci Denon AVR-3808ci]
|-
! TV
| [https://shop.panasonic.com/support-only/TH-50PZ800U.html Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 26 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# This guide shows how to either enable TCP port 8080 (for Kodi Remote Control), or fully disable the local Firewalld daemon. It also shows how to disable SELinux. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 26, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 26 ==

=== Obtaining the Fedora 26 Server (x86_64) Installation Image ===
Visit the Fedora 26 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download (64-bit 2.2GB iso image). Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 26 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 26.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Adjusting or Disabling Firewalld ===
'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. It greatly enhances security, but it can interfere with certain networking features of Kodi such as uPnP, file-sharing, remote-control apps, etc. Because of this, two steps are shown below. One step opens TCP port 8080, which allows Kodi to be remotely controlled and for remote-control apps such as [[Kore]] or [https://yatse.tv/redmine/projects/yatse Yatse] to work properly. The second step completely disables Firewalld, and is intended for situations where other network connectivity is required (e.g. uPnP, file-sharing, AirPlay, Bonjour, etc.). Only one or the other of these steps should be performed depending on your needs. If you have no need for this kind of network connectivity, then it is probably better to skip both steps and leave Firewalld running as-is.

==== Enable TCP Port 8080 to Enable Kodi Remote-Control ====
The following command adds a new permanent rule to Firewalld that allows access via TCP port 8080. This step assumes that your local network is 192.168.0.0/24. If it is something else, then adjust the command accordingly.
{{redv|'''IMPORTANT:'''|Only perform this step if you '''just ''' want open TCP port 8080 to enable remote control of Kodi.}}
<syntaxhighlight lang="bash">
sudo firewallctl zone --permanent FedoraServer add rich-rule 'rule family="ipv4" source address="192.168.0.0/24" port port="8080" protocol="tcp" accept'
</syntaxhighlight>
 

==== Disable Firewalld Entirely ====
The following commands fully disable and uninstall Firewalld. This may also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
{{redv|'''WARNING:'''|Only perform these steps if you need network-based connectivity beyond Kodi remote-control. If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

=== Setting SELinux to Permissive Mode ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[https://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 26 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [https://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo https://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
{{bluev|'''NOTE concerning X-Windows vs Wayland:'''|At the time of writing (August 2017), native Wayland support in Fedora 26 for nVidia GPUs is very-much a moving target (it appears to be a bit more stable for AMD / Intel based GPUs). nVidia Drivers are undergoing enhancement, compositors being made more compatible with nVidia drivers, and issues with things like KMS (kernel mode-setting) are being hashed out. This Wiki will continue to use X-Windows instead of native Wayland (or XWayland within X-Windows) until the landscape becomes a bit less turbulent and a bit more stable.}}

Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [https://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 26 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv https://download1.rpmfusion.org/free/fedora/updates/26/SRPMS/k/kodi-17.4-1.fc26.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-08-30 19:57:26.794695552 -0400
+++ kodi.spec.patched 2017-08-30 19:57:04.246018991 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.4
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 26 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T05:21:05Z

Wirerydr: Added mention of new Firewalld steps into Assumptions section

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 26 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 26 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 26 Server (x86_64)]
|-
! Kodi
| [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/kodi.html Kodi v17.3 (Krypton)] from the [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/index.html rpmfusion-free] repository
|-
! Motherboard
| [https://www.gigabyte.com/Motherboard/GA-F2A88XM-D3H-rev-30#ov Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [https://www.amd.com/en-us/products/processors/desktop/a-series-apu# AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 460 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [https://www.wdc.com/en-um/products/internal-storage/wd-black-desktop.html Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [https://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [https://usa.denon.com/us/product/hometheater/receivers/avr3808ci Denon AVR-3808ci]
|-
! TV
| [https://shop.panasonic.com/support-only/TH-50PZ800U.html Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 26 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# This guide shows how to either enable TCP port 8080 (for Kodi Remote Control), or fully disable the local Firewalld daemon. It also shows how to disable SELinux. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 26, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 26 ==

=== Obtaining the Fedora 26 Server (x86_64) Installation Image ===
Visit the Fedora 26 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download (64-bit 2.2GB iso image). Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 26 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 26.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Adjusting or Disabling Firewalld ===
'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. It greatly enhances security, but it can interfere with certain networking features of Kodi such as uPnP, file-sharing, remote-control apps, etc. Because of this, two steps are shown below. One step opens TCP port 8080, which allows Kodi to be remotely controlled and for remote-control apps such as [[Kore]] or [https://yatse.tv/redmine/projects/yatse Yatse] to work properly. The second step completely disables Firewalld, and is intended for situations where other network connectivity is required (e.g. uPnP, file-sharing, AirPlay, Bonjour, etc.). Only one or the other of these steps should be performed depending on your needs. If you have no need for this kind of network connectivity, then it is probably better to skip both steps and leave Firewalld running as-is.

==== Enable TCP Port 8080 to Enable Kodi Remote-Control ====
The following command adds a new permanent rule to Firewalld that allows access via TCP port 8080. This step assumes that your local network is 192.168.0.0/24. If it is something else, then adjust the command accordingly.
{{redv|'''IMPORTANT:'''|Only perform this step if you '''just ''' want open TCP port 8080 to enable remote control of Kodi.}}
<syntaxhighlight lang="bash">
sudo firewallctl zone --permanent FedoraServer add rich-rule 'rule family="ipv4" source address="192.168.0.0/24" port port="8080" protocol="tcp" accept'
</syntaxhighlight>
 

==== Disable Firewalld Entirely ====
The following commands fully disable and uninstall Firewalld. This may also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
{{redv|'''WARNING:'''|Only perform these steps if you need network-based connectivity beyond Kodi remote-control. If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

=== Setting SELinux to Permissive Mode ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[https://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 26 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [https://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo https://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
{{bluev|'''NOTE concerning X-Windows vs Wayland:'''|At the time of writing (August 2017), native Wayland support in Fedora 26 for nVidia GPUs is very-much a moving target (it appears to be a bit more stable for AMD / Intel based GPUs). nVidia Drivers are undergoing enhancement, compositors being made more compatible with nVidia drivers, and issues with things like KMS (kernel mode-setting) are being hashed out. This Wiki will continue to use X-Windows instead of native Wayland (or XWayland within X-Windows) until the landscape becomes a bit less turbulent and a bit more stable.}}

Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [https://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 26 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv https://download1.rpmfusion.org/free/fedora/releases/26/Everything/source/SRPMS/k/kodi-17.3-1.fc26.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-08-20 20:33:00.312714969 -0400
+++ kodi.spec.patched 2017-08-20 20:30:27.948942696 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 26 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T05:07:42Z

Wirerydr: Updated Firewalld section to include optional opening of 8080 only, instead of fully disabling Firewalld

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 26 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 26 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 26 Server (x86_64)]
|-
! Kodi
| [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/kodi.html Kodi v17.3 (Krypton)] from the [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/index.html rpmfusion-free] repository
|-
! Motherboard
| [https://www.gigabyte.com/Motherboard/GA-F2A88XM-D3H-rev-30#ov Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [https://www.amd.com/en-us/products/processors/desktop/a-series-apu# AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 460 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [https://www.wdc.com/en-um/products/internal-storage/wd-black-desktop.html Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [https://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [https://usa.denon.com/us/product/hometheater/receivers/avr3808ci Denon AVR-3808ci]
|-
! TV
| [https://shop.panasonic.com/support-only/TH-50PZ800U.html Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 26 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 26, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 26 ==

=== Obtaining the Fedora 26 Server (x86_64) Installation Image ===
Visit the Fedora 26 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download (64-bit 2.2GB iso image). Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 26 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 26.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Adjusting or Disabling Firewalld ===
'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. It greatly enhances security, but it can interfere with certain networking features of Kodi such as uPnP, file-sharing, remote-control apps, etc. Because of this, two steps are shown below. One step opens TCP port 8080, which allows Kodi to be remotely controlled and for remote-control apps such as [[Kore]] or [https://yatse.tv/redmine/projects/yatse Yatse] to work properly. The second step completely disables Firewalld, and is intended for situations where other network connectivity is required (e.g. uPnP, file-sharing, AirPlay, Bonjour, etc.). Only one or the other of these steps should be performed depending on your needs. If you have no need for this kind of network connectivity, then it is probably better to skip both steps and leave Firewalld running as-is.

==== Enable TCP Port 8080 to Enable Kodi Remote-Control ====
The following command adds a new permanent rule to Firewalld that allows access via TCP port 8080. This step assumes that your local network is 192.168.0.0/24. If it is something else, then adjust the command accordingly.
{{redv|'''IMPORTANT:'''|Only perform this step if you '''just ''' want open TCP port 8080 to enable remote control of Kodi.}}
<syntaxhighlight lang="bash">
sudo firewallctl zone --permanent FedoraServer add rich-rule 'rule family="ipv4" source address="192.168.0.0/24" port port="8080" protocol="tcp" accept'
</syntaxhighlight>
 

==== Disable Firewalld Entirely ====
The following commands fully disable and uninstall Firewalld. This may also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
{{redv|'''WARNING:'''|Only perform these steps if you need network-based connectivity beyond Kodi remote-control. If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

=== Setting SELinux to Permissive Mode ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[https://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 26 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [https://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo https://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
{{bluev|'''NOTE concerning X-Windows vs Wayland:'''|At the time of writing (August 2017), native Wayland support in Fedora 26 for nVidia GPUs is very-much a moving target (it appears to be a bit more stable for AMD / Intel based GPUs). nVidia Drivers are undergoing enhancement, compositors being made more compatible with nVidia drivers, and issues with things like KMS (kernel mode-setting) are being hashed out. This Wiki will continue to use X-Windows instead of native Wayland (or XWayland within X-Windows) until the landscape becomes a bit less turbulent and a bit more stable.}}

Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [https://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 26 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv https://download1.rpmfusion.org/free/fedora/releases/26/Everything/source/SRPMS/k/kodi-17.3-1.fc26.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-08-20 20:33:00.312714969 -0400
+++ kodi.spec.patched 2017-08-20 20:30:27.948942696 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 26 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

HOW-TO:Install Kodi for Linux

2017-08-22T04:06:17Z

Wirerydr: Updated Fedora link for Fedora 26

{{mininav|[[Linux]] {{l2| [[Installation]] }} }}
== Installing Kodi on Ubuntu-based distributions ==
{{warning|Some (later) Ubuntu versions include Kodi built by Ubuntu themselves. If you have installed Ubuntu Kodi, please remove the packages "kodi kodi-bin kodi-data" before trying to install team-xbmc PPA packages.}}

See [[SSH]] or [http://help.ubuntu.com/community/UsingTheTerminal Click here to find out how to use the terminal.]

Use the command line terminal and enter the following commands. Follow the prompts as you would any other software installation.

<syntaxhighlight lang="bash">
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

{{#lst:Team XBMC PPA|repos}}

Note that this PPA only provides builds for Ubuntu i386 and Ubuntu amd64 but not for Ubuntu armhf, which can run on a Raspberry Pi.

=== Installing binary add-ons (PVR, audio decoders, audio encoders, screensavers, visualizations, audio DSP) ===
{{see|Ubuntu binary add-ons}}

=== Installing a development build ===
{{see also|Development builds}}
To install a beta/unstable version of {{kodi}} you must first add the unstable repository, then install XBMC. Use <code>ppa:team-xbmc/xbmc-nightly</code> for nightly builds and <code>ppa:team-xbmc/unstable</code> for [[beta]] builds.

<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/xbmc-nightly
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

Note that if you have any addons (such as PVR clients), these must be updated as well (they will not be updated automatically):
<syntaxhighlight lang="bash">
sudo apt-get install kodi-pvr-mythtv
</syntaxhighlight>

=== Upgrading ===
<section begin="Ubuntu upgrade" />
To update Kodi when a new version is released, just do a general system/package or use the following commands in the terminal (or via [[SSH]]):

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get upgrade
</syntaxhighlight>

{{note|In some cases where additional packages are required, Kodi will fail to upgrade when using the upgrade commands as above. To install additional packages use the command below:

<syntaxhighlight lang="bash">
sudo apt-get dist-upgrade
</syntaxhighlight>}}
<section end="Ubuntu upgrade" />

=== Downgrading to a stable version from a development version ===
If you install a nightly build or an unstable release and want to return to a stable release, follow these instructions:

Find the current PPA you are using:
<syntaxhighlight lang="bash">
sudo apt-cache policy | grep team-xbmc
</syntaxhighlight>

Remove the unstable or nightly PPA where it says '''PPAHERE''':
<syntaxhighlight lang="bash">
sudo add-apt-repository -r ppa:PPAHERE
</syntaxhighlight>

Then restore the stable version with the following commands:
<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get remove kodi kodi-bin
sudo apt-get install kodi
</syntaxhighlight>

=== Downgrading between newer and older stable versions ===
If you want to return to the previous stable release, follow these instructions:

Remove the current stable PPA:
<syntaxhighlight lang="bash">
sudo add-apt-repository -r ppa:team-xbmc/ppa
</syntaxhighlight>

Then install the old stable version with the following commands:
<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/kodi-old
sudo apt-get update
sudo apt-get remove kodi*
sudo apt-get install kodi
</syntaxhighlight>

=== Reverting to an earlier nightly ===
ALthough launchpad doesn't list older nightlies in their PPA, they are usually still available for download directly from the website.
Visit https://launchpad.net/~team-xbmc/+archive/ubuntu/xbmc-nightly/+packages?field.name_filter=&field.status_filter=superseded&field.series_filter=

You will then have to download the appropiate .deb file and manually install it.

=== Uninstalling ===
If you need to remove and purge an application and finally removing/purging also the application configurations files, do so by using the following commands:

<syntaxhighlight lang="bash" enclose="div">
sudo apt-get update
sudo apt-get remove kodi*
sudo apt-get purge kodi*
</syntaxhighlight>

Then remove the settings folder to remove all settings and library data. This will not delete any videos or music, but just the settings and library data itself:
<syntaxhighlight lang="bash">
rm -r ~/.kodi/
</syntaxhighlight>
or
<syntaxhighlight lang="bash" enclose="div">
rm -r ~/.xbmc/ # for older versions before 14.0
</syntaxhighlight>

== Embedded/Appliance type install==

=== LibreELEC ===
{{main|LibreELEC}}
{{#lst:LibreELEC|intro}}

== Third Party Repositories ==


The instructions in this section are for unofficial Linux binaries that are un/semi supported by Team Kodi. Most of those binaries use system ffmpeg or even worse totally untested libav, which is not recommended for {{kodi}} as we support ffmpeg only.

=== Debian ===

The installation if you are using Debian (Jessie), you can use the debian-backports repository.

Add the following lines to your /etc/apt/sources.list file, as superuser (sudo)

<syntaxhighlight lang="bash">
# kodi repos
# starting with debian jessie, debian provides kodi via its backports repository
# remember: those packages are not supported by team kodi
deb http://http.debian.net/debian jessie-backports main
</syntaxhighlight>

And then, update APT and install Kodi.

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

Enjoy your new Kodi.

=== Fedora ===
Refer to [[HOW-TO:Install Kodi on Fedora 26 using RPMFusion packages]] for a guide showing how to install Fedora 26 and Kodi to create a quick-booting, standalone style of media player.

=== Raspbian ===
{{see also|HOW-TO:Install Kodi on Raspberry Pi}}
Installing on Raspbian is done with:

<syntaxhighlight lang="bash">
sudo apt-get install kodi
</syntaxhighlight>

Upgrading on Raspbian is done with:

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get upgrade
</syntaxhighlight>

== Installation from source ==
If distribution packages are not available, or you need a newer version, or specific features enabled, then you will most likely need to compile from source. While compiling from source does not differ very much between distributions (except for installation of build dependencies), a few different guides are available in this wiki.

* [[HOW-TO compile XBMC for Linux from source code]]
* [[HOW-TO compile XBMC for Linux on Debian/Ubuntu]] - This is a tutorial on how to compile and install {{kodi}} on Debian and Ubuntu.

== See also ==
* [[Linux]]
* [[HOW-TO:Autostart XBMC for Linux]]
*[[JeOS implementations for Kodi]]

* [[Linux FAQ]]

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]
[[Category:Manual]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T04:04:28Z

Wirerydr: Minor update to X11 vs Wayland verbage

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 26 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 26 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 26 Server (x86_64)]
|-
! Kodi
| [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/kodi.html Kodi v17.3 (Krypton)] from the [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/index.html rpmfusion-free] repository
|-
! Motherboard
| [https://www.gigabyte.com/Motherboard/GA-F2A88XM-D3H-rev-30#ov Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [https://www.amd.com/en-us/products/processors/desktop/a-series-apu# AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 460 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [https://www.wdc.com/en-um/products/internal-storage/wd-black-desktop.html Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [https://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [https://usa.denon.com/us/product/hometheater/receivers/avr3808ci Denon AVR-3808ci]
|-
! TV
| [https://shop.panasonic.com/support-only/TH-50PZ800U.html Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 26 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 26, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 26 ==

=== Obtaining the Fedora 26 Server (x86_64) Installation Image ===
Visit the Fedora 26 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download (64-bit 2.2GB iso image). Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 26 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 26.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[https://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 26 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [https://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo https://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
{{bluev|'''NOTE concerning X-Windows vs Wayland:'''|At the time of writing (August 2017), native Wayland support in Fedora 26 for nVidia GPUs is very-much a moving target (it appears to be a bit more stable for AMD / Intel based GPUs). nVidia Drivers are undergoing enhancement, compositors being made more compatible with nVidia drivers, and issues with things like KMS (kernel mode-setting) are being hashed out. This Wiki will continue to use X-Windows instead of native Wayland (or XWayland within X-Windows) until the landscape becomes a bit less turbulent and a bit more stable.}}

Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [https://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 26 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv https://download1.rpmfusion.org/free/fedora/releases/26/Everything/source/SRPMS/k/kodi-17.3-1.fc26.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-08-20 20:33:00.312714969 -0400
+++ kodi.spec.patched 2017-08-20 20:30:27.948942696 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 26 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T04:02:08Z

Wirerydr: Updated for Fedora 26; Upgrade most http:// URLs to https://; Updated X11 vs Wayland verbage

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 26 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 26 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 26 Server (x86_64)]
|-
! Kodi
| [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/kodi.html Kodi v17.3 (Krypton)] from the [https://download1.rpmfusion.org/free/fedora/releases/26/Everything/x86_64/os/repoview/index.html rpmfusion-free] repository
|-
! Motherboard
| [https://www.gigabyte.com/Motherboard/GA-F2A88XM-D3H-rev-30#ov Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [https://www.amd.com/en-us/products/processors/desktop/a-series-apu# AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 460 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [https://www.wdc.com/en-um/products/internal-storage/wd-black-desktop.html Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [https://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [https://usa.denon.com/us/product/hometheater/receivers/avr3808ci Denon AVR-3808ci]
|-
! TV
| [https://shop.panasonic.com/support-only/TH-50PZ800U.html Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 26 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 26, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 26 ==

=== Obtaining the Fedora 26 Server (x86_64) Installation Image ===
Visit the Fedora 26 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download (64-bit 2.2GB iso image). Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 26 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 26 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 26.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[https://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 26 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [https://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo https://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
{{bluev|'''NOTE concerning X-Windows vs Wayland:'''|At the time of writing (August 2017), native Wayland support in Fedora 26 for nVidia GPUs is very-much a moving target (it appears to be a bit more stable for AMD / Intel based GPUs). nVidia Drivers are undergoing enhancement, compositors being made more compatible with nVidia drivers, and issues with things like KMS (kernel mode-setting) are being hashed out. This Wiki will continue to use X-Windows instead of native Wayland (and XWayland within X-Windows) until the landscape becomes a bit less turbulent and stable.}}

Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [https://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 26 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv https://download1.rpmfusion.org/free/fedora/releases/26/Everything/source/SRPMS/k/kodi-17.3-1.fc26.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-08-20 20:33:00.312714969 -0400
+++ kodi.spec.patched 2017-08-20 20:30:27.948942696 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 26 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

File:Fedora 26 Kodi 17 Install 005 - Console Login.png

2017-08-22T03:59:15Z

Wirerydr:

File:Fedora 26 Kodi 17 Install 004 - Install In Progress.png

2017-08-22T03:58:58Z

Wirerydr:

File:Fedora 26 Kodi 17 Install 003 - User Creation.png

2017-08-22T03:58:36Z

Wirerydr:

File:Fedora 26 Kodi 17 Install 002 - Software Selection.png

2017-08-22T03:57:31Z

Wirerydr:

File:Fedora 26 Kodi 17 Install 001 - Main Screen.png

2017-08-22T03:56:54Z

Wirerydr:

Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T03:52:19Z

Wirerydr: Wirerydr moved page HOW-TO talk:Install Kodi on Fedora 25 using RPMFusion packages to HOW-TO talk:Install Kodi on Fedora 26 using RPMFusion packages: Updated from Fedora 25 to Fedora 26

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-08-22T03:52:18Z

Wirerydr: Wirerydr moved page HOW-TO:Install Kodi on Fedora 25 using RPMFusion packages to HOW-TO:Install Kodi on Fedora 26 using RPMFusion packages: Updated from Fedora 25 to Fedora 26

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.3 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [https://www.evga.com/Products/Specs/GPU.aspx?pn=3533A3B0-18D0-4D86-8DD7-27904C44E042 EVGA GeForce GTX 450 SuperClocked 1024MB PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.3-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-06-19 23:09:08.530340121 -0400
+++ kodi.spec.patched 2017-06-19 23:02:33.844321732 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-06-22T05:14:49Z

Wirerydr: Updated reference to author's graphics card

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-06-21T01:35:28Z

Wirerydr: Minimzed list of packages installed during nVidia driver installation

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.3 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.3-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-06-19 23:09:08.530340121 -0400
+++ kodi.spec.patched 2017-06-19 23:02:33.844321732 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-06-20T04:18:35Z

Wirerydr: Updated Kodi from 17.1 to 17.3; Deprecated nVidia 340.x legacy driver coverage; Fixed small section-heading typo

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.3 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [https://negativo17.org/nvidia-driver-improvements-for-fedora-25/ Negativo17 fedora-nvidia repository].

{{bluev|'''NOTE:'''|There are several categories of nVidia drivers releases, covering different eras of nVidia-based graphics. Formerly, this guide covered both the '''Legacy 340.x''' drivers (for older G8x, G9x, and GT2xx GPUs), as well as the current '''Short-Lived''' drivers for more modern GPUs. However the '''Legacy 340.x''' repository at Negativo17 has been discontinued, and as-such this guide now only covers current nVidia GPUs and motherboards based on them. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers. If so, then you may be able to get them successfully installed from the RPMFusion repository using [https://rpmfusion.org/Howto/NVIDIA their HOWTO]. You can then continue on with the remainder of this guide.}}

==== (nVidia) Enabling the Negativo17 fedora-nvidia Driver Repository ====
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the nVidia Drivers ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.3-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-06-19 23:09:08.530340121 -0400
+++ kodi.spec.patched 2017-06-19 23:02:33.844321732 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.3
@@ -38,7 +38,9 @@
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Build Dependencies ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-04-11T17:58:56Z

Wirerydr: Updated Kodi from 17.0 to 17.1

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.1 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.1-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-04-11 12:50:07.790160089 -0400
+++ kodi.spec.patched 2017-04-11 12:57:23.121705633 -0400
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.1
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-02-10T16:33:10Z

Wirerydr: Updated Kodi from 17.x RC to 17.x Final

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2017, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.0-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-02-10 10:47:58.888201410 -0500
+++ kodi.spec.patched 2017-02-10 10:52:16.218891454 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-02-10T15:55:52Z

Wirerydr:

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
As of February 10th, 2016, this guide was updated to cover Fedora 25 and to Kodi 17.x Krypton. It is ready for mainstream use.
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''' and '''updates''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.0-1.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-02-10 10:47:58.888201410 -0500
+++ kodi.spec.patched 2017-02-10 10:52:16.218891454 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
#global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-18T16:00:14Z

Wirerydr: Added step disabling optical drive auto-closing

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/testing/25/SRPMS/k/kodi-17.0-0.12.rc3.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-01-18 01:13:16.224851760 -0500
+++ kodi.spec.patched 2017-01-18 01:21:02.841865498 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Build issue, fixed upstream
Patch3: kodi-17.0rc3-AEDefines.patch
@@ -259,11 +263,14 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%patch3 -p1 -b.aedefines
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -294,7 +301,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
~
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>
 
=== Configure Optical Drive to Not Automatically Close ===
Sometimes you will find that when you eject your optical drive tray, it will try to immediately close again, giving you little time to insert/remove a disc. If this is a problem for you then apply the following steps to configure a Kernel parameter to disable optical drive auto-closing.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "dev.cdrom.autoclose = 0" >>/etc/sysctl.d/50-cdrom_autoclose.conf'
sudo sysctl -p /etc/sysctl.d/50-cdrom_autoclose.conf
</syntaxhighlight>
 
== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-18T15:49:06Z

Wirerydr: Added step preventing Kodi from being auto-updated from repo when locally-built version is used

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/testing/25/SRPMS/k/kodi-17.0-0.12.rc3.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-01-18 01:13:16.224851760 -0500
+++ kodi.spec.patched 2017-01-18 01:21:02.841865498 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Build issue, fixed upstream
Patch3: kodi-17.0rc3-AEDefines.patch
@@ -259,11 +263,14 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%patch3 -p1 -b.aedefines
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -294,7 +301,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
~
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
==== Prevent Kodi From Being Updated Automatically ====
Now that you are using your own build of Kodi, you will probably want to prevent it from being automatically updated whenever new installation RPMs become available in the RPMFusion repository (because they would remove your ability to playback DVD content). The following step prevents Kodi from being automatically updated. You will now be able to choose when to grab a new source release, and build/install it yourself.
<syntaxhighlight lang="bash">
sudo sh -c 'echo "exclude=kodi*" >>/etc/dnf/dnf.conf'
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-18T15:35:58Z

Wirerydr: Update rebuilding-kodi section to utilize RC3

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/testing/25/SRPMS/k/kodi-17.0-0.12.rc3.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- kodi.spec 2017-01-18 01:13:16.224851760 -0500
+++ kodi.spec.patched 2017-01-18 01:21:02.841865498 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Build issue, fixed upstream
Patch3: kodi-17.0rc3-AEDefines.patch
@@ -259,11 +263,14 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%patch3 -p1 -b.aedefines
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -294,7 +301,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
~
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-12T19:46:19Z

Wirerydr: Updated URL for Kodi SRPM from 'updates-testing' to 'updates' repo

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/25/SRPMS/k/kodi-17.0-0.12.rc2.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- /home/kodi/orig/kodi.spec 2017-01-09 21:27:17.288275582 -0500
+++ kodi.spec 2017-01-12 00:04:31.463223839 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-12T05:09:58Z

Wirerydr: Fix SOURCE4 path typo in the dvd-enabling patch

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/testing/25/SRPMS/k/kodi-17.0-0.12.rc2.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- /home/kodi/orig/kodi.spec 2017-01-09 21:27:17.288275582 -0500
+++ kodi.spec 2017-01-12 00:04:31.463223839 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdcss/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-10T17:02:52Z

Wirerydr: Added section showing how to rebuild Kodi with DVD Playback enabled

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi ==
The simplest way to install Kodi is to use the pre-built packages provided by RPMFusion. However at present these pre-built packages do not provide DVD playback capability (including TS_VIDEO folders). If you require DVD playback capability, then see below for a series of steps that recreate your own Kodi packages with DVD playback capability enabled.
 
=== Installing Kodi Using Pre-Built RPMFusion Packages (No DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform this step if you want to use the pre-built packages from RPMFusion.}}
The following command installs the pre-build Kodi packages from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>
 
=== Rebuilding Kodi Packages (Includes DVD Playback) ===
{{redv|'''IMPORTANT:'''|Only perform these steps if you want to rebuild Kodi yourself to enable DVD Playback capability.}}
{{redv|'''IMPORTANT:'''|These steps cause you to obtain and use [http://www.videolan.org/developers/libdvdcss.html libdvdcss] for encrypted DVD playback. Ensure that obtaining/using libdvdcss is legal in your jurisdiction before proceeding.}}
The following steps first set up a development environment, and then build Kodi from the RPMFusion Source package, after enabling DVD Playback. The resulting RPMs may then be installed either on this system, or another Fedora 25 system intended to run Kodi. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
==== Set-Up Build Environment and Toolchain ====
These steps create an RPM build tree within your user's home environment, and install some tools used by the build process.
<syntaxhighlight lang="bash">
sudo dnf install rpmdevtools rpmlint gcc-c++
rpmdev-setuptree
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install the RPMFusion Source RPM for Kodi, which will be used to reproduce the Kodi packages. They also install the source-trees for libdvdcss, libdvdnav, and libdvdread, which collectively provide DVD playback capability.
{{bluev|'''NOTE:'''|The Source RPM for Kodi is what was available from RPMFusion at the time of writing (Kodi 17.0-0.12 RC2 as of Jan. 10th). Once Kodi Final has been released and made available by RPMFusion, this guide will be updated.}}
<syntaxhighlight lang="bash">
rpm -iv http://download1.rpmfusion.org/free/fedora/updates/testing/25/SRPMS/k/kodi-17.0-0.12.rc2.fc25.src.rpm
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
curl -Lo ~/rpmbuild/SOURCES/kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
</syntaxhighlight>
 
==== Enable DVD Playback Capability ====
This step creates a patch that re-enables libdvdcss/libdvdnav/libdvdread as well as optical-drive support. It then applies the patch to the Kodi Source RPM SPEC file. The original SPEC file is saved as '''*.orig'''. Cut-and-paste this step in its entirety.
<syntaxhighlight lang="bash">
cat <<"ENDcat" >/tmp/re-enable_dvd_spec.patch
--- /home/kodi/orig/kodi.spec 2017-01-09 21:27:17.288275582 -0500
+++ kodi.spec 2017-01-09 21:51:52.049916449 -0500
@@ -4,7 +4,7 @@
# use the line below for pre-releases
%global DIRVERSION %{version}%{PRERELEASE}
%global _hardened_build 1
-%global _with_dvd 0
+%global _with_dvd 1

Name: kodi
Version: 17.0
@@ -25,18 +25,22 @@
Source1: kodi-generate-tarball-xz.sh

%if 0%{?_with_dvd}
-# kodi uses modified libdvd{nav,read} source and downloads at build time
+# kodi uses modified libdvd{css,nav,read} source and downloads at build time
# wget -O kodi-libdvdnav-master.tar.gz https://github.com/xbmc/libdvdnav/archive/master.tar.gz
Source2: kodi-libdvdnav-master.tar.gz
# wget -O kodi-libdvdread-master.tar.gz https://github.com/xbmc/libdvdread/archive/master.tar.gz
Source3: kodi-libdvdread-master.tar.gz
+# wget -O kodi-libdvdcss-master.tar.gz https://github.com/xbmc/libdvdcss/archive/master.tar.gz
+Source4: kodi-libdvdcss-master.tar.gz
%endif

# Set program version parameters
Patch1: kodi-16.0-versioning.patch

# Drop DVD library support
+%if ! 0%{?_with_dvd}
Patch2: kodi-17a2-libdvd.patch
+%endif

# Optional deps (not in EPEL)
%if 0%{?fedora}
@@ -256,10 +260,13 @@
%prep
%setup -q -n %{name}-%{DIRVERSION}
%patch1 -p1 -b.versioning
+%if ! 0%{?_with_dvd}
%patch2 -p1 -b.libdvd
+%endif
%if 0%{?_with_dvd}
cp -p %{SOURCE2} tools/depends/target/libdvdnav/libdvdnav-master.tar.gz
cp -p %{SOURCE3} tools/depends/target/libdvdread/libdvdread-master.tar.gz
+cp -p %{SOURCE4} tools/depends/target/libdvdread/libdvdcss-master.tar.gz
%endif

@@ -290,7 +297,9 @@
%else
--disable-ssh \
%endif
+%if ! 0%{?_with_dvd}
--disable-optical-drive \
+%endif
--disable-optimizations --disable-debug \
%ifnarch %{arm}
--enable-gl \
ENDcat
cd ~/rpmbuild/SPECS
patch -b </tmp/re-enable_dvd_spec.patch
</syntaxhighlight>
 
==== Install Kodi Source RPM, and libdvdcss / libdvdnav / libdvdread Modules ====
These steps install dependencies required to build Kodi.
<syntaxhighlight lang="bash">
sudo dnf builddep kodi
sudo dnf install doxygen giflib-devel
</syntaxhighlight>
 
==== Generate the Patched Source Tree ====
These steps create the final patched source-tree that will be used to actually build Kodi.
<syntaxhighlight lang="bash">
cd ~/rpmbuild/SOURCES
./kodi-generate-tarball-xz.sh
</syntaxhighlight>
 
==== Build Kodi RPMs ====
This step builds Kodi, and packages it in several installable RPMs. A summary of how long things took will be shown at the end. A log of the build process will be saved as '''~/build_kodi.log''' .
{{bluev|'''NOTE:'''|This step will probably take a LONG time - potentially an hour or longer. It's a good time to grab a coffee, wash some dishes, ''etc.''}}
<syntaxhighlight lang="bash">
time rpmbuild -ba ~/rpmbuild/SPECS/kodi.spec 2>&1 | tee ~/build_kodi.log
</syntaxhighlight>
 
==== Install Kodi From Your Rebuilt RPM ====
The resulting installable RPMs are saved inside '''~/rpmbuild/RPMS/x86_64''' . These can either be installed on the local system, or any other Fedora 25 system that has been prepared to run Kodi. The following step installs Kodi onto the local system, along with any dependencies it has.
<syntaxhighlight lang="bash">
sudo dnf install ~/rpmbuild/RPMS/x86_64/kodi-17*x86_64.rpm
</syntaxhighlight>
 
== Post-Installation Configuration ==
The following steps enable Kodi to be started automatically, and enable things like power management (''e.g.'' so Kodi can properly shutdown the system).
=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2017-01-10T15:43:12Z

Wirerydr: Update status section; remove xorg un-downgrade; add some addt'l nVidia tags

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. The guide shows how to install pre-built packages from RPMFusion (which do not support DVD playback), and alternatively shows how to rebuild the RPMFusion packages with DVD-playback capability enabled. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Jan. 10th, 2016), Kodi 17.x Krypton is in RELEASE-CANDIDATE status. As such this guide utilizes the latest Kodi RC available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== (nVidia) Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== (nVidia) Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== (nVidia) Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-17T15:27:08Z

Wirerydr: Added missing link to Fedora Wayland Changes wiki

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See [https://fedoraproject.org/wiki/Changes/WaylandByDefault this Fedora Wiki page] for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
==== Reversing Any Previous Xorg Downgrade ====
When Fedora 25 was initially released, the latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) was incompatible with version 1.19 of the Xorg X11 X-Windows server that came packaged with Fedora. In order to make things work, this guide originally showed how to downgrade the Xorg X11 X-Windows server to version 1.18 (from Fedora 24). nVidia subsequently released an updated driver (340.101, released Dec. 15th, 2016) that works properly with Xorg 1.19. The following steps will ensure that you are now using the latest Xorg X11 X-Windows server version:
<syntaxhighlight lang="bash">
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then sed --in-place=.bak "s/^exclude\=xorg-x11\*//g" /etc/dnf/dnf.conf; fi'
sudo dnf update
</syntaxhighlight>

=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-16T16:40:51Z

Wirerydr: Minor Restructuring of the X-Windows / Nouveau sections

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
==== Installing the base X-Windows Group ====
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
==== Reversing Any Previous Xorg Downgrade ====
When Fedora 25 was initially released, the latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) was incompatible with version 1.19 of the Xorg X11 X-Windows server that came packaged with Fedora. In order to make things work, this guide originally showed how to downgrade the Xorg X11 X-Windows server to version 1.18 (from Fedora 24). nVidia subsequently released an updated driver (340.101, released Dec. 15th, 2016) that works properly with Xorg 1.19. The following steps will ensure that you are now using the latest Xorg X11 X-Windows server version:
<syntaxhighlight lang="bash">
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then sed --in-place=.bak "s/^exclude\=xorg-x11\*//g" /etc/dnf/dnf.conf; fi'
sudo dnf update
</syntaxhighlight>

=== (nVidia) Removing the Nouveau Driver ===
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-16T16:18:08Z

Wirerydr: Removed Xorg 1.19 -> 1.18 downgrade step (for nVidia 340.x drivers); Added step to upgrade back to 1.19

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
</syntaxhighlight>
 
==== Reversing Any Previous Xorg Downgrade ====
When Fedora 25 was initially released, the latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) was incompatible with version 1.19 of the Xorg X11 X-Windows server that came packaged with Fedora. In order to make things work, this guide originally showed how to downgrade the Xorg X11 X-Windows server to version 1.18 (from Fedora 24). nVidia subsequently released an updated driver (340.101, released Dec. 15th, 2016) that works properly with Xorg 1.19. The following steps will ensure that you are now using the latest Xorg X11 X-Windows server version:
<syntaxhighlight lang="bash">
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then sed --in-place=.bak "s/^exclude\=xorg-x11\*//g" /etc/dnf/dnf.conf; fi'
sudo dnf update
</syntaxhighlight>

==== (nVidia) Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

User talk:Mooninite

2016-12-06T19:57:01Z

Wirerydr: Undo revision 126746 by Wirerydr (talk) Oops - wrong user

'''Welcome to ''Kodi''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User:Ned Scott|Ned Scott]] ([[User talk:Ned Scott|talk]]) 01:09, 8 April 2015 (EDT)

User talk:Klojum

2016-12-06T19:56:21Z

Wirerydr:

Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-06T19:54:58Z

Wirerydr:

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-06T19:54:17Z

Wirerydr: Undo revision 126740 by Klojum (talk) Undone until issues with tty login prompt (after running "systemctl stop kodi") can be resolved

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; echo "exclude=xorg-x11*" >>/etc/dnf/dnf.conf; fi'
</syntaxhighlight>

==== (nVidia) Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

User talk:Mooninite

2016-12-06T17:31:28Z

Wirerydr:

Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

2016-12-06T17:30:52Z

Wirerydr: Undid Klojum's changes until it can be figured out why they cause a tty login to no-longer appear after "systemctl stop kodi"

To [[User:Klojum|Klojum]] ([[User talk:Mooninite|talk]]) - Thank you very much for the "kodi.service" changes re: gettys and plymouth. I did some testing with these changes, and with them I noticed I no longer get a tty login prompt when I do a "systemctl stop kodi". So for now I'm undo'ing your changes, but I will continue to look into this until I figure out what's wrong with the login prompt. Once I've sorted that out I will reinstate your changes accordingly. Thanks again for your contribution!

[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 12:30, 6 December 2016 (EST)

==Guide rewrite==
I am going to be revising a few sections soon.
#Firewall: You can leave it enabled and just open the following ports: TCP: 1151, 8080, and UDP: 1900, 9777
#Pulseaudio: Kodi is fully functional with pulseaudio installed and enabled.
#Systemd service: If you have GDM installed (and autologin enabled) you do not need any of the service script or other changes so it makes this guide much more simple. As the old saying goes: Keep It Simple Stupid.
:[[User:Mooninite|Mooninite]] ([[User talk:Mooninite|talk]]) 09:05, 8 April 2015 (EDT)

#Thanks for the firewall-related tips. I believe the port-list that should be opened will depend on individual circumstances. For example on my standalone setup the kodi.bin process is listening on ports TCP (8080, 1147) and UDP (9777, 1900). Were I to utilize miniDLNA I would have to add TCP port 8200. Airplay can potentially require TCP (80, 443, 554, 3689, 5297, 5289) and UDP (554, 5289, 5353). Given that this is a standalone environment and making custom adjustments to the firewall as services are enabled/disabled is an advanced topic, it seems much simpler to leave the firewall disabled - with the caveats already mentioned in the wiki.
#Pulseaudio still has some deficiencies, such has lacking support for TrueHD or DTS-MA, preventing use of Dolby Pro Logic II, etc. Refer to [[PulseAudio ]]for some further explanation. Actually, the only real advantage Pulseaudio offers is non-exclusive use of the audio subsystem, in cases where you'd like (for example) desktop sounds or other apps to co-exist with Kodi. Since this guide is strongly focused on creating a standalone Kodi environment, Pulseaudio makes little sense to utilize. Given its deficiencies and lack of countervailing advantages, there's no reason to utilize PulseAudio.
#Why would you want GDM to be installed? It's just an unnecessary layer of functionality that introduces complexity but offers little/no benefit. At the very least you'd then have to set up GDM-based auto-login, which is not only extra complexity but a potential security risk. The spirit of this guide is to create a standalone, lightweight installation of Kodi with minimal additional requirements. You are exactly right re: KISS, and introducing a dependency on an unnecessary software layer would seem to contravene this.
You made some earlier edits that removed the section on disabling SELinux. Kodi may have evolved to the point where it can properly function in an SELinux-Enforcing environment, but it used to have issues. I will test in an enforcing environment and update the wiki accordingly. However until I've tested it I will revert your changes to restore the SELinux section.

Thanks again for the tips!
:[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 12:03, 24 April 2015 (EDT)

Hope you don't mind that I added a section for CEC, it was a feature I needed and I thought it may be useful until libcec>=3.0.0 is put into the fedora repos and the rpm in rpmfusion is rebuilt.

:[[User:Slashnull|Slashnull]] ([[User talk:Slashnull|talk]]) 13:46, 15 January 2016 (EDT)

Don't mind at all Slashnull - TYVM for the contribution, and also for maintaining the existing look-and-feel. I may reorder things a bit to avoid CEC users from doing a double install of the generic and then CEC-enabled RPMs, but that's trivial.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 00:20, 18 January 2016 (EST)

Hi Spazticclown - thanks for the video-group contribution. In my experience this is not actually necessary in order to run Kodi as described in this HowTo - not on any version of Fedora from F19 through to the current F23, anyway. I believe as long as the user is in group 'wheel' (which it is as a result of [[HOW-TO:Install Kodi on Fedora 23 using RPMFusion packages#Starting_the_Installation_and_Creating_a_Kodi_User|step 3.3]]), that is sufficient. Just to be sure I took a look at my main kodi box running in my livingroom, and confirmed that user Kodi is not present in group 'video' (gid 39). As such I have reverted back to before your change, but I did want to thank you again for your contribution.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 23:51, 7 February 2016 (EST)

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T20:04:42Z

Wirerydr: Added step to stop DNF updates from upgrading Xorg X11 server up past 1.18 with 340.x series nVidia drivers

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; echo "exclude=xorg-x11*" >>/etc/dnf/dnf.conf; fi'
</syntaxhighlight>

==== (nVidia) Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T18:41:17Z

Wirerydr:

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Krypton)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free''' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; fi'
</syntaxhighlight>

==== (nVidia) Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T16:14:15Z

Wirerydr: Add notice re: Kodi's beta status; update kodi.service file to include required dependency on systemd-user-sessions.service

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
{{bluev|'''NOTE:'''|At present (as of Nov. 30th, 2016), Kodi 17.x Krypton is in BETA status. As such this guide utilizes the latest Kodi beta available from the RPMFusion repository. When Kodi 17.x final has been released and made available in the RPMFusion repository, this guide will be updated accordingly.}}
 
 
 
== Current State of This Guide ==
As of November 30th, 2016, this guide was recently updated (to Fedora 25 and to Kodi 17.x Krypton). It works on the author's system, but more widespread testing by the community is desired before the guide can be labeled "complete".
 
 
This guide has been author-tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Isengard)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== (nVidia) Install Closed-Source Binary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; fi'
</syntaxhighlight>

==== (nVidia) Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver, now that it has been superceded by the closed-source binary nVidia driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T04:52:27Z

Wirerydr: Removed references to the RPMFusion 'nonfree' repsitories

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
This guide is in the middle of being actively re-written (as of Nov. 29th, 2016), and should only be used with caution. In particular, the following version upgrades are being done:
* The reference version of Fedora is being upgraded from 23 to 25.
* The reference version of Kodi is being upgraded from 15.x (Isengard) to 17.x (Krypton).
Once the rewrite is completed, this wiki will be marked as "in-testing" for a period of time to allow for any potential errors to be corrected, after-which it will be marked as "ready-for-use".
 
 
This guide is being tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Isengard)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
</syntaxhighlight>

=== Replace Open-Source Nouveau Video Drivers with Proprietary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

==== Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; fi'
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

File:Fedora 25 Kodi 17 Install 005 - Console Login.png

2016-11-30T04:48:57Z

Wirerydr: Wirerydr uploaded a new version of "File:Fedora 25 Kodi 17 Install 005 - Console Login.png"

File:Fedora 25 Kodi 17 Install 002 - Software Selection.png

2016-11-30T04:48:46Z

Wirerydr: Wirerydr uploaded a new version of "File:Fedora 25 Kodi 17 Install 002 - Software Selection.png"

File:Fedora 25 Kodi 17 Install 005 - Console Login.png

2016-11-30T04:47:50Z

Wirerydr:

File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png

2016-11-30T04:47:34Z

Wirerydr:

File:Fedora 25 Kodi 17 Install 003 - User Creation.png

2016-11-30T04:47:22Z

Wirerydr:

File:Fedora 25 Kodi 17 Install 002 - Software Selection.png

2016-11-30T04:47:07Z

Wirerydr:

HOW-TO:Install Kodi for Linux

2016-11-30T04:42:37Z

Wirerydr: Updated Fedora Howto link to point to new (Fedora 25) version

{{mininav|[[Linux]] {{l2| [[Installation]] }} }}
== Installing Kodi on Ubuntu-based distributions ==
{{warning|Some (later) Ubuntu versions include Kodi built by Ubuntu themselves. If you have installed Ubuntu Kodi, please remove the packages "kodi kodi-bin kodi-data" before trying to install team-xbmc PPA packages.}}

See [[SSH]] or [http://help.ubuntu.com/community/UsingTheTerminal Click here to find out how to use the terminal.]

Use the command line terminal and enter the following commands. Follow the prompts as you would any other software installation.

<syntaxhighlight lang="bash">
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

{{#lst:Team XBMC PPA|repos}}

Note that this PPA only provides builds for Ubuntu i386 and Ubuntu amd64 but not for Ubuntu armhf, which can run on a Raspberry Pi.

=== Installing binary add-ons (PVR, audio decoders, audio encoders, screensavers, visualizations, audio DSP) ===
{{see|Ubuntu binary add-ons}}

=== Installing a development build ===
{{see also|Development builds}}
To install a beta/unstable version of {{kodi}} you must first add the unstable repository, then install XBMC. Use <code>ppa:team-xbmc/xbmc-nightly</code> for nightly builds and <code>ppa:team-xbmc/unstable</code> for [[beta]] builds.

<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/xbmc-nightly
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

Note that if you have any addons (such as PVR clients), these must be updated as well (they will not be updated automatically):
<syntaxhighlight lang="bash">
sudo apt-get install kodi-pvr-mythtv
</syntaxhighlight>

=== Upgrading ===
<section begin="Ubuntu upgrade" />
To update Kodi when a new version is released, just do a general system/package or use the following commands in the terminal (or via [[SSH]]):

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get upgrade
</syntaxhighlight>

{{note|In some cases where additional packages are required, Kodi will fail to upgrade when using the upgrade commands as above. To install additional packages use the command below:

<syntaxhighlight lang="bash">
sudo apt-get dist-upgrade
</syntaxhighlight>}}
<section end="Ubuntu upgrade" />

=== Downgrading to a stable version from a development version ===
If you install a nightly build or an unstable release and want to return to a stable release, follow these instructions:

Find the current PPA you are using:
<syntaxhighlight lang="bash">
sudo apt-cache policy | grep team-xbmc
</syntaxhighlight>

Remove the unstable or nightly PPA where it says '''PPAHERE''':
<syntaxhighlight lang="bash">
sudo add-apt-repository -r ppa:PPAHERE
</syntaxhighlight>

Then restore the stable version with the following commands:
<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get remove kodi kodi-bin
sudo apt-get install kodi
</syntaxhighlight>

=== Downgrading between newer and older stable versions ===
{{incomplete}}

=== Uninstalling ===
If you need to remove and purge an application and finally removing/purging also the application configurations files, do so by using the following commands:

<syntaxhighlight lang="bash" enclose="div">
sudo apt-get update
sudo apt-get remove kodi*
sudo apt-get purge kodi*
</syntaxhighlight>

Then remove the settings folder to remove all settings and library data. This will not delete any videos or music, but just the settings and library data itself:
<syntaxhighlight lang="bash">
rm -r ~/.kodi/
</syntaxhighlight>
or
<syntaxhighlight lang="bash" enclose="div">
rm -r ~/.xbmc/ # for older versions before 14.0
</syntaxhighlight>

== Third Party Repositories ==


The instructions in this section are for unofficial Linux binaries that are un/semi supported by Team Kodi. Most of those binaries use system ffmpeg or even worse totally untested libav, which is not recommended for {{kodi}} as we support ffmpeg only.

=== Debian ===

The installation if you are using Debian (Jessie), you can use the debian-backports repository.

Add the following lines to your /etc/apt/sources.list file, as superuser (sudo)

<syntaxhighlight lang="bash">
# kodi repos
# starting with debian jessie, debian provides kodi via its backports repository
# remember: those packages are not supported by team kodi
deb http://http.debian.net/debian jessie-backports main
</syntaxhighlight>

And then, update APT and install Kodi.

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get install kodi
</syntaxhighlight>

Enjoy your new Kodi.

=== Fedora ===
Refer to [[HOW-TO:Install Kodi on Fedora 25 using RPMFusion packages]] for a guide showing how to install Fedora 25 and Kodi to create a quick-booting, standalone style of media player.

=== OpenELEC ===
{{main|OpenELEC}}
{{#lst:OpenELEC|intro}}

=== KodiBuntu ===
The installation instructions on this page are intended for people who already have a Linux-based OS setup, or wish to do their own installation of Linux. Alternatively you can try out [[KodiBuntu]], which will install both an OS and {{kodi}} with an easy installer.

{{main|KodiBuntu}}
{{#lst:KodiBuntu|intro}}

=== Raspbian ===
{{see also|HOW-TO:Install Kodi on Raspberry Pi}}
Installing on Raspbian is done with:

<syntaxhighlight lang="bash">
sudo apt-get install kodi
</syntaxhighlight>

Upgrading on Raspbian is done with:

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get upgrade
</syntaxhighlight>

At the moment the build in Raspbian are outdated. At the moment only http://michael.gorven.za.net offers prebuild packages.

== Installation from source ==
If distribution packages are not available, or you need a newer version, or specific features enabled, then you will most likely need to compile from source. While compiling from source does not differ very much between distributions (except for installation of build dependencies), a few different guides are available in this wiki.

* [[HOW-TO compile XBMC for Linux from source code]]
* [[HOW-TO compile XBMC for Linux on Debian/Ubuntu]] - This is a tutorial on how to compile and install {{kodi}} on Debian and Ubuntu.

== See also ==
* [[Linux]]
* [[HOW-TO:Autostart XBMC for Linux]]
*[[JeOS implementations for Kodi]]

* [[Linux FAQ]]

{{Updated|16}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]
[[Category:Manual]]

Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T04:39:11Z

Wirerydr: Wirerydr moved page HOW-TO talk:Install Kodi on Fedora 23 using RPMFusion packages to HOW-TO talk:Install Kodi on Fedora 25 using RPMFusion packages: Updated to reference Fedora 25 (previously referenced Fedora 23)

==Guide rewrite==
I am going to be revising a few sections soon.
#Firewall: You can leave it enabled and just open the following ports: TCP: 1151, 8080, and UDP: 1900, 9777
#Pulseaudio: Kodi is fully functional with pulseaudio installed and enabled.
#Systemd service: If you have GDM installed (and autologin enabled) you do not need any of the service script or other changes so it makes this guide much more simple. As the old saying goes: Keep It Simple Stupid.
:[[User:Mooninite|Mooninite]] ([[User talk:Mooninite|talk]]) 09:05, 8 April 2015 (EDT)

#Thanks for the firewall-related tips. I believe the port-list that should be opened will depend on individual circumstances. For example on my standalone setup the kodi.bin process is listening on ports TCP (8080, 1147) and UDP (9777, 1900). Were I to utilize miniDLNA I would have to add TCP port 8200. Airplay can potentially require TCP (80, 443, 554, 3689, 5297, 5289) and UDP (554, 5289, 5353). Given that this is a standalone environment and making custom adjustments to the firewall as services are enabled/disabled is an advanced topic, it seems much simpler to leave the firewall disabled - with the caveats already mentioned in the wiki.
#Pulseaudio still has some deficiencies, such has lacking support for TrueHD or DTS-MA, preventing use of Dolby Pro Logic II, etc. Refer to [[PulseAudio ]]for some further explanation. Actually, the only real advantage Pulseaudio offers is non-exclusive use of the audio subsystem, in cases where you'd like (for example) desktop sounds or other apps to co-exist with Kodi. Since this guide is strongly focused on creating a standalone Kodi environment, Pulseaudio makes little sense to utilize. Given its deficiencies and lack of countervailing advantages, there's no reason to utilize PulseAudio.
#Why would you want GDM to be installed? It's just an unnecessary layer of functionality that introduces complexity but offers little/no benefit. At the very least you'd then have to set up GDM-based auto-login, which is not only extra complexity but a potential security risk. The spirit of this guide is to create a standalone, lightweight installation of Kodi with minimal additional requirements. You are exactly right re: KISS, and introducing a dependency on an unnecessary software layer would seem to contravene this.
You made some earlier edits that removed the section on disabling SELinux. Kodi may have evolved to the point where it can properly function in an SELinux-Enforcing environment, but it used to have issues. I will test in an enforcing environment and update the wiki accordingly. However until I've tested it I will revert your changes to restore the SELinux section.

Thanks again for the tips!
:[[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 12:03, 24 April 2015 (EDT)

Hope you don't mind that I added a section for CEC, it was a feature I needed and I thought it may be useful until libcec>=3.0.0 is put into the fedora repos and the rpm in rpmfusion is rebuilt.

:[[User:Slashnull|Slashnull]] ([[User talk:Slashnull|talk]]) 13:46, 15 January 2016 (EDT)

Don't mind at all Slashnull - TYVM for the contribution, and also for maintaining the existing look-and-feel. I may reorder things a bit to avoid CEC users from doing a double install of the generic and then CEC-enabled RPMs, but that's trivial.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 00:20, 18 January 2016 (EST)

Hi Spazticclown - thanks for the video-group contribution. In my experience this is not actually necessary in order to run Kodi as described in this HowTo - not on any version of Fedora from F19 through to the current F23, anyway. I believe as long as the user is in group 'wheel' (which it is as a result of [[HOW-TO:Install Kodi on Fedora 23 using RPMFusion packages#Starting_the_Installation_and_Creating_a_Kodi_User|step 3.3]]), that is sufficient. Just to be sure I took a look at my main kodi box running in my livingroom, and confirmed that user Kodi is not present in group 'video' (gid 39). As such I have reverted back to before your change, but I did want to thank you again for your contribution.
:Cheers... [[User:Wirerydr|Wirerydr]] ([[User talk:Wirerydr|talk]]) 23:51, 7 February 2016 (EST)

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T04:39:09Z

Wirerydr: Wirerydr moved page HOW-TO:Install Kodi on Fedora 23 using RPMFusion packages to HOW-TO:Install Kodi on Fedora 25 using RPMFusion packages: Updated to reference Fedora 25 (previously referenced Fedora 23)

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
This guide is in the middle of being actively re-written (as of Nov. 29th, 2016), and should only be used with caution. In particular, the following version upgrades are being done:
* The reference version of Fedora is being upgraded from 23 to 25.
* The reference version of Kodi is being upgraded from 15.x (Isengard) to 17.x (Krypton).
Once the rewrite is completed, this wiki will be marked as "in-testing" for a period of time to allow for any potential errors to be corrected, after-which it will be marked as "ready-for-use".
 
 
This guide is being tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Isengard)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
sudo dnf config-manager --set-enabled rpmfusion-nonfree-updates-testing
</syntaxhighlight>

=== Replace Open-Source Nouveau Video Drivers with Proprietary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

==== Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; fi'
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]

Archive:Install Kodi on Fedora 26 using RPMFusion packages

2016-11-30T04:36:50Z

Wirerydr:

{{mininav| [[Installing]] | [[Linux]] }}
{{see also|Linux FAQ}}
<section begin="intro" />This page presents an approach to turning a minimal installation of Fedora 25 into a standalone Kodi 17.x (Krypton) installation, with minimal additional software / overhead. The Kodi packages available from RPMFusion are used as the basis for this setup. At the end of this guide you will have a set-top box style of system that, when powered up, will quickly boot and then start Kodi automatically without intervention (''e.g.'' no need to first log in).<section end="intro" />
 
 
 
== Current State of This Guide ==
This guide is in the middle of being actively re-written (as of Nov. 29th, 2016), and should only be used with caution. In particular, the following version upgrades are being done:
* The reference version of Fedora is being upgraded from 23 to 25.
* The reference version of Kodi is being upgraded from 15.x (Isengard) to 17.x (Krypton).
Once the rewrite is completed, this wiki will be marked as "in-testing" for a period of time to allow for any potential errors to be corrected, after-which it will be marked as "ready-for-use".
 
 
This guide is being tested on the following hardware/software:
<section begin="Testing" />
{| class="prettytable" style="background-color:#FFFFFF;"
! OS
| [https://getfedora.org/en/server Fedora 25 Server (x86_64)]
|-
! Kodi
| [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/kodi.html Kodi v17.0 Beta 5 (Isengard)] from the [http://download1.rpmfusion.org/free/fedora/updates/25/x86_64/repoview/index.html rpmfusion-free-updates] repository
|-
! Motherboard
| [http://www.gigabyte.com/products/product-page.aspx?pid=4716 Gigabyte GA-F2A88XM-D3H (rev 3.0)]
|-
! CPU
| [http://www.amd.com/en-us/products/processors/desktop/a-series-apu#2 AMD A6-5400K dual-core 3.8GHz 65W]
|-
! Memory
| [http://www.corsair.com/en-us/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1600c9 Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz PC12800]
|-
! Graphics
| [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]
|-
! Disk
| [http://www.wdc.com/global/products/specs/?driveID=792&language=1 Western Digital 1TB 7200RPM Black HDD]
|-
! Case
| [http://www.antec.com/pdf/manuals/Fusion%20Remote%20&%20Fusion%20Remote%20Black_EN%20manual.pdf Antec Fusion Remote Black HTPC Case]
|-
! Receiver
| [http://usa.denon.com/us/product/HomeTheater/AVReceiversHT/AVR3808CI Denon AVR-3808ci]
|-
! TV
| [http://shop.panasonic.com/shop/model/TH-50PZ800U# Panasonic 50" VIERA TH-50PZ800U Plasma]
|}<section end="Testing" />

 
 
== Assumptions ==
# This guide assumes you have at least a slight familiarity with Linux in general. If you know what a Bash shell is, can cut-and-paste commands, and are comfortable editing files with VI or Emacs, then you should be fine.
# It is assumed that Kodi will be installed into a freshly-installed Fedora 25 Server (x86_64) environment that was set up with no additional software specified. If you already have such an environment then you can skip the steps showing how to do a fresh-install of Fedora.
# This guide was written with the use of an nVidia-based graphics card in-mind, (tested with an [http://www.asus.com/Graphics_Cards/ENGT240_SILENTDI1GD3/ Asus ENGT240 Silent GT240 fanless PCI-E 2.0 card]). If you have an AMD, Intel or other graphics solution, then either skip the nVidia-specific steps or substitute your own. Also, this guide covers replacing the open-source Nouveau (open-source) video drivers that come included in Fedora with closed-source binary drivers drivers from nVidia (as obtained from Negativo17's nVidia repository) for improved performance. You can skip this if you'd prefer, although your performance mileage may vary.
# It is assumed that audio will be passed via the HDMI port on your video card / motherboard to your TV / sound-system. Kodi can certainly handle other methods of passing audio, however those are beyond the scope of this article.
# Everything is done with the goal of minimizing how many software packages / dependencies are required. For example, since Kodi will be run as a fullcreen application, there is no need for heavyweight desktop environments such as Gnome and KDE, and all the apps/clutter they introduce.
# In order to make things simpler, this guide disables both SELinux and the local firewalld daemon. Ensure that the system is adequately protected by things like your internet router's firewall, and encrypted/passworded WiFi (you DO have your WiFi protected, right?...)
# As of release 25, Fedora comes in three flavours: [https://getfedora.org/en/workstation Workstation], [https://getfedora.org/en/server Server], and [https://getfedora.org/en/atomic Atomic]. This guide installs the '''Server edition''' (with no additional software specified) in order to get the leanest, most minimal install possible. At the time of writing, when tested this installation consumed approximately 410MB of memory (excluding buffers / cache) when playing a 1080p 5.1-channel video. The full installation including Fedora, Kodi and a modest library of thumbnails/artwork consumed about 9GB of disk space. For the purposes of testing, a 20GB partition was used.
 
== Installing Fedora 25 ==

=== Obtaining the Fedora 25 Server (x86_64) Installation Image ===
Visit the Fedora 25 (Server) download page at https://getfedora.org/en/server/download/ , and click the '''download''' button to start your download. Once your download has completed, burn the '''.iso''' image you just downloaded to a DVD. It's also possible to create an installable USB flash drive with this ISO and install from it, or even to perform a network install without having any local DVD media, but these are outside the scope of this guide.
 
 
[[File:Fedora 25 Kodi 17 Install 001 - Main Screen.png|right|500px|Fedora Installation Main Installation Screen]]
=== Configure How Fedora will be Installed ===
Boot from the DVD you just created. If necessary, bring up your BIOS's boot-menu by pressing <F12> (or whatever your BIOS uses) to select booting from your optical drive. When the DVD boots you will be shown a text-menu with several options. Select "Install", and proceed. The system will then boot up into Fedora's graphical installer (Anaconda). Choose your desired keyboard layout and language, and proceed. You will then be shown Anaconda's main installation screen, similar to this:
 
 
You can make whatever choices you like for everything in the '''LOCALIZATION''' and '''SYSTEM''' sections.
 
 
Ensure that the '''INSTALLATION SOURCE''' section is set to ''Local Media''. If not then click to enter it, and change it accordingly.
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 002 - Software Selection.png|right|500px|Fedora Installation Software Selection Screen]]
Within the '''SOFTWARE SELECTION''' section:
# Ensure that '''Base Environment''' in the left-pane is set to ''Fedora Custom Operating System'' (equivalent to ''Minimal Install'' in previous Fedora versions).
# Ensure that ''none'' of the add-ons in the right-hand pane are selected.
When correctly set, this screen should look as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 003 - User Creation.png|right|500px|Fedora User-Creation Screen]]
=== Starting the Installation and Creating a Kodi User ===
When finished setting up all desired installation options, Begin the install.

During installation, set the password for user '''root''' by clicking '''''ROOT PASSWORD'''''). You should also create the non-privileged user that Kodi will run as - click '''''USER CREATION'''''. You can choose whatever full-name / username / password you'd like; this guide assumes a username of 'kodi'. When creating this account, check '''''Make this user administrator'''''. (Note: This user isn't granted superuser rights directly; rather it can run privileged commands via tools such as '''''sudo'''''.)
 
The User Creation screen should looks as follows:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 004 - Install In Progress.png|right|500px|Fedora Installation In-Progress]]
Once you've finished with these two settings, installation will continue. The installation screen should look similiar to:
{{-}}
 
 
[[File:Fedora 25 Kodi 17 Install 005 - Console Login.png|right|500px|Fedora Console Login]]
=== Rebooting into Fedora ===

When the installation has completed, remove the installation DVD and click '''''REBOOT''''' to restart the system. The system should reboot and reach a textmode console login screen, as shown below. If you reach this point then you've successfully finished a minimal install of Fedora 25.
{{-}}

== Configuring Fedora / Installing Dependencies ==

Now that Fedora is installed, some configuration needs to be performed, and some dependencies need to be installed and configured.

{{redv|'''IMPORTANT:'''|Unless otherwise mentioned, all following commands should be run as user '''''kodi'''''. Elevated privileges will be obtained via '''''sudo''''' if required.}}

=== A Quick Note About DNF vs YUM, Updating Packages To Latest Versions, and Rebooting ===
{{bluev|'''NOTE:'''|Back in Fedora 22, the YUM package-manager was replaced by DNF. DNF is highly backward-compatible, and uses a nearly (but not completely) identical command syntax. In practice you may choose to either continue typing in 'yum' commands (which are passed off transparently to DNF), or use 'dnf' commands directly. This HOWTO standardizes on using 'dnf', but you may choose 'yum' instead if you prefer.}}

Perform a full update of all installed packages (including the kernel if necessary).
<syntaxhighlight lang="bash">
sudo dnf update
</syntaxhighlight>
When you're ready, reboot the system after these steps have completed for changes to take effect (especially any Kernel updates that may have happened).
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Setting SELinux to Permissive Mode, and Disabling Firewalld ===
'''SELinux''' is a part of the kernel that enforces access control over many parts of the system, including filesystems, processes, sockets, etc. Although Kodi can be made to operate with SELinux active, that is beyond the scope of this guide. Instead, SELinux left active but set to '''permissive mode'''. It could also be completely deactivated, but then the entire filesystem would require re-labeling should you later decide to turn SELinux back on.

'''Firewalld''' is the local firewall daemon that is included by-default with recent Fedora releases. Because it can interfere with things such as uPnP, file-sharing, remote-control apps, etc., firewalld is disabled in this guide.
{{redv|'''WARNING:'''|If your system is in any way exposed to the internet or other untrusted zones, then it is recommended to ensure those zones are adequately protected by their own firewalls before disabling this system's local firewalld.}}

Terminate firewalld if it is running, and then remove it from the system permanently. This will also trigger removal of some additional, dependent packages, which are not necessary to the operation of Kodi.
<syntaxhighlight lang="bash">
sudo systemctl stop firewalld
sudo dnf remove firewalld
</syntaxhighlight>

Next, reconfigure SELinux to change its policy from ''enforcing'' to ''permissive''.
<syntaxhighlight lang="bash">
sudo sed --in-place=.bak 's/^SELINUX\=enforcing/SELINUX\=permissive/g' /etc/selinux/config
</syntaxhighlight>

'''''You will need to reboot afterwards for these two changes to completely take effect'''''.
<syntaxhighlight lang="bash">
sudo systemctl reboot
</syntaxhighlight>

=== Enable Use Of the RPMFusion Repository ===
[http://rpmfusion.org/ RPMFusion] is a set of 3rd-party repositories providing legally redistributable software (including Kodi) which, for one reason or another, is not included in Fedora distributions. This includes a '''free''' repository containing open-source software, and a '''non-free' repository containing redistributable software that is not open-source. Only the '''free''' repository is required by Kodi. The '''release''', '''updates''', and '''updates-testing''' variants of the free repository for Fedora 25 will be installed and enabled.
<syntaxhighlight lang="bash">
sudo dnf install --nogpgcheck \
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
sudo dnf config-manager --set-enabled rpmfusion-nonfree-updates-testing
</syntaxhighlight>

=== Replace Open-Source Nouveau Video Drivers with Proprietary nVidia Drivers ===
Although the open-source Nouveau drivers that come with Fedora have made great strides recently, the closed-source binary drivers from nVidia still offer better performance/features. There are a variety of places to obtain these binary drivers, including from RPMFusion, however this guide shows how to install them from the [http://negativo17.org/nvidia-driver/ Negativo17 nVidia repository].

{{bluev|'''NOTE:'''|There are several catetories of nVidia driver releases, of-which two are used by this guide: '''Short-Lived''' and '''Legacy 340.x'''. The Short-Lived drivers are for users with modern video cards who want rapidly-emerging features/fixes. The Legacy-340.x drivers are for users of older generations of nVidia video cards (such as the author's GT240-based card). Depending on how old your card is, you may need to use the 340.x series of driver. Refer to [http://www.nvidia.com/object/IO_32667.html this nVidia article] to see if your video card requires you to stick with 340.x series drivers, or if you can use the Short-Lived drivers. Negativo17 provides separate repositories for each, and this guide shows how to install either.}}

==== Enabling the Legacy 340.x nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Legacy 340.x series''' nVidia driver for older video cards (cannot mix with the Short-Lived series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia-340.repo
</syntaxhighlight>

==== Enabling the Short-Lived nVidia Driver Repository ====
{{redv|'''IMPORTANT:'''|Only perform this step if you want the '''Short-Lived''' nVidia driver for modern video cards (cannot mix with the Legacy 340.x series).}}
<syntaxhighlight lang="bash">
sudo dnf config-manager --add-repo http://negativo17.org/repos/fedora-nvidia.repo
</syntaxhighlight>

==== Installing the Selected nVidia Driver ====
The following will install your selected nVidia drivers along with VDPAU (hardware-accelerated video decoding and postprocessing) support.
<syntaxhighlight lang="bash">
sudo dnf install \
nvidia-driver \
nvidia-settings \
kernel-devel \
dkms-nvidia \
libva-utils \
libva-vdpau-driver \
vdpauinfo
</syntaxhighlight>

==== Removing the Nouveau Driver ====
Next, remove the open-source Nouveau driver.
<syntaxhighlight lang="bash">
sudo dnf remove xorg-x11-drv-nouveau
</syntaxhighlight>

=== Install Basic X-Windows Support ===
Kodi requires a functioning X-Windows Server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any desktop environments such as Gnome or KDE; It also does not require their display managers (GDM and KDM respectively). In this guide, only a basic X-Windows system is installed.
{{bluev|'''NOTE:'''|In Fedora 25, the default GDM session (and corresponding X-Server) has been changed from Xorg X11 to Wayland. (See http:// this note for more information.) In theory this should work for most (if not all) applications when running under Gnome. However this guide configures Kodi to run in standalone mode without utilizing either GDM or Gnome. Since Kodi is not (yet, at least) compatible with Wayland, the traditional Xorg X11 X-Server is used instead. If a method can be devised to run Kodi in standalone mode directly under Wayland, then this Wiki will be updated accordingly.}}
 
{{redv|'''IMPORTANT:'''|The latest 340.x driver available from nVidia (340.98 as of Nov. 29th, 2016) is incompatible with the newly-released version 1.19 of the Xorg X11 X-Windows server that comes packaged with Fedora. In order to resolve this incompatibility, when the 340.x drivers are present the Xorg X11 X-Windows server will be downgraded to the 1.18 version from Fedora 24. Once nVidia releases a new and working 340.x driver, this Wiki will be updated accordingly.}}
The following commands install a basic X-Windows setup.
{{bluev|'''NOTE:'''|This will '''''not''''' cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.}}
<syntaxhighlight lang="bash">
sudo dnf groupinstall "base-x"
sudo sh -c 'if dnf list installed nvidia-driver | grep -q fedora-nvidia-340; then dnf --releasever=24 downgrade xorg-x11-server-Xorg --allowerasing; fi'
</syntaxhighlight>

=== Enabling Kodi Audio and Accelerated Video Within X-Windows ===
In order for the Kodi user-account to be able to use produce audio and accelerated video within the X-Windows system, it must be added to the '''''audio''''' and '''''video''''' user-groups.
<syntaxhighlight lang="bash">
sudo usermod kodi -a -G audio
sudo usermod kodi -a -G video
</syntaxhighlight>

== Installing Kodi And Configuring It To Run Automatically ==

=== Installing Kodi from the RPMFusion repository ===
The following command actually installs Kodi from the RPMFusion repository. Any dependencies that Kodi requires but are not yet installed will also be included automatically.
<syntaxhighlight lang="bash">
sudo dnf install kodi
</syntaxhighlight>

=== Create Systemd Service File For X-Windows / Kodi ===
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it is a manually-customized service file that was not installed as part of any package, it gets placed in '''''"/etc/systemd/system"''''' instead of '''''"/lib/systemd/systemd"'''''.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target

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

[Install]
WantedBy = multi-user.target
ENDcat'
</syntaxhighlight>

=== Install DBUS addon for X-Windows ===
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the ''/usr/bin/dbus-launch'' tool within in the Systemd service file from the previous step.
<syntaxhighlight lang="bash">
sudo dnf install dbus-x11
</syntaxhighlight>

=== Load and Enable New Systemd Service File ===
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
<syntaxhighlight lang="bash">
sudo systemctl daemon-reload
sudo systemctl enable kodi
</syntaxhighlight>

=== Reconfigure PolicyKit To Enable Poweroff, Suspend and Similiar Functions ===
In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
ENDcat'
</syntaxhighlight>

=== Install UPower ===
UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
<syntaxhighlight lang="bash">
sudo dnf install upower
</syntaxhighlight>

=== Configure Xwrapper To Allow Non-Console Users To Start X-Server ===
In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
<syntaxhighlight lang="bash">
sudo bash -c 'cat <<"ENDcat" >/etc/X11/Xwrapper.config
allowed_users = anybody
ENDcat'
sudo chmod 644 /etc/X11/Xwrapper.config
</syntaxhighlight>

== All Finished, and Last Tips ==
If all has gone well thus far, then the next time you restart the system it should boot all the way into Kodi (fullscreen standalone) without needing to log in first, or perform any other intervention. At this point you should be able to commence configuring your minimal Kodi install as desired. Enjoy!

# As previously mentioned, this method of installing Kodi avoids the need to log into the system for normal operation. However you may still reach the system remotely via '''''SSH''''', whether or not Kodi is running at the time.
# If you have remotely accessed the system, then Kodi can be easily started / stopped with the following two commands (run as user '''''kodi'''''):

<syntaxhighlight lang="bash">
sudo systemctl start kodi
</syntaxhighlight>

<syntaxhighlight lang="bash">
sudo systemctl stop kodi
</syntaxhighlight>

{{Updated|17}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]