From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001218]: Line-In and Mic-In do not work
Date: Wed, 6 Jul 2005 23:26:12 +0200 [thread overview]
Message-ID: <8280b4084eb010d368b448e01e5afa7a@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1218>
======================================================================
Reported By: hugo4711
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1218
Category: PCI - emu10k1
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Fedora Core 4
Kernel Version: 2.6.11-1.1369_FC4
======================================================================
Date Submitted: 06-28-2005 20:03 CEST
Last Modified: 07-06-2005 23:26 CEST
======================================================================
Summary: Line-In and Mic-In do not work
Description:
Capturing from Line-In and Mic-In don't work. I have connected a
bttv-tv-card with Line-In and I cannot hear the sound output from it.
Every single input is at 100% using alsamixer and kmix. This happened
after an update from FC3 to FC4. Before the update everything was fine.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0001216 Microphone does not work
======================================================================
----------------------------------------------------------------------
cpitchford - 06-29-05 23:08
----------------------------------------------------------------------
I have an audigy1 card and have noticed that line in wasn't working and
that the "live-drive" inputs were missing (aux2, line2, etc) This appeared
to be the case since 2.6.12-rc2. Line in definately works on 2.6.12-rc1
however so that fault was introduced between these two kernel versions.
Now running with 2.6.12.1 and the fault remains, installing 1.0.9b fixes
it again. I think merging the fixed 1.0.9b into the kernel would solve it,
though I'm not an expert
----------------------------------------------------------------------
rlrevell - 07-06-05 23:26
----------------------------------------------------------------------
Fixed in CVS. Should also be fixed in the nest stable kernel release.
Issue History
Date Modified Username Field Change
======================================================================
06-28-05 20:03 hugo4711 New Issue
06-28-05 20:03 hugo4711 Distribution => Fedora Core 4
06-28-05 20:03 hugo4711 Kernel Version => 2.6.11-1.1369_FC4
06-29-05 06:28 netslayer Note Added: 0005303
06-29-05 08:33 rlrevell Note Added: 0005304
06-29-05 10:08 hugo4711 Note Added: 0005305
06-29-05 23:08 cpitchford Note Added: 0005319
07-06-05 22:10 rlrevell Relationship added duplicate of 0001216
07-06-05 23:26 rlrevell Note Added: 0005397
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-06 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 21:26 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-06 21:27 [ALSA - driver 0001218]: Line-In and Mic-In do not work bugtrack
2005-07-06 20:10 bugtrack
2005-06-29 21:08 bugtrack
2005-06-29 8:08 bugtrack
2005-06-29 6:33 bugtrack
2005-06-29 4:28 bugtrack
2005-06-28 18:03 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=8280b4084eb010d368b448e01e5afa7a@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