From: Takashi Iwai Subject: Re: snd-hda-intel, AD 1988b: SPDIF output not working correctly, volume low for analog output Date: Fri, 20 Jul 2007 15:47:55 +0200 Message-ID: References: <200707170832.01976.ml_alsa@mortal-soul.de> <200707171822.58228.ml_alsa@mortal-soul.de> <200707200829.03682.ml_alsa@mortal-soul.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (ns.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id B44CC103860 for ; Fri, 20 Jul 2007 15:47:55 +0200 (CEST) In-Reply-To: <200707200829.03682.ml_alsa@mortal-soul.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Matthias Dahl Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Fri, 20 Jul 2007 08:29:02 +0200, Matthias Dahl wrote: > > On Thursday 19 July 2007 15:50:19 Takashi Iwai wrote: > > > So, the primary problem is rather the 6stack-dig preset doesn't match > > with your device. The SPDIF problem seems independent, though, but > > we'd better to fix the stuff first. > > > > With auto model, do you get louder output from the analog out? > > Just tested it and as far as I can tell, only spdif seems a lot louder, analog > output is equal to 6stack-dig. OK. You may be able to figure out what influences on the volume by comparing /proc/asound/card0/codec#* file on both models. > Reminds me what also a bit strange: the PCM mixer control only appears after I > have played back something. > > On detail: - unload alsa, rm asound.state, load alsa, alsamixer (no pcm vol) > - play back something, alsamixer (pcm volume is there) > > From there on, it'll always be visible, even after restarts. I also do not > have any channel configuration control (2/4/6 channels). It's just not there. > No matter if I use auto or 6stack-dig. This is expected behavior. The PCM volume is implemented via softvol plugin, and it creates dynamically at the first run. But, usually, it's restored via alsactl at the next boot. > > The first thing to do is to check which pin widget corresponds to the > > real I/O jacks. It's a guess work and trial-and-error. > > Sounds a lot like digging into patch_analog.c (a long change/recompile/test > cycle) or is there a way to figure this stuff out during runtime...? Could > you please elobrate on what I should do? Thanks. Yes, it'll involve with patch_analog.c deeply. Basically you need to modify init verb table and the mixer element table. Check the AD1988B datasheet, and try to assign the different PIN (and corresponding mixer / selector widgets) in init verb and mixer tables. Then, rebuild driver, and try the driver until you get the complete mapping of pin widgets. Takashi