mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Takashi Iwai" <tiwai@suse.de>,
	"Romano Giannetti" <romano@dea.icai.upcomillas.es>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: ALC883 recording troubles...
Date: Sat, 28 Jun 2008 14:39:32 +0200	[thread overview]
Message-ID: <19f34abd0806280539g4961392evb469d7c106c198c9@mail.gmail.com> (raw)
In-Reply-To: <6278d2220806280529n70c6233dk1c5768df5d52acf@mail.gmail.com>

On Sat, Jun 28, 2008 at 2:29 PM, Daniel J Blueman
<daniel.blueman@gmail.com> wrote:
> Using your dumped config and
> ftp://202.65.194.211/pc/audio/ALC268_DataSheet_1.3.pdf page 42, your
> front mic pin complex is at node 19h; the mixers connecting to it are
> at nodes 0Bh, 22h and 23h, all at the second input index, so one of
> these should work:
>
> # ./hda-verb /dev/snd/hwC0D0 0x0b SET_AMP_GAIN_MUTE 0x7280
> # ./hda-verb /dev/snd/hwC0D0 0x22 SET_AMP_GAIN_MUTE 0x7280
> # ./hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x7280
>
> On my ALC883, we need to mute the first input instead, thus 0x7180.
> Can you see if the above helps you out?

Thanks for helping out!

Unfortunately, none of these commands (with either 0x7180 or 0x7280)
seems to make any difference at all. (I tried various combinations,
with reloading the driver in-between to undo the trial attempts.)


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-06-28 12:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 19:59 Daniel J Blueman
2008-06-10  5:59 ` Takashi Iwai
2008-06-11 19:00   ` Daniel J Blueman
2008-06-11 21:37     ` Daniel J Blueman
2008-06-12 10:45       ` Takashi Iwai
2008-06-12 10:49     ` Takashi Iwai
2008-06-12 13:03       ` Vegard Nossum
2008-06-12 13:12         ` Takashi Iwai
2008-06-12 13:48           ` Vegard Nossum
2008-06-12 13:52             ` Takashi Iwai
2008-06-12 13:55               ` Vegard Nossum
2008-06-12 14:01                 ` Vegard Nossum
2008-06-12 14:13                   ` Takashi Iwai
2008-06-12 14:02                 ` Takashi Iwai
2008-06-12 14:18                   ` Vegard Nossum
2008-06-12 14:23                     ` Takashi Iwai
2008-06-12 14:58                       ` Daniel J Blueman
2008-06-12 15:18                         ` Takashi Iwai
2008-06-12 16:55                       ` Vegard Nossum
2008-06-12 17:29                         ` Vegard Nossum
2008-06-12 17:53                           ` Takashi Iwai
2008-06-12 18:31                             ` Vegard Nossum
2008-06-12 21:50       ` Daniel J Blueman
2008-06-13 10:38         ` Romano Giannetti
2008-06-28  0:05       ` Daniel J Blueman
     [not found]         ` <19f34abd0806280311s115062e6vc6d0f304cb744934@mail.gmail.com>
     [not found]           ` <6278d2220806280329j2f77c52dp8fbae78420c136c1@mail.gmail.com>
2008-06-28 12:29             ` Daniel J Blueman
2008-06-28 12:39               ` Vegard Nossum [this message]
2008-06-28 13:24                 ` Daniel J Blueman
2008-06-28 13:46                   ` Vegard Nossum
2008-06-29 17:29                   ` Romano Giannetti
2008-06-29 21:33                     ` Daniel J Blueman
2008-08-14 19:10             ` Daniel J Blueman
2008-08-15 14:42               ` Takashi Iwai
2008-08-15 22:01                 ` Daniel J Blueman
2008-08-16  8:38                   ` Takashi Iwai
2008-08-16 13:37                     ` Daniel J Blueman
2008-08-16 17:00                       ` Takashi Iwai
2008-08-16 17:33                         ` Daniel J Blueman
2008-08-17  8:04                           ` Takashi Iwai
2008-06-10 12:22 ` Romano Giannetti
2008-06-10 12:53   ` Vegard Nossum

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=19f34abd0806280539g4961392evb469d7c106c198c9@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=daniel.blueman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romano@dea.icai.upcomillas.es \
    --cc=tiwai@suse.de \
    /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

all inboxes | Powered by JetHome®