Re: [RFT] Major snd_hda rewrite

On 06.04.2012 00:20, Jaroslav Suchanek wrote:
> On Mon, 2012-01-23 at 22:05 +0400, Yuri Pankov wrote:
>> On Wed, Jan 18, 2012 at 06:02:13PM +0200, Alexander Motin wrote:
>>> On 01/12/12 15:04, Yuri Pankov wrote:
>>>> On Thu, Jan 12, 2012 at 02:57:52PM +0200, Alexander Motin wrote:
>>>>> On 01/12/12 14:18, Yuri Pankov wrote:
>>>>>> On Wed, Jan 11, 2012 at 09:33:17PM +0200, Alexander Motin wrote:
>>>>>>> I would like request for testing of my work on further HDA sound driver
>>>>>>> improvement.
>>>>>> [...]
>>>>>>> Patch can be found here:
>>>>>>> http://people.freebsd.org/~mav/hda.rewrite.patch
>>>>>>>
>>>>>>> Patch was generated for 10-CURRENT, but should apply to fresh 9-STABLE
>>>>>>> and 8-STABLE branches also.
>>>>>>
>>>>>> Patch applied cleanly to r230008 using `svn patch`.
>>>>>>
>>>>>> hdacc0:<NVidia GT220 HDA CODEC>    at cad 0 on hdac0
>>>>>> hdaa0:<NVidia GT220 HDA CODEC Audio Function Group>    at nid 1 on hdacc0
>>>>>> pcm0:<NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)>    at nid 5 on hdaa0
>>>>>> hdacc1:<NVidia GT220 HDA CODEC>    at cad 1 on hdac0
>>>>>> hdaa1:<NVidia GT220 HDA CODEC Audio Function Group>    at nid 1 on hdacc1
>>>>>> pcm1:<NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)>    at nid 5 on hdaa1
>>>>>> hdacc2:<NVidia GT220 HDA CODEC>    at cad 2 on hdac0
>>>>>> hdaa2:<NVidia GT220 HDA CODEC Audio Function Group>    at nid 1 on hdacc2
>>>>>> pcm2:<NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)>    at nid 5 on hdaa2
>>>>>> hdacc3:<NVidia GT220 HDA CODEC>    at cad 3 on hdac0
>>>>>> hdaa3:<NVidia GT220 HDA CODEC Audio Function Group>    at nid 1 on hdacc3
>>>>>> pcm3:<NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)>    at nid 5 on hdaa3
>>>>>> hdacc4:<IDT 92HD75BX HDA CODEC>    at cad 0 on hdac1
>>>>>> hdaa4:<IDT 92HD75BX HDA CODEC Audio Function Group>    at nid 1 on hdacc4
>>>>>> pcm4:<IDT 92HD75BX HDA CODEC PCM (Analog)>    at nid 13 and 11 on hdaa4
>>>>>> pcm5:<IDT 92HD75BX HDA CODEC PCM (Analog)>    at nid 15 and 24 on hdaa4
>>>>>> pcm6:<IDT 92HD75BX HDA CODEC PCM (Front Digital)>    at nid 30 on hdaa4
>>>>>>
>>>>>> pcm4 (builtin speakers) and pcm5 (headphones) seem to work fine, however
>>>>>
>>>>> Thank you.
>>>>>
>>>>>> I'm not getting anything out of pcm0-pcm3 (connected to a TV via HDMI),
>>>>>> mplayer just pauses at the beggining, trying to cat anything to
>>>>>> /dev/dsp{0-3}.0 gives:
>>>>>>
>>>>>> pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead
>>>>>>
>>>>>> It was the same with the old driver and I'm not sure if it's (most
>>>>>> likely) my misconfiguration or a driver problem.
>>>>>
>>>>> It sounds more like a driver problem. HDMI audio is still not very well
>>>>> discovered area, and, according to ALSA reading, NVidia HDMI is also not
>>>>> very standard. Probably I'll finally have to buy something to
>>>>> experiment. What card do you have?
>>>>
>>>> It's a laptop with "nVidia Corporation GT216 [GeForce GT 230M]" (as
>>>> identified by x11/nvidia-driver).
>>>
>>> I've reproduced it on NVidia GT210. It seems there is some problem with
>>> MSI generation. Switching to legacy PCI interrupts fixes problem for me.
>>> Linux HDA driver disables MSI for all NVidia controllers.
>>>
>>> Try to add hint.hdac.0.msi=0 into the /boot/loader.conf.
>>
>> Sorry for delay. Indeed, setting hint.hdac.0.msi=0 helped.
>
> I tried the same trick but without success. I am attaching output of
> dmesg, sysctl, uname, sndstat and pciconf. I am using FreeBSD
> 9.0-RELEASE with MAV's recent patches.
>
> The chipset is NVidia ION. I am also using NVidia's drivers 295.33. The
> box is connected to receiver over HDMI. It does not work even with X
> server running. But the analog output works just fine.
>
> Any idea is appreciated.

dmesg you've provided is not verbose and so quite useless for HDA 
diagnosing. From what I can see here, it looks more alike to older 
GeForce 8300 based board (ASUS M4N78 PRO) I have, then to newer cards. 
Unluckily, I've tried all I could from the HDA side and still unable to 
make HDMI audio work on that my board. So either it is X11 video driver 
problem not initializing audio path properly on this chip, or I am 
missing some chip-specific clues.

-- 
Alexander Motin