[yugo]

Hello,

I have installed kodi on fedora 26, following more or less the how-to. Thanks for it.

Instead of uninstalling firewalld, I opened port 8080.

Code:

firewallctl zone --permanent FedoraServer add rich-rule 'rule family="ipv4" source address="192.168.0.0/24" port port="8080" protocol="tcp" accept'

This was enough for the remote server and for kore to work.

[wirerydr]

Hello,

I have installed kodi on fedora 26, following more or less the how-to. Thanks for it.

Thanks for the feedback, yugo - glad the Wiki was useful for you. I will be updating it for Fedora 26 in the near future. I was holding off until I could finish exploring whether I could get get the nascent Wayland fork of Kodi (PKerling's GSoC 2017 project) up and running on Fedora 26 without a full-blown Gnome desktop setup. I'm finding this more difficult to achieve than I had originally hoped, so I'll update the Wiki with Fedora 26 under tried-and-true X11 for now.

Instead of uninstalling firewalld, I opened port 8080.

Code:

firewallctl zone --permanent FedoraServer add rich-rule 'rule family="ipv4" source address="192.168.0.0/24" port port="8080" protocol="tcp" accept'

This was enough for the remote server and for kore to work.

Seems reasonable. If you're not worried about things like SMB, NFS, AirPlay, miniDLNA, etc., then TCP on port 8080 should be fine. When updating the Wiki for F26 I'll add this in for those who only care about remote-control / web-control. Actually, I suppose eventually I should take a closer look at whether or not packages like Samba automatically open up the firewall appropriately during their installation scripts...

Thanks, yugo.

[wirerydr]

The Wiki has been updated for Fedora 26, and also incorporates yugo's suggestion above about only enabling TCP port 8080 (for Kodi remote-control) instead of fully disabling Firewalld (thanks again).

Cheers - Wire

[wirerydr]

The wiki has been updated from Kodi 17.3 to 17.4.

Cheers - WireRydr

[erqiyang]

Hi, Thanks for your guide. It's easy to follow and will most of the time get things to work.

I've recently re-installed my entire box again (for various reasons), and installed Fedora 26 server with Kodi 17.5 from the rpmfusion repo.

My box is connected to the TV through hdmi, and I have a cec box in between from eight-pulse.

The problem now is, the audio does not play when I select the output to the TV. 

I installed the alsa-utils and ran a speaker-test command, and I can get the sound from the TV, so the set-up must be correct. (Additionally, this was a working set-up before my hands got itchy... )

the aplay -l output is here:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


i'm pretty sure it's a software issue, but have ran out of idea after spending the past 1 week searching the net for solution. (plus, I am also sure I found the fix previously, but cannot recall it now).

Any idea how this can be rectified?

[wirerydr]

Hi, Thanks for your guide. It's easy to follow and will most of the time get things to work.

I've recently re-installed my entire box again (for various reasons), and installed Fedora 26 server with Kodi 17.5 from the rpmfusion repo.

My box is connected to the TV through hdmi, and I have a cec box in between from eight-pulse.

The problem now is, the audio does not play when I select the output to the TV. 

I installed the alsa-utils and ran a speaker-test command, and I can get the sound from the TV, so the set-up must be correct. (Additionally, this was a working set-up before my hands got itchy... )

 Itchy hands definitely help to keep life interesting.  Without debug logs, system logs, etc. however, the best I can probably offer are a few suggestions, in decreasing order of likelihood:

1. Double-check in Kodi that you're using the correct Alsa card/device.  In my case, under Settings -> System -> Audio -> Audio Output Device  I have 4 devices listed (all from the same HDMI card), and the 2nd one is what works for me.  Kodi will probably default to using the 1st enumerated device unless you specify otherwise, and that might not be right for you.
   
2. Make sure you don't have Kodi muted / volume'ed down.  I haven't seen it often recently, but upon occasion I've discovered that a fresh install of Kodi will have no volume until I manually increase it and/or enable passthrough (which I always do after fresh installs since I'm using an A/V receiver that can decode all of the most common formats).
   
3. Ensure that you've added whatever user you're running Kodi as to the audio group as indicated in the wiki.
   
4. Double-check that Alsa itself isn't muted, at least on the specific channel you need.  alsamixer is one tool you can use to control this.
   
5. I think you mentioned connecting your Kodi box to a TV with a CEC box in the middle.  Presumably there is no A/V receiver involved.  In this case double-check that you're not trying to test with an audio format that your TV cannot support.  E.g. with passthrough enabled, playing media with a DTS-HD or Dolby TrueHD audio track when your TV can only accept PCM.
   
6. Try testing your setup without the CEC box.  I doubt this is actually the problem, but it's worth ruling out.
   

Failing that, take a look at your kodi logs ( found in $HOME/.kodi/temp ) and see if any audio-related errors / weirdness show up.  I'd suggest first doing this right after powering up Kodi, and if that looks good then again after attempting to play some media.  If you're willing to wade through more data then do this with debugging enabled.

Sorry I can't be more help off the top of my head.  Best of luck, and let us know how this turns out for you!

[erqiyang]

Hi, Thanks for your guide. It's easy to follow and will most of the time get things to work.

I've recently re-installed my entire box again (for various reasons), and installed Fedora 26 server with Kodi 17.5 from the rpmfusion repo.

My box is connected to the TV through hdmi, and I have a cec box in between from eight-pulse.

The problem now is, the audio does not play when I select the output to the TV. 

I installed the alsa-utils and ran a speaker-test command, and I can get the sound from the TV, so the set-up must be correct. (Additionally, this was a working set-up before my hands got itchy... )

 Itchy hands definitely help to keep life interesting.  Without debug logs, system logs, etc. however, the best I can probably offer are a few suggestions, in decreasing order of likelihood:

1. Double-check in Kodi that you're using the correct Alsa card/device.  In my case, under Settings -> System -> Audio -> Audio Output Device  I have 4 devices listed (all from the same HDMI card), and the 2nd one is what works for me.  Kodi will probably default to using the 1st enumerated device unless you specify otherwise, and that might not be right for you.
   
2. Make sure you don't have Kodi muted / volume'ed down.  I haven't seen it often recently, but upon occasion I've discovered that a fresh install of Kodi will have no volume until I manually increase it and/or enable passthrough (which I always do after fresh installs since I'm using an A/V receiver that can decode all of the most common formats).
   
3. Ensure that you've added whatever user you're running Kodi as to the audio group as indicated in the wiki.
   
4. Double-check that Alsa itself isn't muted, at least on the specific channel you need.  alsamixer is one tool you can use to control this.
   
5. I think you mentioned connecting your Kodi box to a TV with a CEC box in the middle.  Presumably there is no A/V receiver involved.  In this case double-check that you're not trying to test with an audio format that your TV cannot support.  E.g. with passthrough enabled, playing media with a DTS-HD or Dolby TrueHD audio track when your TV can only accept PCM.
   
6. Try testing your setup without the CEC box.  I doubt this is actually the problem, but it's worth ruling out.
   

Failing that, take a look at your kodi logs ( found in $HOME/.kodi/temp ) and see if any audio-related errors / weirdness show up.  I'd suggest first doing this right after powering up Kodi, and if that looks good then again after attempting to play some media.  If you're willing to wade through more data then do this with debugging enabled.

Sorry I can't be more help off the top of my head.  Best of luck, and let us know how this turns out for you! 

Thanks. I've actually gone through step 1 - 5 that you mentioned. Literally nothing works. I can try step 6 again over this weekend maybe, but like you mentioned, I highly doubt it's a problem.

I've also stopped Kodi and ran speaker-test independently from the CLI, and it can send sound to the TV.  Additionally, I've scoured through all the debug logs in $HOME/.kodi/temp, and there's no error related to sound at all. I've also gone as far as to look at the linux log, and there's absolutely no error. (I can probably try to post the logs again this weekend if I haven't solve it by then).

It seems to me that the sound signal is being blackholed somewhere. :-(

You can rest assured that if I ever find the solution, I'll definitely post it here for my future reference as well.

[erqiyang]

Hi, Thanks for your guide. It's easy to follow and will most of the time get things to work.

I've recently re-installed my entire box again (for various reasons), and installed Fedora 26 server with Kodi 17.5 from the rpmfusion repo.

My box is connected to the TV through hdmi, and I have a cec box in between from eight-pulse.

The problem now is, the audio does not play when I select the output to the TV. 

I installed the alsa-utils and ran a speaker-test command, and I can get the sound from the TV, so the set-up must be correct. (Additionally, this was a working set-up before my hands got itchy... )

 Itchy hands definitely help to keep life interesting.  Without debug logs, system logs, etc. however, the best I can probably offer are a few suggestions, in decreasing order of likelihood:

1. Double-check in Kodi that you're using the correct Alsa card/device.  In my case, under Settings -> System -> Audio -> Audio Output Device  I have 4 devices listed (all from the same HDMI card), and the 2nd one is what works for me.  Kodi will probably default to using the 1st enumerated device unless you specify otherwise, and that might not be right for you.
   
2. Make sure you don't have Kodi muted / volume'ed down.  I haven't seen it often recently, but upon occasion I've discovered that a fresh install of Kodi will have no volume until I manually increase it and/or enable passthrough (which I always do after fresh installs since I'm using an A/V receiver that can decode all of the most common formats).
   
3. Ensure that you've added whatever user you're running Kodi as to the audio group as indicated in the wiki.
   
4. Double-check that Alsa itself isn't muted, at least on the specific channel you need.  alsamixer is one tool you can use to control this.
   
5. I think you mentioned connecting your Kodi box to a TV with a CEC box in the middle.  Presumably there is no A/V receiver involved.  In this case double-check that you're not trying to test with an audio format that your TV cannot support.  E.g. with passthrough enabled, playing media with a DTS-HD or Dolby TrueHD audio track when your TV can only accept PCM.
   
6. Try testing your setup without the CEC box.  I doubt this is actually the problem, but it's worth ruling out.
   

Failing that, take a look at your kodi logs ( found in $HOME/.kodi/temp ) and see if any audio-related errors / weirdness show up.  I'd suggest first doing this right after powering up Kodi, and if that looks good then again after attempting to play some media.  If you're willing to wade through more data then do this with debugging enabled.

Sorry I can't be more help off the top of my head.  Best of luck, and let us know how this turns out for you!  

Thanks. I've actually gone through step 1 - 5 that you mentioned. Literally nothing works. I can try step 6 again over this weekend maybe, but like you mentioned, I highly doubt it's a problem.

I've also stopped Kodi and ran speaker-test independently from the CLI, and it can send sound to the TV.  Additionally, I've scoured through all the debug logs in $HOME/.kodi/temp, and there's no error related to sound at all. I've also gone as far as to look at the linux log, and there's absolutely no error. (I can probably try to post the logs again this weekend if I haven't solve it by then).

It seems to me that the sound signal is being blackholed somewhere. :-(

You can rest assured that if I ever find the solution, I'll definitely post it here for my future reference as well. 

 Ok. I've gotten it to work. And I think it's also a mistake on my part. What happened was I had copied the $HOME/.kodi directory as a back-up from the old to the new installation, thinking that it should work. However, I forgotten that I was actually using pulseaudio from the old set-up. So when I got it booted up the first time, I couldn't hear any sound from the TV (I was actually only testing the GUI Sound at this point). 

In the old set-up, my sound was to 5.1, but it will not work in ALSA, since my TV only takes in 2 channel. Since the GUI Sound doesn't generate any log at all, I really couldn't see what's happening. So I tried to generate some log to show you by playing some video (hoping some error message will show up). To be honest, a bunch of logs, but no error on them as well. But hey, the audio playback was through the TV this time round. Still, the GUI Sound is not playing at all, and it's kind of irritating for me because I'm very used to them.

In desperation, I actually navigated to the folder where the GUI sound wave file was located (/usr/share/kodi/addons/resource.uisounds.kodi/resources/) to manually play them through kodi. None of the file could play through kodi at all. I ran the file through the speaker-test command (speaker-test -c 2 -D hw:0,8 -r 44100 -t wav -w /usr/share/kodi/addons/resource.uisounds.kodi/resources/back.wav) and got a bunch of error rejecting the wave files due to channel count and/or sample rate etc.

Eventually, I looked up the old configuration (that I had backed-up), and under the guisettings.xml, I found the holy grail. (<audiodevice>PULSE:alsa_output.hw_0_8</audiodevice>). I was using PulseAudio all along. *facepalm*

Interestingly, even with PulseAudio installed and running, it wasn't giving output to the TV speaker, so I added a file at $HOME/.asoundrc with the following config:

defaults.pcm.!card 0
defaults.ctl.!card 0
defaults.pcm.!device 8
defaults.ctl.!device 8

That makes the audio device as the default pulse audio device for output. And solves everything.

tldr? 

1. Install PulseAudio :
sudo dnf -y install pulseaudio alsa-utils

alsa-utils is needed for some tools used in subsequent step

2. Identify output device :
aplay -l

That gives an output similar to this:
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

In my system, there's a couple of device. If you know which device you are using, good. Otherwise, you can run through each of them with speaker-test and see what works. In my case : 

sudo systemctl stop kodi
speaker-test -D hw:0,3
speaker-test -D hw:0,7
speaker-test -D hw:0,8
speaker-test -D hw:0,9
speaker-test -D hw:0,10

You need to stop kodi first so it frees up the device for testing.

3. Configure default device :
Create a file at location /home/.kodi/.asoundrc with the following input:

defaults.pcm.!card 0
defaults.ctl.!card 0
defaults.pcm.!device 8
defaults.ctl.!device 8

Change the device and card accordingly.

4. Reboot the box

The above step works for me, so its here in case anyone else needs them too.

[Hcodi]

Thanks for this wiki.

[wirerydr]

@erqiyang:

Ok. I've gotten it to work. And I think it's also a mistake on my part. What happened was I had copied the $HOME/.kodi directory as a back-up from the old to the new installation, thinking that it should work. However, I forgotten that I was actually using pulseaudio from the old set-up. So when I got it booted up the first time, I couldn't hear any sound from the TV (I was actually only testing the GUI Sound at this point). 

Very glad to hear you got it working.  I had originally thought to mention PulseAudio, but because in the wiki I advise disabling it entirely (see here for why), I figured "eh, that's probably not it"...  Thanks also for the excellent writeup.  I would like to incorporate that into the wiki for those who (like yourself) do have an unavoidable need for PulseAudio.


@Hcodi

Thanks for this wiki.

You're very welcome.  Now that Fedora 27 is out, along with Kodi 17.6 (probably the last of the 17.x editions), I will be updating the Wiki accordingly once the Kodi RPMs make it out of RPMFusion's updates-testing repo and into updates.  Should be in another day or two...

[Deriv]

Were there some complications with Fedora 27 and Kodi? Or other reason why the guide has not yet been updated?

Anyway, thanks for the effort!

[wirerydr]

Were there some complications with Fedora 27 and Kodi? Or other reason why the guide has not yet been updated?

For some reason the Kodi 17.6 packages have not moved out of RPMFusion's Rawhide Development repository and into either Updates-Testing or Updates, as I would normally have expected.  I'm a little loath to update the wiki to refer to development packages before they have worked their way through the testing process.

If you really want to live on the bleeding edge, you can find RPMFusion's list of Kodi RPMs within their Rawhide Development repository here.

[Deriv]

Now I'm not at all familiar with the different repositories, but I noticed that here
http://download1.rpmfusion.org/free/fedo...ackages/k/
one can find kodi-17.6-1.fc27.x86_64.rpm

Isn't that what is needed?

[wirerydr]

Now I'm not at all familiar with the different repositories, but I noticed that here
http://download1.rpmfusion.org/free/fedo...ackages/k/
one can find kodi-17.6-1.fc27.x86_64.rpm

Isn't that what is needed?

You're right - thanks for pointing this out.  Fedora 27 came out on Nov. 14th, and Kodi 17.6 got released on Nov. 15th.  Repos usually don't slip new packages into their "releases" repo after that version has gone live.  Instead, they go into "updates", possibly after having first gone through "updates-testing".  For this reason it didn't even occur to me to look in "releases".

It looks like RPMFusion is actively updating their packaging of Kodi 17.6 - they now have 17.6-4 in their "rawhide" repo dated January 24th.  But what you found in "releases" is enough for the wiki to get updated, which I will do shortly.

Thanks again!

[jkarmani]

Amazing. In case someone wants to install Kodi Krypton 17.6 on iPhone running on iOS 11.3 can follow these steps:
 

1. Download Kodi Krypton 17.6 .IPA file.
   
2. Download and install Cydia Impactor.
   
3. Drag and drop the .ipa file of Kodi Krypton 17.6 inside Cydia Impactor.
   
4. Follow on-screen instructions and wait for installation to get completed.
   

Source: JailbreakNerds