You are not logged in.
Pages: 1
The DisplayPort/HDMI audio output of my GTX660 card stops after upgrading to nvidia-dkms-415.18-1. The device is still listed by "aplay -l" but does not produce sound. It appears as off to "pavucontrol". Downgrading to nvidia-dkms-410.78-1 solves the issue, though.
Any idea if it is a bug or a configuration matter?
Offline
Same issue here, with a GTX970.In pavucontrol I can list the HDMI GM204 profiles, but all are marked "unavailable" and "unplugged".
Last edited by zebulon (2018-11-25 15:50:03)
Offline
Upgrading to nvidia-dkms-415.18-4 do not solve the issue either.
Offline
Reported on nvidia forums (not by myself):
https://devtalk.nvidia.com/default/topi … 8-drivers/
Offline
The issue persists with version 415.22-1. Sad!
Offline
Same still at 415.25
Offline
Being stuck to version 410.78-1 was an annoyance. Now, if paired with kernel 4.20, X fails to start. Upgrading to 415.xx turned obligatory. And the annoyance turned into a hindering problem.
Offline
That is a problem, but please continue to report the issue upstream to https://devtalk.nvidia.com/default/board/98/linux/
Last edited by zebulon (2019-01-03 06:09:07)
Offline
It looks this has been fixed, at least for me, but not with a driver update. I suppose there was a change of API in 415, which was matched in a new PulseAudio or other sound component?
Offline
I note that I need to rebuild the driver (I use nvidia-dkms) to make the sound through HDMI work again, sometimes. I did not find out exactly what is triggering this, but this works now.
Offline
It seems there is a race condition for this bug on my system. Sometimes the sound works, sometimes it does not after reboot. I would say it works 10% of the time.
Offline
I have just made an observation that seems to confirm there is a race condition. I have rebooted around 20 times and collected dmesg outputs for 12 non-working instances and 6 working ones. But I also observed something interesting: when I reboot with the TV on, I noticed that:
when I see the boot screen of my motherboard (an Asus MAximus gene VIII) followed by the dmesg sequence and the KDE bootsplash then the sound is not working
sometimes after I reboot I do not see any image (TV displays a "No image" on TV, this comes from the TV itself) until I start to see the KDE splash (I do not see anything before that, no motherboard UEFI logo, no dmesg) then the sound works!
I can now confirm this happens 100% of the times. If I boot my computer and observe the Asus UEFI boot screen (the very first one when it proposes to press DEL to enter bios), I ctrl+alt+del to force reboot. If then the TV does not show the boot screen but a "No signal" (~ 25% of times) and only shows the computer image once it reaches the KDE splash screen, then the sound is working.
So there seems to be a pattern with the way the HDMI activates, and this is time based. Any idea?
Offline
At last: nvidia have fixed the bug in latest drivers 430.26.
Offline
Pages: 1