HDMI audio no longer works with 190.xx releases

[fredericva]

As said in the topic title, HDMI audio output with 185.xx works perfectly, but when upgraded to 190.xx, doesn't.

aplay -l, aplay -L and all other usual places to look display the same information for both 185.xx and 190.xx series drivers, but with 190.xx no sound is sent over HDMI.

Switching back and forth between 185.18.36 and 190.42 respectively enables and disables HDMI audio output.

I have attached a bug report using 190.42. If another bug report using 180.16.36 is also needed, let me know and I'll attach it.

[Ankh]

FWIW, I have 190.42 working OK with audio over HDMI. It was working with 185.* as well - must be some subtlety you're missing.

My nvidia-bug-report (details my working system setup) is in this thread :

http://www.nvnews.net/vbulletin/showthread.php?t=141000

[fredericva]

Originally Posted by Ankh

FWIW, I have 190.42 working OK with audio over HDMI. It was working with 185.* as well - must be some subtlety you're missing.

My nvidia-bug-report (details my working system setup) is in this thread :

http://www.nvnews.net/vbulletin/showthread.php?t=141000

Then perhaps it's a chip specific bug?

Running "speaker-test -c6 -Dplughw:0,3" and "speaker-test -c6 -Dhdmi" works on 185.* but doesn't on 190.42. I've checked alsamixer, and have tried all possible controls as well.

aplay -l:

**** List of PLAYBACK Hardware Devices ****      
card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
  Subdevices: 1/1                                                       
  Subdevice #0: subdevice #0                                            
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]        
  Subdevices: 1/1                                                       
  Subdevice #0: subdevice #0

[tack]

I'm also having problems with 190.42. 6- and 8-channel LPCM was being seen by my AVR as 2 channel LPCM. AC3 and DTS passthrough as well as 2-channel PCM worked fine. (IOW, it was behaving like SPDIF.)

I'm in the process of adding 8 channel support to MPlayer. Last night, just before committing, I thought I'd do another quick round of tests, and that's when I found 6 and 8 channel content wasn't working, whereas it was just the night before.

Struggling to recall what might have changed, the only thing I remember doing was rebooting. (I do it rarely, but I was having ugly NFS problems.) After troubleshooting many red herrings, I finally determined that downgrading to 185.18.36 solved the problem.

I did several upgrades/downgrades to see what worked and what didn't. Here's the sequence of events:

1. On 190.42, after rebooting, noticed that 6/8 channel PCM was not working. AC3/DTS passthrough and 2 channel PCM was fine.
2. Rebooted (warm and cold), downgraded and upgraded kernel versions (ensuring that snd_hda_codec_nvhdmi had the 8 channel capability in all cases), swapped out my HDMI cable, to no avail.
3. Downgraded to 185.18.36; 6/8 channel PCM worked fine again.
4. Upgraded back to 190.42; 6 channel PCM worked now. (I neglected to test 8 channel PCM.)
5. Power cycled; still at 190.42; 6 channel PCM continued to work.
6. 8 channel PCM didn't work, but instead of being detected by my AVR as 2 channels, it was now indicating 6 channels.
7. Downgraded to 185.18.36; both 6/8 channel PCM worked again.
8. Upgraded to 190.42; both 6/8 channel PCM still worked.
9. Rebooted; still at 190.42; 6 channel PCM continued to work, but 8 channel broken (being detected as 6 channels)
10. Downgraded to 185.18.36; both 6/8 channel PCM worked again.
11. Decided to try 190.42 again; both 6/8 channel PCM still worked.
12. Rebooted; still at 190.42; but now, 6 channel PCM being detected as 8 channels on my AVR (but all 6 channels were present and mapped correctly), and 8 channel content was correct.
13. Downgraded to 185.18.36; both 6/8 channel PCM worked properly again.

Based on the above, it looks an awful lot like 190.xx is missing some important channel initialization step (or it's buggy) which is present and working in 185.18.xx.

Once running 185.18.xx and then upgrading to 190.xx, things still seem to work properly at least until rebooting. I was at 190.xx for several weeks, and then just the other night decided to reboot, and that's when my troubles began. (And that several week gap is almost certainly why I fell down the troubleshooting rabbit hole.)

My motherboard is a Gigabyte GA-E7AUM-DS2H. /proc/asound/card0/codec#3 contains:

Codec: Nvidia MCP7A HDMI
Address: 3
Function Id: 0x1
Vendor Id: 0x10de0007
Subsystem Id: 0x10de0101
Revision Id: 0x100100
No Modem Function Group found
Default PCM:
    rates [0x0]:
    bits [0x0]:
    formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x04 [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital: Enabled
  Digital category: 0x0
  PCM:
    rates [0xc0]: 48000 88200
    bits [0xf]: 8 16 20 24
    formats [0x1]: PCM
Node 0x05 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x18560110: [Jack] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x1, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x04
Node 0x06 [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0xc0]: 48000 88200
    bits [0xf]: 8 16 20 24
    formats [0x1]: PCM
Node 0x07 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x58560121: [N/A] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x2, Sequence = 0x1
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x06
Node 0x08 [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0xc0]: 48000 88200
    bits [0xf]: 8 16 20 24
    formats [0x1]: PCM
Node 0x09 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x58560122: [N/A] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x2, Sequence = 0x2
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x08
Node 0x0a [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0xc0]: 48000 88200
    bits [0xf]: 8 16 20 24
    formats [0x1]: PCM
Node 0x0b [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x58560123: [N/A] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x2, Sequence = 0x3
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0a
Node 0x0c [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0xc0]: 48000 88200
    bits [0xf]: 8 16 20 24
    formats [0x1]: PCM
Node 0x0d [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x00000014: OUT Detect
  Pin Default 0x58560124: [N/A] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0x2, Sequence = 0x4
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x0c

[fredericva]

Trying with any number of channels between 1 and 8 all gives the same result on my system with 190.42: no sound output.

All works fine with 185.18.36 as previously stated.

[seaweed]

I am using an ION, mine was ok on earlier driver and kernel (190.40 on standard kernel version shipped with ubuntu 9.10 ) but since when I updated my kernel to 2.6.32-020632rc5 and driver version to 190.42, it doesn't work anymore.

[tack]

Originally Posted by seaweed

I am using an ION, mine was ok on earlier driver and kernel (190.40 on standard kernel version shipped with ubuntu 9.10 ) but since when I updated my kernel to 2.6.32-020632rc5 and driver version to 190.42, it doesn't work anymore.

And if you now reboot into the old kernel (still with 190.42), it works?

[toddbailey]

Hate to join the problem but Me too


I'm reverting back to 185.36 until the next release.

190.42 appears to have "issues"

[alanw]

Almost the same thing here.

Multichannel lpcm works like charm on 185 series series, but with 190 series drivers it only comes out as 2 channel lpcm.

My chipset is nvidia 9400 integrated motherboard

Surely the 190 series drivers broke hdmi audio completely. I think the driver tries to make some channel number detection or allocation, which could be a great thing if it worked. On intel G45 it works like the driver detects the available rates and channels and handles channel allocation according to that.

[tack]

Surely by now there's enough independent confirmation of this problem.

Can anyone from nvidia confirm this will be addressed?

Thanks.

[tack]

I just tried 190.36 and it's also not quite right. Once rebooted, my AVR sees both 6 and 8 channel LPCM as 8 channels.

As always, downgrading to 185.18.36 works, and continues to work after upgrading to 190.xx UNTIL I reboot.

Edit: let me clarify what I mean by "downgrading to 185.18.36": I kill X, run through the 185.18.36 installer, start X. If I, at that point, kill X and upgrade back to 190.42, it remains working until the next reboot.

It is not sufficient to merely insmod the 185.18.36 driver, I must also start X while under 185.18.36. However it is not necessary to play audio while at 185.18.36 -- immediately after X starts, if I kill it and upgrade back to 190.42, it's fine until next reboot.

[alanw]

Originally Posted by tack

Edit: let me clarify what I mean by "downgrading to 185.18.36": I kill X, run through the 185.18.36 installer, start X. If I, at that point, kill X and upgrade back to 190.42, it remains working until the next reboot.
.

From what you write i am pretty sure the problem is where the card makes handshake process with the receiver and reads EDID. This is when you turn on the computer or reboot.