From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000383]: Audigy LS - Capturing from Mic and kernel oops
Date: Tue, 13 Jul 2004 19:40:21 +0200 [thread overview]
Message-ID: <7c39458ab2caf677ebe0e086860fedaa@bugtrack.alsa-project.org> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000383
======================================================================
Reported By: Luke
Assigned To: pzad
======================================================================
Project: ALSA - driver
Bug ID: 383
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution:
Kernel Version:
======================================================================
Date Submitted: 07-13-2004 17:45 CEST
Last Modified: 07-13-2004 19:40 CEST
======================================================================
Summary: Audigy LS - Capturing from Mic and kernel oops
Description:
I just updated my cvs repository and rebuilt the snd_audigyls module to
check if my former reported bugs are fixed.
Unfortunateley, my kernel oopsed once again.
I tried to capture some voice of my mic with no success. Maybe I don't get
the explanation in the cvs log. I attached a screenshot to review my
alsamixer settings. This is what I used to configure it:
"The MIC and LINE IN use the AC97 chip.
The AC97 uses the PLAYBACK(Not CAPTURE) controls in alsamixer for
controlling CAPTURE. Then, instead of sending that output to the
speakers, it sends it to the Philips 1361T ADC. This results in high
quality ADC conversion.
E.g. For LINE IN capture, set LINE IN playback volume and unmute it.
Set MASTER volume.
There is a new control for "CAPTURE feedback into PLAYBACK". If one does
not want any feedback, leave it at it's minimum."
======================================================================
----------------------------------------------------------------------
jcdutton - 07-13-2004 19:40 CEST
----------------------------------------------------------------------
Fixed in latest cvs.
Fixed by:
[alsa-cvslog] CVS: alsa-kernel/core memalloc.c,1.34,1.35
Bug History
Date Modified Username Field Change
======================================================================
07-13-04 17:45 Luke New Bug
07-13-04 17:45 Luke File Added: audigyoops
07-13-04 17:50 Luke File Added: audigyscreen.png
07-13-04 19:40 jcdutton Bugnote Added: 0001415
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-07-13 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:40 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 18:15 [ALSA - driver 0000383]: Audigy LS - Capturing from Mic and kernel oops bugtrack
2004-08-27 18:14 bugtrack
2004-07-13 22:13 noreply
2004-07-13 15:45 noreply
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=7c39458ab2caf677ebe0e086860fedaa@bugtrack.alsa-project.org \
--to=noreply@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 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.