Re: snd_hda(4): getting line-in to work

From: Garrett Cooper <yanefbsd_at_gmail.com>
Date: Thu, 8 Jan 2009 09:37:16 -0800
On Wed, Jan 7, 2009 at 3:34 AM, Garrett Cooper <yanefbsd_at_gmail.com> wrote:
> Alexander Motin wrote:
>>
>> Garrett Cooper wrote:
>>>
>>> On Tue, Jan 6, 2009 at 12:53 PM, Alexander Motin <mav_at_freebsd.org> wrote:
>>>>
>>>> Garrett Cooper wrote:
>>>>>
>>>>>   I'm not sure if it's user error or not, but my snd_hda(4) enabled
>>>>> chipset doesn't have line-in support enabled. I was wondering if there
>>>>> were a special set of instructions I need to follow to get this
>>>>> working.
>>>>
>>>> The main instruction is to boot system with verbose messages. snd_hda
>>>> writes
>>>> all information needed to answer most questions. Read it yourself and if
>>>> it
>>>> does not help - send it to me.
>>>>
>>>>> [gcooper_at_orangebox /scratch/ltp]$ cat /dev/sndstat
>>>>> FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
>>>>> Installed devices:
>>>>> pcm0: <HDA Analog Devices AD1988B PCM #0 Analog> at cad 0 nid 1 on
>>>>> hdac0  [MPSAFE] (1p:1v/1r:1v channels duplex default)
>>>>
>>>> All I can see here is that you have some recording device. You can
>>>> browse
>>>> and select specific recording source with `mixer =rec` command. For
>>>> additional details look verbose output and read new snd_hda man page.
>>>>
>>>>> pcm1: <HDA Analog Devices AD1988B PCM #1 Analog> at cad 0 nid 1 on
>>>>> hdac0  [MPSAFE] (1p:1v/0r:0v channels)
>>>>> pcm2: <HDA Analog Devices AD1988B PCM #2 Digital> at cad 0 nid 1 on
>>>>> hdac0  [MPSAFE] (1p:1v/0r:0v channels)
>>>>
>>>> --
>>>> Alexander Motin
>>>
>>> Trying with the instructions on the manpage actually disabled my
>>> sound... then again I probably screwed up the settings (I believe it
>>> was noted as pcm2 before??).
>>>
>>> Here're the device.hints entries and I attached the -v boot log
>>> snippet for the card:
>>
>> In attached log you have missed one of very interesting parts while
>> grepping: pcmX devices output prints sound processing paths within codec for
>> every PCM device. Look it first before doing something.
>>
>>> hint.hdac.0.cad0.nid17.config="as=1seq=0 device=Headphones"
>>> hint.hdac.0.cad0.nid18.config="as=2seq=0 device=Line-out"
>>> hint.hdac.0.cad0.nid19.config="as=3seq=0 device=Speaker"
>>> hint.hdac.0.cad0.nid20.config="as=4seq=0 device=Mic"
>>> hint.hdac.0.cad0.nid21.config="as=5seq=0 device=Line-in"
>>> hint.hdac.0.cad0.nid22.config="as=6seq=0 device=Line-out"
>>> hint.hdac.0.cad0.nid23.config="as=6seq=0 device=Mic"
>>> hint.hdac.0.cad0.nid24.config="as=6seq=0 device=CD"
>>> hint.hdac.0.cad0.nid36.config="as=5seq=0 device=Line-out"
>>> hint.hdac.0.cad0.nid37.config="as=6seq=0 device=Line-out"
>>
>> Except lack of speces between fields there is also lack of any sense. I
>> don't understand what was you trying to do, but it will not work:
>>  - you configured nid 21 and nid 36 as association five, but made one of
>> them input and other output. It is incorrect, association may include only
>> pins of one direction (in/out);
>>  - association 6 is the same;
>>  - nid 19 has connectivity "None", so it will not be used by driver.
>> It is all described in manual.
>>
>> Actually I think default configuration is quite reasonable. There is some
>> things that can be tuned, but you should first understand what you have and
>> how it works.
>
>   Honestly, I feel as if I'm staring at a jigsaw puzzle all in pieces right
> now, trying to sort out what's going on -- I've never truly played with
> device.hints(5) before...
>   I'll look at the PCM entries and try to finally sort this out...
> Thanks,
> -Garrett

Alexander,
    Ok, I got stuck again. Can you possibly push me in the right
direction (complete verbose dmesg attached)? The line-in and SPDIF
(not so much of a concern) are the only issues that I'm aware of. I'll
have to open up my case and wire up the front ports in order to test
them for you.
    Also, the knobs that show up in xfce4-mixer are completely useless
for snd_hda(4) (every time I move the sliders it sets the volume back
to 0). Is this a known issue?
Thanks,
-Garrett

Received on Thu Jan 08 2009 - 16:37:19 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:40 UTC