All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ivica Bukvic <ico@fuse.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [revisited] bug? with cs4205 and intel8x0 module
Date: Wed, 05 Mar 2003 18:51:39 +0100	[thread overview]
Message-ID: <s5hfzq1itw4.wl@alsa2.suse.de> (raw)
In-Reply-To: <000001c2e326$e48d40c0$aa1f830a@ICO>

At Wed, 5 Mar 2003 09:52:49 -0500,
Ivica Bukvic wrote:
> 
> Hi all, 
> 
> A while ago I posted this message, although mixed with some other false
> assumptions of mine -- apologies for my ignorance( see:
> http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg05286.ht
> ml thread) and then did the same thing just a couple days ago with the
> whole output log as requested (see:
> http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg06824.ht
> ml).
> 
> Basically, the problem remains -- that I can select the recordable audio
> input from alsamixer without any problems, but I cannot do the same from
> Kmix (KDE mixer), nor from the aumix. The second message contains all
> the pertinent info (for instance I can select Line-input as my recording
> source, but not the Mic-input).

perhaps the problem is that there are both "Mic Capture Volume/Switch"
and "Capture Route".  and the oss-emulation layer chooses the former
while the latter must be set, too.

hmm, we'll need a workaround here...


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

      reply	other threads:[~2003-03-05 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 14:52 [revisited] bug? with cs4205 and intel8x0 module Ivica Bukvic
2003-03-05 17:51 ` Takashi Iwai [this message]

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=s5hfzq1itw4.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ico@fuse.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.