Negative…still shows as “unplugged”.
[QUOTE=
Is there a chance that another HDMI device is actually connected? Do any of the following command strings result in audible sound?
aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav
aplay -D plughw:1,7 /usr/share/sounds/alsa/Front_Right.wav
aplay -D plughw:1,8 /usr/share/sounds/alsa/Front_Right.wav
Apologies if on the wrong track here…remote diagnosis can be a challenge. :[/QUOTE]
The results of the above commands is:
> aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav
aplay: main:828: audio open error: Device or resource busy
:~> aplay -D plughw:1,7 /usr/share/sounds/alsa/Front_Right.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
~> aplay -D plughw:1,8 /usr/share/sounds/alsa/Front_Right.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
No need for apologies; to the contrary, I very much appreciate your efforts in whichever direction might take us…Thank You!!!
No audible sound evident with any of those?
Upon realizing that the following command resulted in error message:
> aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav
aplay: main:828: audio open error: Device or resource busy
I did the following:
> pulseaudio -k
> pulseaudio --start
> aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
As you can see, that cleared the “Device or resource busy” message from the first run of the commands.
No sound though…
Yes, that was to be expected since PA had probably grabbed that device. We’ll wait and see if oldcpu has any advice on this.
Sounds good…I am doing what I can on this end and I will report anything that might be of help to you guys.
Thanks!!!
Another data point, with AlsaMixer (v1.1.5) the volume for S/PDIF / S/PDIF 1 & S/PDIF 2 shows 00 and the only control over then is to mute them, but no volume increase allowed.
In case it helps with the ongoing trouble shooting.
No, that’s for digital output (usually via a fibreoptic cable or perhaps coaxial cable with RCA connectors).
Lets try again what deano_ferrari suggested, but this time suspending pulse audio. Try this as a regular user and also try a second time with root permissions …ie :
pasuspender -- aplay -D plughw:1,3 /usr/share/sounds/alsa/test.wav
pasuspender -- aplay -D plughw:1,7 /usr/share/sounds/alsa/test.wav
pasuspender -- aplay -D plughw:1,8 /usr/share/sounds/alsa/test.wav
… as noted, try that in a konsole/xterm as a regular user. Then if no sound, in that konsole/xterm (only) switch to root permissions, and try the above again.
Let us know if you get any errors.
.
Noted…Thanks.
No sound with the new commands as regular user:
~> pasuspender -- aplay -D plughw:1,3 /usr/share/sounds/alsa/test.wav
Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
~> pasuspender -- aplay -D plughw:1,7 /usr/share/sounds/alsa/test.wav
Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
~> pasuspender -- aplay -D plughw:1,8 /usr/share/sounds/alsa/test.wav
Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Multiple errors running them with root permissions (sudo su)
# pasuspender -- aplay -D plughw:1,3 /usr/share/sounds/alsa/test.wav
Connection failure: Connection refused
pa_context_connect() failed: Invalid argument
# pasuspender -- aplay -D plughw:1,7 /usr/share/sounds/alsa/test.wav
Connection failure: Connection refused
pa_context_connect() failed: Invalid argument
# pasuspender -- aplay -D plughw:1,8 /usr/share/sounds/alsa/test.wav
Connection failure: Connection refused
pa_context_connect() failed: Invalid argument
Oldcpu: thanks for stepping in…!!!
Open a terminal and watch alsa with
sudo alsactl monitor
Try power-cycling the monitor, and see if the ‘plugged’ status changes. You could also check via pavucontrol (configuration tab).
The “sudo alsactl monitor” command does not do anything…it hangs without a cursor until Ctr-Z is pressed to stop it.
Power-cycling the monitor (off/on) does not change the status shown in the pavucontrol, still shows “unplugged” in all HDMI profiles.
No, it’s not hanging, it’s monitoring as designed… and yes CTRL+C to terminate when done. 
Power-cycling the monitor (off/on) does not change the status shown in the pavucontrol, still shows “unplugged” in all HDMI profiles.
Ok, thanks for the update.
FWIW, here’s a archlinux thread where some users describe similar ‘unplugged’ issues, but they seem to be using DP connected monitors rather than HDMI, and if I understand correctly at least one user found that the monitor was using the wrong sound settings. Another found some setting in the nvidia control panel utility. Do you have such a graphical config utility? (Sorry I’m not an nvidia user, so can only share what I find from reading).
I will go over that thread to see if something helps…thanks for that pointer.
As far as the monitor, like I said in my initial post, it was working with 13.2 for a few years without an issue.
I will check on the nvidia configuration utility as I go over the thread above, right now I do not know what to look for.
Thanks, I will continue with my readings…
Yes, well it could well be due to a kernel regression, and a bug report may be needed to help resolve this.
I will check on the nvidia configuration utility as I go over the thread above, right now I do not know what to look for.
It was nvidia-settings I was thinking of, and based on a quick search of the nvidia repo it doesn’t appear to exist anymore, so forget it. It was just an idea after reading the archlinux thread I linked to. I don’t have nvidia hardware so unfamiliar with it really.
It could be a kernel regression as deano_ferrari notes possible.
I also recall reading this above:
> /sbin/lspci -nnk | grep -A2 VGA
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2)
Subsystem: NVIDIA Corporation Device [10de:1097]
Kernel driver in use: nvidia
That suggests the proprietary graphic driver (I think) … and further I think the HDMI is in part associated with that driver in addition to the kernel. I have not used the proprietary nvidia driver for years. I vaguely recall many years back there was a GUI one could bring up to configure the nvidia proprietary driver. Is such the same today? If so, is there an HDMI control in that GUI ? … This is a speculative question - I simply do not know.
[edit ] maybe that is the nvidia-settings that deano_ferrari was referring to - I just read his post above now.
Correct, I am using the Nvidia proprietary driver.
The configuration utility does not have any HDMI controls, that I see.
Possibly instead called “nvidia-xconfig” ? Again - I’m speculating as I don’t use a nVidia proprietary driver. Even if there is such an app, nor do I know if it provides any HDMI control.
That was a CLI version of the graphical utility, but was strictly for configuring the X-server as far as I know.