From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000773]: Kernel 2.6.10 with ALSA 1.08rc1 from CVS (12/30/2004)
Date: Sat, 1 Jan 2005 23:02:21 +0100 [thread overview]
Message-ID: <20050101220221.5CD5533F@alsa.alsa-project.org> (raw)
Audigy2 Value - SB0400 card
Audigy2 Value- AUX-In and LINE-IN no sound
Message-ID: <2f7bc01a0f26baa27c2ba60b2586ad08@bugtrack.alsa-project.org>
X-Priority: 3
X-Mailer: PHPMailer [version 1.72]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=773>
======================================================================
Reported By: hodgesw
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 773
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: 1.08rc1
Kernel Version: 2.6.10
======================================================================
Date Submitted: 01-01-2005 01:21 CET
Last Modified: 01-01-2005 23:02 CET
======================================================================
Summary: Kernel 2.6.10 with ALSA 1.08rc1 from CVS
(12/30/2004)
Audigy2 Value - SB0400 card
Audigy2 Value- AUX-In and LINE-IN no sound
Description:
Kernel 2.6.10 with ALSA 1.08rc1 from CVS (12/30/2004)
Audigy2 Value - SB0400 card
After trying many modprobe.preload/modprobe.conf alternatives I
manually loaded driver using "modprobe -v snd-emu10k1"
with /etc/modprobe.conf: "options snd-emu10k1 extin="0x3fff"
After setting alsamixer volumes
"speakertest" works; "aplay" produces good sound; mic produces good
sound;
"line in" does not work; "auxin" does nor work.
kde configure plays sound.
xmms cannot find sound card.
======================================================================
----------------------------------------------------------------------
rlrevell - 01-01-05 22:01
----------------------------------------------------------------------
This is a new driver after all (though based on emu10k1), its quite
possible there's a bug. Can you try Windows to verify the hardware is OK?
----------------------------------------------------------------------
pzad - 01-01-05 23:02
----------------------------------------------------------------------
do
alsactl -f test.state store
and attach test.state
Issue History
Date Modified Username Field Change
======================================================================
01-01-05 01:21 hodgesw New Issue
01-01-05 01:21 hodgesw Distribution => 1.08rc1
01-01-05 01:21 hodgesw Kernel Version => 2.6.10
01-01-05 02:27 rlrevell Note Added: 0003029
01-01-05 16:13 hodgesw Note Added: 0003032
01-01-05 18:44 rlrevell Note Added: 0003033
01-01-05 20:35 pzad Note Added: 0003035
01-01-05 21:51 hodgesw Note Added: 0003036
01-01-05 22:01 rlrevell Note Added: 0003037
01-01-05 23:02 pzad Note Added: 0003040
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-01 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 22:02 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-16 14:32 [ALSA - driver 0000773]: Kernel 2.6.10 with ALSA 1.08rc1 from CVS (12/30/2004) bugtrack
2005-04-18 21:20 bugtrack
2005-01-05 1:07 bugtrack
2005-01-04 18:50 bugtrack
2005-01-03 21:48 bugtrack
2005-01-02 8:20 bugtrack
2005-01-02 3:00 bugtrack
2005-01-01 23:30 bugtrack
2005-01-01 21:01 bugtrack
2005-01-01 20:51 bugtrack
2005-01-01 19:35 bugtrack
2005-01-01 17:44 bugtrack
2005-01-01 15:13 bugtrack
2005-01-01 1:27 bugtrack
2005-01-01 0:21 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=20050101220221.5CD5533F@alsa.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 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.