Kodi Community Forum

Full Version: HDMI Audio Device Disappears (ALSA)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi Everyone,

I have Kodi v18 running under Ubuntu 18.04 with pulseaudio disabled.  I have been having issues with my HDMI audio device disappearing from within Kodi - Usually in the system settings it will list as "HDA Intel PCH, DON DENON-AVR on HDMI" when working correctly (for both decoded and passthru).  After an idle period (receiver off, Kodi system always on) audio will stop working in Kodi and the only listed audio devices will be "HDA Intel PCH, HDMI" and "HDA Intel PCH, HDMI 1", neither of which will work.  Restarting Kodi (the app, not the whole system) will allow the Denon receiver to be "re-detected" and work properly.  I know there are issues with EDID handshakes with AV receivers over HDMI when they go offline like this, but from what I can tell the OS is detecting the receiver as back online - just Kodi is not seeing that change. I did run into this occasionally prior to v18, but since updating it happens almost every time the system goes idle.  Anyone have any steps to figure out where this is failing or good ways to solve it?

Thanks!

EDIT:
Paste of initial audio detect along with events when receiver is powered back on: fetodujoma.kodi (paste)
I may be seeing the same thing... 18.04 minimal server, asla, standalone boot to x11. Everything works fine for a while, but if I let anything sleep, or turn reciever inputs etc, the screen is black and no audio. Logging in ssh shows service still running. Restarting the Kodi service fixes it again for a while. Are you saying that in your case the audio drops but the video is still working?
Correct, video is not an issue for me ever.  Interestingly I think the issue is occurring not during the idle period, but when the receiver is turned back on.  I connected into the primary session while the system was "idle" with vnc yesterday and the audio device was still listed correctly in Kodi.  As soon as I started the receiver the audio device list in Kodi went back to the generic  "HDA Intel PCH, HDMI 1."  It seems ubuntu is re-handshaking with the receiver as it powers up, but Kodi does not correctly refresh the device list.
maybe look into this wiki about creating an edid file to store the id Creating_and_using_edid.bin_via_xorg.conf
(2019-02-12, 18:55)disaacso Wrote: [ -> ]maybe look into this wiki about creating an edid file to store the id Creating_and_using_edid.bin_via_xorg.conf
 Had to do some tweaking to get this to work with intel card as it does not use xorg.conf, but I did get EDID dumped and set in a new xorg.conf.  Unfortunately this issue still occurs, though video behavior seems a bit different (as expected) - it may help cdhesse with the black screen thing.
Hi

I think I might have the same issue after recently moving from 17.6 to 18.0.
In my situation, after a few (or dozen) minutes the TV turns black, AVR speaker indicators go off. There is no sound of course, I have UI sounds enabled, and there is no sound when I push the remote buttons, but kodi process is still active, logs are updated with key-press events.
To recover, I have to either reboot, or stop lightdm, rmmod snd_hda_intel and modprobe it again. If I restart lightdm without reinserting the sound module, I get the video, but no sound, but in the settings the output device at hdmi#0 is still there.
Around the time when blank screen happens, I can see in Xorg.0.log the following:
[ 20524.904] (II) event2 - Video Bus: device removed
[ 20524.940] (II) event0 - Power Button: device removed
[ 20524.956] (II) event1 - Pulse-Eight USB-CEC Adapter: device removed

kodi.log http://paste.ubuntu.com/p/XKVvgYZxst/
Xorg.log http://paste.ubuntu.com/p/vNw6CVvYNy/

The issue goes not happen when I reproduce the same below scenario with 17.6 (from official xbmc-team ppa as well), so I guess there is an issue with 18.0, because nothing changes except for the version. Everything runs flawlessly. 

Kodi (18.0 Git:20190128-d81c34c). Platform: Linux x86 64-bit
OS: Ubuntu 18.04.2 LTS
Mainboard (SoC): ASRock J4105-ITX
CPU: Intel® Celeron® J4105 CPU @ 1.50GHz
GPU: VGA compatible controller [0300]: Intel Corporation Device [8086:3185] (rev 03) (prog-if 00 [VGA controller])
install method: PPA http://ppa.launchpad.net/team-xbmc/ppa/ubuntu *** 2:18.0+git20190128.1934-final-0bionic
hardware setup: Kodi box -> pulse-eight USB - CEC Adapter -> AVR (Yamaha RX-S601D) -> Panasonic TV
Power management settings:
cat /sys/module/snd_hda_intel/parameters/power_save_controller -> N
cat /sys/module/snd_hda_intel/parameters/power_save -> 0

Steps to reproduce:
  1. pulseaudio is uninstalled
  2. delete .kodi directory before install
  3. fresh Kodi 18.0 install - apt install kodi
  4. sudo systemctl start lightdm
  5. set audio output device to HDA Intel PCH, MEI Panasonic-TV on HDMI #0 - this how it looks in kodi settings.
  6. set passthrough to the same device
  7. leave it for a couple minutes
  8. after a while, tv screen turns black, pressing remote buttons doesn't 'wake' it, there is no sound.
Start kodi as follows:

xset -dpms && kodi
@uowiec
I think your issue is similar to what I have reported here.

https://bugs.freedesktop.org/show_bug.cgi?id=109509

And that’s no Kodi issue for sure but a kernel issue.
If that's the case use the drm_kms_helper (or the newer variant) with video grub option - as documented by me here in this forum. This will hardcode EDID information and devices will magically reappear.
(2019-02-15, 09:38)fritsch Wrote: [ -> ]If that's the case use the drm_kms_helper (or the newer variant) with video grub option - as documented by me here in this forum. This will hardcode EDID information and devices will magically reappear.
Thanks fritsch,

Followed your steps here with the update for the 4.15 kernel: 2148505 (post)  

I tried this (in addition to the xorg.conf method) and still have the same issue.  @Memphiz  might be on to something with that bug report, it looks similar to this issue.  I did find a spare nvidia card kicking around this morning, so I will probably stick that in my box this weekend and see if it solves the issue.
xorg.conf with edid is nvidia only.

Post your dmesg after you applied the drm_kms_helper workaround.
(2019-02-15, 19:41)fritsch Wrote: [ -> ]xorg.conf with edid is nvidia only.

Post your dmesg after you applied the drm_kms_helper workaround.
oxapelejow (paste)
You have a typo. The log lists a == for your edid loader: drm.edid_firmware==HDMI-A-2:edid/edid.bin . It should only be a single =.
(2019-02-15, 23:30)yasij Wrote: [ -> ]You have a typo. The log lists a == for your edid loader: drm.edid_firmware==HDMI-A-2:edid/edid.bin . It should only be a single =.
 Good catch - testing with that fixed now....

EDIT:  So far so good, this looks better: yahabocere (paste)
(2019-02-15, 07:41)fritsch Wrote: [ -> ]Start kodi as follows:

xset -dpms && kodi
Hi
Thanks for the tip. I had trouble to include the "xset -dpms" into the lightdm session, but i launched that from desktop session, and Leia run for couple hours without any issue. 
How do I make it peperment?
Pages: 1 2