From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001323]: MIC jack not supported
Date: Fri, 12 Aug 2005 23:09:42 +0200 [thread overview]
Message-ID: <f26b11b0da4047d6777fe363c8ac63b4@bugtrack.alsa-project.org> (raw)
The following issue requires your FEEDBACK.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1323>
======================================================================
Reported By: submax82
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1323
Category: PCI - ca0106
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Distribution: debian 3.1 sarge
Kernel Version: linux 2.6.12.4
======================================================================
Date Submitted: 08-08-2005 22:10 CEST
Last Modified: 08-12-2005 23:09 CEST
======================================================================
Summary: MIC jack not supported
Description:
The problem is simple but important! The alsamixer do not show the volume
of the MIC therefore this do not work!
======================================================================
----------------------------------------------------------------------
rlrevell - 08-10-05 05:21
----------------------------------------------------------------------
Known problem, capture is not supported in that ALSA version. You need the
latest ALSA sources from CVS (I think 1.0.9b also supports capture with
that device).
----------------------------------------------------------------------
jcdutton - 08-12-05 23:09
----------------------------------------------------------------------
Waiting for feedback. Does upgrading to alsa-driver 1.0.9b help?
Issue History
Date Modified Username Field Change
======================================================================
08-08-05 22:10 submax82 New Issue
08-08-05 22:10 submax82 Distribution => debian 3.1 sarge
08-08-05 22:10 submax82 Kernel Version => linux 2.6.12.4
08-08-05 22:59 submax82 Issue Monitored: submax82
08-08-05 23:00 submax82 Note Added: 0005714
08-10-05 05:21 rlrevell Note Added: 0005746
08-12-05 23:09 jcdutton Note Added: 0005790
08-12-05 23:09 jcdutton Status assigned => feedback
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-12 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 21:09 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-13 12:21 [ALSA - driver 0001323]: MIC jack not supported bugtrack
2005-11-06 23:06 bugtrack
2005-09-25 2:00 bugtrack
2005-09-15 4:44 bugtrack
2005-09-10 8:39 bugtrack
2005-08-13 12:28 bugtrack
2005-08-10 3:21 bugtrack
2005-08-08 21:00 bugtrack
2005-08-08 20:10 bugtrack
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=f26b11b0da4047d6777fe363c8ac63b4@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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