From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001036]: Replacement SB Live card not detected
Date: Fri, 30 Dec 2005 04:22:21 +0100 [thread overview]
Message-ID: <da3234e9d2b2ba71b73da44df3eb2487@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1036>
======================================================================
Reported By: grolschie
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1036
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian
Kernel Version: 2.6.3
======================================================================
Date Submitted: 04-05-2005 02:10 CEST
Last Modified: 12-30-2005 04:22 CET
======================================================================
Summary: Replacement SB Live card not detected
Description:
Hi there.
I have been using my SB Live Value PCI for over a year with ALSA with no
problems. I recently swapped the card for a newer SB Live 5.1 DE PCI card.
Even though these cards are pretty much the same, alsaconf cannot detect
any supported sound cards. lspci shows that the new card is indeed
detected.
Regards,
grolschie
======================================================================
----------------------------------------------------------------------
pzad - 04-05-05 10:20
----------------------------------------------------------------------
This can by sb live (c) 2003 with STAC9758. Some older alsa versions had
bug for this card - card was sillent. And proper support was added in alsa
1.0.5.
kernel 2.6.3 contains old alsa. Try to upgrade to never alsa.
----------------------------------------------------------------------
rlrevell - 12-30-05 04:22
----------------------------------------------------------------------
Any improvement with later releases?
Issue History
Date Modified Username Field Change
======================================================================
04-05-05 02:10 grolschie New Issue
04-05-05 02:10 grolschie Distribution => Debian
04-05-05 02:10 grolschie Kernel Version => 2.6.3
04-05-05 02:12 grolschie Note Added: 0004333
04-05-05 08:30 pzad Note Added: 0004334
04-05-05 08:55 grolschie Note Added: 0004335
04-05-05 10:20 pzad Note Added: 0004336
12-30-05 04:22 rlrevell Note Added: 0007205
======================================================================
-------------------------------------------------------
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:[~2005-12-30 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 3:22 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 2:09 [ALSA - driver 0001036]: Replacement SB Live card not detected bugtrack
2005-12-31 1:42 bugtrack
2005-12-30 23:32 bugtrack
2005-04-05 8:20 bugtrack
2005-04-05 6:55 bugtrack
2005-04-05 6:30 bugtrack
2005-04-05 0:12 bugtrack
2005-04-05 0: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=da3234e9d2b2ba71b73da44df3eb2487@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