mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: ALC883 recording troubles...
Date: Thu, 12 Jun 2008 12:45:16 +0200	[thread overview]
Message-ID: <s5hk5gv0w5f.wl%tiwai@suse.de> (raw)
In-Reply-To: <6278d2220806111437m22b16795i9650bad8f93120e6@mail.gmail.com>

At Wed, 11 Jun 2008 22:37:49 +0100,
Daniel J Blueman wrote:
> 
> On Wed, Jun 11, 2008 at 8:00 PM, Daniel J Blueman
> <daniel.blueman@gmail.com> wrote:
> > On Tue, Jun 10, 2008 at 6:59 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >> At Mon, 9 Jun 2008 20:59:00 +0100,
> >> Daniel J Blueman wrote:
> >>>
> >>> Hi Takashi-san,
> >>>
> >>> I'm experiencing DC offset with the microphone on 2.6.24 (Ubuntu 8.04
> >>> LTS x86-64). I can see on Audacity that the DC offset that varies with
> >>> the recording capture level.
> >>
> >> Could you elaborate?  The mic bias level could be changed via the pin
> >> control value.  Usually, it's set as VREF 80%.
> >
> > When the recording->capture level is set to 0, the mic has no DC
> > offset as expected. Maxing the recording->capture level, the mic input
> > is saturated, in between, we see a linear connection.
> >
> >>> Plus, the mixer playback->mic-boost
> >>> muting enables/disables mic-boost in recording.
> >>
> >> This is a known bug in alsa-lib mixer abstraction.  No kernel issue.
> >
> >>> It feels like the ALC883 pins aren't configured quite right. The mobo
> >>> is an Asus P5E-VM with current BIOS [1]
> >>>
> >>> What's the routine to debug this? Would it help to install windows,
> >>> dump the register space and compare?
> >>
> >> You can find *.INI file that contains the default pin configuration
> >> in Windows.  This might be useful in the case BIOS is broken but
> >> Windows does a black magic.
> >
> > That'll be these defaults stashed in the INF file [2]. Let me know if
> > it's not what you expected and I'll publish the complete INF file.
> >
> >> Anyway, please run alsa-info.sh with --no-upload option and show the
> >> generated file here.  It contains the codec information and mixer
> >> setup.
> >>        http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh
> >
> > See [3].
> 
> >> Also, you can adjust the pin setting on the fly via hda-verb utility
> >> below:
> >>        http://ftp.suse.com/pub/people/tiwai/misc/hda-verb-0.2.tar.bz2
> >>
> >> Don't forget to build snd-hda-intel module with
> >> CONFIG_SND_HDA_HWDEP=y to use this command.
> >
> > I'll give this a shot if I get time.
> 
> Looking at the datasheet and ALSA report, changing the front mic node
> id also affects capturing from the (rear) mic input.

Depends on the hardware implementation.  But, usually, no, different
pin widgets are assigned for front and mic jacks.

> ftp://66.104.77.130/pc/audio/ALC883_DataSheet_1.3.pdf
> 
> We get the "hda_codec: Unknown model for ALC883, trying auto-probe
> from BIOS..." kernel message, so we may need to tweak
> pci/hda/patch_realtek.c.

Note that this is no error but information.  The driver has preset
models for known devices and use the static configuration table for
such devices.  For other devices, the driver just relies on BIOS
setup.

> Also, I can reproduce the problem the with HD
> and legacy front-panel audio settings in the BIOS. Do you know a way
> to dump eg the pin configuration in windows or other useful state, so
> I can compare with all the possible node ID configuration values?

Sorry, no, I've not booted Windows over years :)


Takashi

  reply	other threads:[~2008-06-12 10:45 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 [this message]
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
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=s5hk5gv0w5f.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=daniel.blueman@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®