alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@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: Sun, 10 Apr 2011 09:21:35 +0800	[thread overview]
Message-ID: <BANLkTimcFQRMmjT9+FhJXnkNqNQPTMHZNQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikhM1i8PK8HC9yN6d8yevx982CwGw@mail.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



>
> 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



> 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


> 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*

  parent reply	other threads:[~2011-04-10  1:21 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               ` Raymond Yau [this message]
2011-04-11  8:21                 ` [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig 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
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=BANLkTimcFQRMmjT9+FhJXnkNqNQPTMHZNQ@mail.gmail.com \
    --to=superquad.vortex2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).