HDMI sound not working - monitor not detected
I have just upgraded from PCLinuxOS 2016 KDE to PCLinuxOS 2017 KDE and my HDMI audio has stopped working (was working in PCLinuxOS 2016 KDE, no problems). The analog audio still works no problems.
The research I've been doing for the last couple of hours is suggesting that the ALSA driver is not detecting my TV, even though my TV is connected via HDMI (directly) to my PC. I have no other monitors/TV's connected to my PC. I have done google search's and the only useful hit I've had so far is ftp://download.nvidia.com/XFree86/gp...dmi-audio.html But I cannot see any section in the above mentioned site on how to enable HDMI audio for my TV. I have not changed my hardware (TV or PC/video card/etc) since upgrading my distro. Here's some info about my hardware: Code:
[james@localhost ~]$ lspci -nnk | grep -i -A7 audio Code:
[james@localhost ~]$ aplay -l Code:
[root@localhost ~]# lsmod Code:
[james@localhost ~]$ cat /proc/asound/card1/eld#0.0 Code:
[james@localhost ~]$ cat /proc/asound/card1/codec#0 So I guess my question is, can I do anything about this, as it would be nice to have some HDMI audio ;) Thanks in advance for any help with this. |
===> card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Note the device 3 part. By default output goes to device 0. $ speaker-test -c 2 -l 1 -D hw:1,3 |
Quote:
Also I get the following command not found message with the command you have mentioned; Code:
[james@localhost ~]$ speaker-test -c 2 -l 1 -D hw:1,3 |
Actually you have 4 HDMI outputs by the looks of it.
hw:1,3 hw:1,7 hw:1,8 hw:1,9 All listed as HDMI out in aplay -l. I assume your video card has 4 video outs, perhaps you're not plugged into the first one, which is why things got odd. pavucontrol should allow you to select it. Although sometimes I have to disable the interface and re-enable to get pulseaudio to grab a clue about what it was already configured for. Basically on the Configuration tab turn everything off, then turn the one thing you use on. Even if that should technically do nothing because it's already set that way. Also note that you can have per application levels but the application has to be actively using the soundcard for pavucontrol to give you the option to change it (playback tab). Also check your mixer levels. With alsamixer and pavucontrol. |
$ sudo apt-get install alsa-utils
(for speaker-test in debian jessie) |
Quote:
I did try to see in alsamixer, if anything was muted but, could not see any MM pavucontrol does let me select the different outputs but, all of the HDMI outputs say unplugged (but once again can't be). I did also try to play sound using the HDMI outputs with pavucontrol opened and it does show sound playing using HDMI, but I do not hear a thing. KDE is set on the same HDMI output as the one that worked before I installed PCLinuxOS 2017 KDE (and already had the same output selected). But I will try what you said and let you know how it goes. Thanks Shadow for your help so far! :D |
You could try restarting pulseaudio. You might also check your HDMI cable / port. Some ports do NOT support audio (DVI with an HDMI connector). Which could be the one on the TV, not the computer. If you changed things AFTER booting, it could be weird (didn't register with dbus), problems solved by rebooting (m$ methodology).
|
4 Attachment(s)
Quote:
The HDMI ports and cable work no problem, as I even restored my old system back (PCLinuxOS 2016) from my clone images, and HDMI audio worked no problem (and straight away). So I know that's not the issue here and there are no DVI connectors, connecting anything, it's just straight HDMI cable (and both HDMI ports on the TV and video card have no problems). I don't have anything connected to any of the DVI ports on the video card. I have taken some screen shots for ya, to try and give you a better picture of my setup and what's going on. |
So not the hardware then. You might want to put the built in audio to OFF on the configuration tab. As far as restarting pulseaudio.
$ pulseaudio --kill $ pulseaudio --start Although if "autospawn=yes" in /etc/pulse/client.conf, then it will restart itself when stopped (or kill -9 'd). |
When I tried to kill pulseaudio, I get the following;
Code:
[james@localhost ~]$ pulseaudio --kill Code:
[james@localhost ~]$ pulseaudio --start I checked to see if I could hear any sound from HDMI and still nothing (but once again analog works no problems). I'm out of ideas here. :( |
Does speaker-test output to HDMI?
$ speaker-test -c 2 -l 1 -D hw:1,3 $ speaker-test -c 2 -l 1 -D hw:1,7 $ speaker-test -c 2 -l 1 -D hw:1,8 $ speaker-test -c 2 -l 1 -D hw:1,9 If not then perhaps the nvidia driver is the issue. If using pulse, and it appears that you are, then your asoundrc should look a bit like this: File: $HOME/.asoundrc Code:
ctl.pulse { type pulse fallback sysdefault } |
Since pulse had issues you might check the logs.
# journalctl -a Pager methods for less / man should apply. With "q" to quit. And "/" to search. So "/" then "pulse" then [ENTER], and "/" then [ENTER] to search again. # cat /var/log/syslog | grep -i pulse # dmesg | grep -i pulse Depending on your distro init system and things. If it failed, it had reasons. Maybe because it's already running. Maybe for less obvious reasons. |
Quote:
Code:
[james@localhost ~]$ locate speaker-test |
It should be /usr/bin/speaker-test
$ which speaker-test $ apt-file list alsa-utils $ dpkg -c /var/cache/apt/archives/alsa-utils_1.0.28-1_amd64.deb At least for debian jessie. The user needs to be in the audio group and all the usuals of course. |
Quote:
Code:
[james@localhost ~]$ cd /usr/bin/ |
All times are GMT -5. The time now is 04:30 AM. |