[SOLVED] HDMI sound not working - monitor not detected
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
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.
Note the device 3 part. By default output goes to device 0.
$ speaker-test -c 2 -l 1 -D hw:1,3
I forgot to mention that pulseaudio Volume Control reports that my HDMI is unplugged (which it can't be because as mentioned before, that's how my TV is connected to my PC).
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
bash: speaker-test: command not found
BTW How did you tell from my output, that the default audio goes to 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.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Original Poster
Rep:
Quote:
Originally Posted by Shadow_7
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.
Yeah, I am seeing 4 HDMI outputs. My video card has 2 DVI outputs/ports and one mini HDMI port.
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!
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).
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Original Poster
Rep:
Quote:
Originally Posted by Shadow_7
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).
While I will try restarting pulseaudio (I don't think it will solve anything, though). Also what's the best command to use for that?
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.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Original Poster
Rep:
When I tried to kill pulseaudio, I get the following;
Code:
[james@localhost ~]$ pulseaudio --kill
E: [pulseaudio] main.c: Failed to kill daemon: No such process
When I try to start it, I get;
Code:
[james@localhost ~]$ pulseaudio --start
N: [pulseaudio] main.c: User-configured server at {e324a95ff35682e413e3ac0558e8c288}unix:/tmp/pulse-PKdhtXMmr18n/native, refusing to start/autospawn.
I also tried killing it in System Monitor, but as you said, it just restarted itself (autospawned). And yes, it is set to autospawn=yes in /etc/pulse/client.conf
I checked to see if I could hear any sound from HDMI and still nothing (but once again analog works no problems).
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.
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 }
pcm.pulse { type pulse fallback sysdefault }
ctl.!default { type pulse fallback sysdefault }
pcm.!default { type pulse fallback sysdefault }
I checked to see if the package alsa-utils is installed and it is, but as you can see below there is no executable for speaker-test in any folders. There is also no ~/.asoundrc file ether.
I will have a look at the logs, but was thinking of updating the kernel, as I remembered seeing with the google searches I done before, that others said, that worked for them.
At least for debian jessie. The user needs to be in the audio group and all the usuals of course.
I'm not understanding why it's not there ether, I'm sure I remember seeing it there in PCLinuxOS 2016. PCLinuxOS does use apt but not deb packages, it uses rpm packages instead.
Code:
[james@localhost ~]$ cd /usr/bin/
[james@localhost bin]$ ls -l speaker-test
ls: cannot access 'speaker-test': No such file or directory
[james@localhost bin]$ su -
Password:
[root@localhost ~]# apt-file list alsa-utils
-bash: apt-file: command not found
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
