All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerio Tesei <valerio.tesei@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig
Date: Wed, 13 Apr 2011 21:12:55 +0200	[thread overview]
Message-ID: <4DA5F5B7.5010803@gmail.com> (raw)
In-Reply-To: <BANLkTi=4wGJSDGOWwrFHMhd9w17tWvbrNQ@mail.gmail.com>

Il 13/04/2011 13:08, Valerio tesei ha scritto:
> 2011/4/13 Raymond Yau <superquad.vortex2@gmail.com>:
>> 2011/4/12 Valerio Tesei <valerio.tesei@gmail.com>
>>
>>> Il 11/04/2011 10:21, Valerio tesei ha scritto:
>>>
>>>> 2011/4/10 Raymond Yau <superquad.vortex2@gmail.com>
>>>>> 2011/4/8 Valerio tesei <valerio.tesei@gmail.com>
>>>>>> Hi Raymond,
>>>>>> I spent a little time reading sound documentation but doesn't find
>>> anything
>>>
>>>>>> about how to apply a patch to snd-hda-intel, but it is needed? there is
>>> no
>>>
>>>>>> an "patch auto detect"? i enable the patch option in HDA-Intel kernel
>>>>>> config, this WE i will study more, Takashi could you please give me
>>>>>> documentation about patch applying?
>>>>> The easy way is to use Takashi 's daily snapshot
>>>>> since there are a few patches related to alc892
>>>> I'm using it.
>>>> I must wait for a patch, hoping in Takashi? :)
>>>> I think i will make some experiment on patch_realtek.c :)
>>>> For the noise problem if i understand a little, could be a connection
>>>> problem, i will try to graph it.
>>>> For the capture problem i need to read more :)
>>>>>> About the NVIDIA video card, do you think that the hdmi on NVIDIA could
>>>>>> conflicts with the one in motherboard, creating the problem that I'm
>>>>>> experiencing?
>>>>>> I didn't check anything on kernel regarding HDMI, and i use an "edited"
>>>>>> NVIDIA driver (by me) to build against 2.6.39 (only rename smp_lock.h
>>> to
>>>
>>>>>> smp.h in the code) version is 270, taken from gentoo repos.
>>>>> you have to ask nvidia hdmi expert or asus forum
>>>> Seems to be a common problem from 2.6.37 with 267.10 driver, for the
>>>> moment i will hope this does not create any problem.
>>>> I'm not using hdmi on Mobo neither the one on Video card.
>>>>>> To clarify my self
>>>>>> - I *need* to apply alc662 patch to snd-hda-intel to test if commits
>>> work?
>>>
>>>>>> - I *need* to solve problems with NVIDIA drivers to make my sound card
>>>>>> work?
>>>>>> (and if i must specify witch port nvidia must use how i could do that?)
>>>>>> - alsaconf doesn't find my sound card, even when it works (crackly but
>>>>>> works) is this problem linked to capture streams problems ?
>>>>> No need to do anything if Takashi mention that model="auto" is used to
>>>>> support 6stack motherboard
>>>> This mean that tecnicaly my sound card/motherboard must work with the
>>>> patches that Takashi commited?
>>>>>> Some news:
>>>>>> - after module loading I hear a big noise
>>>>>> - after upgrade to Takashi's sound-2.6 kernel tree, i hear dx louder
>>> than
>>>
>>>>>> sx
>>>>>> - some times the sounds mute, after 7/10 seconds sound come back (no
>>>>>> changes
>>>>>> in alsamixer)
>>>>>> I know that I'm completely usefulness and a little bit annoying, I'm
>>>>>> reading
>>>>>> about alsa devel but I gess is a little bit hard for me.
>>>>> [    7.111176] SKU: override=0x1
>>>>> [    7.111385] hda_codec: ALC892: BIOS auto-probing.
>>>>> [    7.111389] autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0)
>>>>> --
>>>>> [    7.116998] Cannot find slave PCM Playback Switch, skipped
>>>>> [    7.117657] input: HDA Intel Headphone as
>>>>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
>>>>> As you have specifed in BIOS setup that "Front Panel Connector" is
>>> [AC97]
>>>
>>>>> and the BIOS seem set "Misc=NO_PRESENCE"
>>>>> why does the driver still create
>>>>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input4 for jack reporting ?
>>>>> Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
>>>>>  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
>>>>>  Amp-In vals:  [0x00 0x00]
>>>>>  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
>>>>>  Amp-Out vals:  [0x00 0x00]
>>>>>  Pincap 0x0001373e: IN OUT HP EAPD Detect Trigger
>>>>>    Vref caps: HIZ 50 GRD 80 100
>>>>>  EAPD 0x2: EAPD
>>>>>  Pin Default 0x02214120: [Jack] HP Out at Ext Front
>>>>>    Conn = 1/8, Color = Green
>>>>>    DefAssociation = 0x2, Sequence = 0x0
>>>>>    Misc = NO_PRESENCE
>>>>>  Pin-ctls: 0xc0: OUT HP VREF_HIZ
>>>>>  Unsolicited: tag=00, enabled=0
>>>>>  Power states:  D0 D1 D2 D3 EPSS
>>>>>  Power: setting=D0, actual=D0
>>>>>  Connection: 5
>>>>>     0x0c 0x0d 0x0e 0x0f 0x26*
>>>> I disconnected the front panel, before install windows 7 to test if
>>>> soundcard work, i was thinking that te problem was a short circuit.
>>>> ___________________________________________
>>>>> Alsa-devel mailing list
>>>>> Alsa-devel@alsa-project.org
>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>> Takashi if you need debug or something else just ask.
>>> I put "more verbose debug" into my kernel config, I'm starting to describe
>>> the issue:
>>>
>>> my player is mplayer, I'm playing a divx by alsa output.
>>>
>>> I tried the patch suggested by Raymond
>>>
>>>        if (codec->vendor_id == 0x10ec0892)
>>>
>>>                spec->stream_analog_alt_capture =
>>> &alc880_pcm_analog_alt_capture;
>>>
>>> Putted into sound/pci/hda/patch_realtek.c ,  function patch_acl662, but
>>> nothing changed, issues are the same.
>>>
>>> After module is loaded big noise starts, at first right channel is muted, I
>>> hear realy disturbed and bass are crackly, after 10 minutes right channel
>>> start crack, after 10 minutes, right channel is low but sounds, only bass
>>> cracks, and high frequencies are clear.
>>>
>>> Front-Panel is physicaly detached from motherboard, in bios is setted as
>>> "AC97", and S/P-DIF is setted as S/P-DIF
>>>
>>> New alsa-info are this:
>>>
>>> http://www.alsa-project.org/db/?f=cef5e8099352f29c70b20ae2853714a200cb37a4
>>>
>>> --
>>>
>>
>> http://thread.gmane.org/gmane.linux.alsa.devel/79348
>>
>> your info is different from  hda-emu/codecs/alc892-asus-p7h55
>>
>> http://git.kernel.org/pub/scm/linux/kernel/git/tiwai/hda-emu.git
>>
>> 2010-08-16     Takashi Iwai    Add alsa-info of ASUS P7H55 M-Pro with ALC892
>> codec
>>
>> Codec: Intel IbexPeak HDMI 491
>> Address: 3
>>
>> http://www.intel.com/support/motherboards/desktop/sb/cs-020642.htm#standards
>>
>>
>>        snd_hda_codec_write(codec, srcs[i], 0,
>>                    AC_VERB_SET_AMP_GAIN_MUTE,
>>                    AMP_IN_UNMUTE(1));
>>
>> The noise may be due to umute of connection 0x0b in 0x0c, 0x0d, 0x0e and
>> 0x0f by alc662_auto_set_output_and_unmute() since those input pins (e.g.
>> Front mic, line and rear mic)  's  "playback switch" in audio mixer 0x0b is
>> not muted by alc662_auto_init_analog_input() or alc662_auto_init_input_src()
>>
>>
>> http://www.intel.com/support/motherboards/desktop/sb/cs-020642.htm#multistream
>>
>> It depend on whether you want your voice record from front mic appear in
>> speakers connected to all rear panel jacks when ummute "front mic playback
>> switch" if you use it as karaoke or multistreaming playback
>>
>>
>> Do you get the correct sound from the rear panel and front HP when running
>> "speaker-test -c 8 -t wav -Dhw:0,0" ?
>>
>>
>> Two set of input sources,capture volume/switches since the number of
>> connections is different in node 0x22 and 0x23 as node 0x22 has the digital
>> mic node 0x12
>>
>>
>> ode 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
>>  Control: name="Input Source", index=0, device=0
>>  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
>>  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
>> [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
>> [0x80 0x80]
>>  Connection: 12
>>     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b 0x12
>> Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
>>  Control: name="Input Source", index=1, device=0
>>  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
>>  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
>> [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
>>  Connection: 11
>>     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
> Yes but my motherboard is ASUS P7H55D-M PRO not ASUS P7H55-M PRO i
> dont know the exact differences between h55d and h55 (i think only a
> 'deluxe' on the package)
> On Asus compare, differences are about gigabit lan (realtek obviusly)
> on p7h55d-pro and more "asus unique features" on p7h55d-pro (wasted
> money to get nothing more than value mobo)
> This is my back panel :
> http://img40.imageshack.us/img40/8864/asusp7h55dmpro1156ddr3m.jpg
> seems the same as p7h55-pro
>  are out of my skills.
> I will revert sound-2.6-git changes (printk and patch you suggested
> above), create a new alsa-info, dump the graph by hda-analyzer tool, I
> will post all these things later (when back home)
> Anyway, all of you make a great work. I realy appreciate. Thanks All.
http://valeriotesei.com/alsa/codec.svg

This is the codec graph, seems there are block not connected, hope this
will help you.
I never work with alsa, but a lot with graphedit on windows and
directshow, if is the same, I think is not normal, do you?

V.

-- 
*Email:* valerio.tesei@gmail.com
*Cellulare:* +39.3394768306
*Gtalk:* valerio.tesei@gmail.com
*LinkedIn:* http://www.linkedin.com/pub/valerio-tesei/22/a87/577

  reply	other threads:[~2011-04-13 19:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 14:59 [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-06  6:19 ` Takashi Iwai
2011-04-06  7:35   ` Raymond Yau
2011-04-06  7:41     ` Takashi Iwai
2011-04-06  8:29       ` Raymond Yau
2011-04-06  9:29         ` Takashi Iwai
2011-04-06 10:49           ` Valerio tesei
2011-04-07  1:53             ` Raymond Yau
2011-04-07 12:59               ` Valerio tesei
2011-04-07 13:13                 ` Raymond Yau
2011-04-07 13:55                   ` Valerio tesei
2011-04-07 19:44                   ` Valerio Tesei
2011-04-08  0:48                     ` Raymond Yau
2011-04-06 12:59           ` Raymond Yau
2011-04-06 13:07             ` Takashi Iwai
2011-04-06 13:19               ` Takashi Iwai
2011-04-08  2:06           ` Raymond Yau
2011-04-08  8:38             ` Valerio tesei
2011-04-08  9:28               ` OT: applying patches (was: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig) Paul Menzel
2011-04-08  9:47                 ` Valerio tesei
2011-04-08 10:27                   ` snd-hda-intel and parameter `patch` (was: OT: applying patches) Paul Menzel
2011-04-08 14:44                     ` snd-hda-intel and parameter `patch` David Henningsson
2011-04-10  1:21               ` [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-11  8:21                 ` Valerio tesei
2011-04-11 19:28                   ` Valerio Tesei
2011-04-13  8:52                     ` Raymond Yau
2011-04-13 11:08                       ` Valerio tesei
2011-04-13 19:12                         ` Valerio Tesei [this message]
2011-04-14 11:11                         ` Raymond Yau
2011-04-18 19:53                           ` Valerio Tesei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DA5F5B7.5010803@gmail.com \
    --to=valerio.tesei@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.