Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rimas Kudelis <rq@akl.lt>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Rimas Kudelis <rq@akl.lt>, alsa-devel@lists.sourceforge.net
Subject: Re: Test model
Date: Thu, 16 Feb 2006 11:29:27 +0200	[thread overview]
Message-ID: <20060216092927.GA32525@soften.ktu.lt> (raw)
In-Reply-To: <200602152348.k1FNm4nq021338@auster.physics.adelaide.edu.au>

Good morning,

On Thu, Feb 16, 2006 at 10:18:04AM +1030, Jonathan Woithe wrote:
> I'm now trying out the test model for ALC260. I've already managed to
> > get sound from the Line In jack and Microphone jack. I've also managed
> > to get the internal Mic working.
> 
> Excellent.  Out of interest, which control appears to be connected to
> the internal mic?

Well it's not too surprising. The internal microphone is connected to
the "MIC1" control. And the external too. Whenever I plug something into
the external microphone jack, the internal one gets automatically muted.

The Line In jack is connected to LINE1 control.

Master volume seems to be controlled by LOUT1 control. By muting this, i
get absolute silence.

And the last thing i've found so far is that PCM channel is the one that
Totem media player uses to play its sound. Also, it's used by Sound
Juicer to play the CD. I wonder though - why isn't a Mute control
available for it?


> > However, I haven't heard any sound from either integrated speakers nor the
> > headphones jack. Even after switching a lot of controls in mixer.
> 
> Interesting.  Perhaps the easiest way forward in that case is to switch
> every jack control to "line out" or "headphone out", unmute everything and
> turn up every control to maximum. Then see if you get sound out in any form
> from the internal speaker.  If we get sound at least we know it's possible
> and you can then work backwards to find the controls which affect it.  If we
> don't then there's some head-scratching to do.

That's what I tried yesterday. Switched all controls to Line Out. That's
how I found out what Mic and Line In jacks are connected to. Now these
two are set to Mic and Line In types, respectively. And everything else
is Line Out. Nothing... Same happens when everything else is set to
Headphones.

Btw, when I redirect the output to Line In, and make everything else
(HP-OUT, LINE-OUT, LINE2 and MIC2) be "Headphone" pins, I get a lot of noise 
from the speakers connected to the Line In jack. These seem to catch
some interference even from the video card (just noticed). That
electronic noise differs depending on what I see in the screen atm. Weird...

> It is available, yes.  It's pin widget 0x15, referred to as "LINE2" in
> the mixer controls.  Including it in the test model didn't appear to cause
> any trouble on my laptop during development so I left it in.  I'm yet to
> revisit the reasons as to why I had trouble with this NID during the
> initial S7020 development - currently I suspect a typo which I failed to
> notice at the time.
> 
> Note also that the problem I had was that sending an initverb to this pin
> caused *all* sound to stop.  Since you get sound out of other jacks when
> using the test model I don't think your lack of sound from the headphone
> jack is due to this problem.

Maybe. I just though that maybe it doesn't really mute all the sound,
but just some pins?

I'm almost out of any ideas. :/ Could it be that the notebook uses
digital i/o for its internal speakers/heaphone jack or something like
this?

Rimas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-16  9:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 22:49 Test model Rimas Kudelis
2006-02-15 23:48 ` Jonathan Woithe
2006-02-16  9:29   ` Rimas Kudelis [this message]
2006-02-16 10:05     ` Rimas Kudelis
2006-02-17  2:05       ` Jonathan Woithe
2006-02-16 10:08     ` Paulo Matias
2006-02-16 16:52       ` Rimas Kudelis
2006-02-17  2:14         ` Jonathan Woithe
2006-02-17  2:12       ` Jonathan Woithe
2006-02-17  1:59     ` Jonathan Woithe
2006-02-17 12:07       ` Rimas Kudelis
2006-02-17 12:57         ` Paulo Matias
2006-02-17 13:17           ` Rimas Kudelis
2006-02-17 18:18             ` Rimas Kudelis
2006-02-17 18:24               ` Paulo Matias
2006-02-17 18:36                 ` Rimas Kudelis
2006-02-20  0:44           ` Jonathan Woithe
2006-02-17 18:40         ` Paulo Matias
2006-02-20  0:27         ` Jonathan Woithe
2006-02-19 17:05       ` Rimas Kudelis
2006-02-19 23:33         ` Jonathan Woithe
2006-02-20  5:32           ` Rimas Kudelis
2006-02-20  6:32             ` Jonathan Woithe
2006-02-20  7:13               ` Rimas Kudelis
2006-02-20 23:17                 ` Jonathan Woithe
2006-02-21 10:17                   ` Rimas Kudelis
2006-02-21 23:20                     ` Jonathan Woithe
2006-02-22  6:40                       ` Rimas Kudelis
2006-02-22 23:50                         ` Jonathan Woithe

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=20060216092927.GA32525@soften.ktu.lt \
    --to=rq@akl.lt \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    /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