From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001720]: Audigy LS only produces noise instead playing music
Date: Sat, 7 Jan 2006 14:19:44 +0100 [thread overview]
Message-ID: <8226d8fe4c0352319ede3aeb494da83c@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1720>
======================================================================
Reported By: Nukem36JL
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1720
Category: PCI - ca0106
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: SuSE
Kernel Version: 2.6.13-15-default
======================================================================
Date Submitted: 01-05-2006 18:16 CET
Last Modified: 01-07-2006 14:19 CET
======================================================================
Summary: Audigy LS only produces noise instead playing music
Description:
lspci:
00:0c.0 Multimedia audio controller: Creative Labs SB Audigy LS
While trying to play a wave- file the card produces noise only. Effect is
the same for all kind of players including aplay, ogg123 .... The card is
used together with another card, which works properly.
Module snd-ca0106 loads without error messages.
======================================================================
----------------------------------------------------------------------
Nukem36JL - 01-07-06 10:29
----------------------------------------------------------------------
In alsamixer card is displayed as "CA0106" Chip is empty. Maybe this causes
the Problem.
----------------------------------------------------------------------
jcdutton - 01-07-06 14:19
----------------------------------------------------------------------
Please post the output of:
cat /proc/asound/version
cat /proc/asound/cards
lspci -vn | grep -1 0401
Issue History
Date Modified Username Field Change
======================================================================
01-05-06 18:16 Nukem36JL New Issue
01-05-06 18:16 Nukem36JL Distribution => SuSE
01-05-06 18:16 Nukem36JL Kernel Version => 2.6.13-15-default
01-05-06 18:19 Nukem36JL Issue Monitored: Nukem36JL
01-07-06 10:29 Nukem36JL Note Added: 0007511
01-07-06 14:19 jcdutton Note Added: 0007512
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-07 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:19 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 20:51 [ALSA - driver 0001720]: Audigy LS only produces noise instead playing music bugtrack
2006-01-09 20:49 bugtrack
2006-01-09 20:48 bugtrack
2006-01-09 20:48 bugtrack
2006-01-09 16:48 bugtrack
2006-01-07 9:29 bugtrack
2006-01-05 17:16 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=8226d8fe4c0352319ede3aeb494da83c@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