From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001585]: No sound from Soundblaster Live USB since updating kernel drivers to 1.0.10.rc3
Date: Fri, 30 Dec 2005 20:08:54 +0100 [thread overview]
Message-ID: <f9177ce53fdad294c09524151d148f88@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1585>
======================================================================
Reported By: sailfrog
Assigned To: Clemens Ladisch
======================================================================
Project: ALSA - driver
Issue ID: 1585
Category: USB - usb-audio
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Debian
Kernel Version: > 2.6.14 (rc1, mm1, mm2, rc2)
======================================================================
Date Submitted: 11-21-2005 17:45 CET
Last Modified: 12-30-2005 20:08 CET
======================================================================
Summary: No sound from Soundblaster Live USB since updating
kernel drivers to 1.0.10.rc3
Description:
Every kernel since 2.6.14 (I have tried rc1, mm1, mm2, and rc2) has left
my external USB sound card broken. It appears to be something in the
alsa-git-2005-11-07.patch that was posted to LKML on 11/07/05:
subject: [ALSA UPDATE] 1.0.10rc3
message-id:
<Pine.LNX.4.61.0511071457480.8818@tm8103.perex-int.cz>
Applying this alsa update to 2.6.14 also renders the card silent. The
card
is visible in /proc/asound/cards, alsamixer sees it and I can adjust the
volume, but I get no sound from xmms, mplayer, etc. I tried enabling alsa
debug and verbose printk but I was unable to find any additional messages
from dmesg or in any log files. The card is a Creative Labs SoundBlaster
Live 24-bit external. I'm using the SPDIF output to run sound through a
home theater system. I'm running debian unstable on a Toshiba laptop.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 20:01
----------------------------------------------------------------------
"I guess if I want to stay with current kernels I will have to revert alsa
to < 1.0.10 if I want USB sound to work :("
Um, no, you'll just have to wait for this bug to be fixed.
----------------------------------------------------------------------
rlrevell - 12-30-05 20:08
----------------------------------------------------------------------
"It appears to be something in the
alsa-git-2005-11-07.patch that was posted to LKML on 11/07/05:
subject: [ALSA UPDATE] 1.0.10rc3
message-id: <Pine.LNX.4.61.0511071457480.8818@tm8103.perex-int.cz>"
OK so it broke between 1.0.10-rc2 and 1.0.10-rc3. Please use ALSA CVS to
do a binary search ("cvs update -D 2005-11-01 -A", "cvs update -D
2005-12-01 -A" etc) to identify the patch that broke it.
Issue History
Date Modified Username Field Change
======================================================================
11-21-05 17:45 sailfrog New Issue
11-21-05 17:45 sailfrog Distribution => Debian
11-21-05 17:45 sailfrog Kernel Version => > 2.6.14 (rc1, mm1,
mm2, rc2)
11-21-05 18:45 sailfrog Issue Monitored: sailfrog
11-22-05 07:54 Clemens LadischNote Added: 0006785
12-09-05 00:51 sailfrog Note Added: 0006965
12-09-05 16:46 smithbone Note Added: 0006968
12-22-05 02:25 sailfrog Note Added: 0007117
12-30-05 19:48 sailfrog Note Added: 0007251
12-30-05 20:01 rlrevell Note Added: 0007252
12-30-05 20:08 rlrevell Note Added: 0007254
======================================================================
-------------------------------------------------------
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 19:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 19:08 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 8:27 [ALSA - driver 0001585]: No sound from Soundblaster Live USB since updating kernel drivers to 1.0.10.rc3 bugtrack
2006-01-10 2:39 bugtrack
2006-01-09 5:32 bugtrack
2006-01-05 15:12 bugtrack
2006-01-04 15:30 bugtrack
2006-01-04 12:15 bugtrack
2006-01-04 10:06 bugtrack
2006-01-04 8:58 bugtrack
2005-12-31 7:54 bugtrack
2005-12-31 6:10 bugtrack
2005-12-31 4:37 bugtrack
2005-12-31 4:33 bugtrack
2005-12-31 4:31 bugtrack
2005-12-31 2:47 bugtrack
2005-12-31 1:32 bugtrack
2005-12-30 19:43 bugtrack
2005-12-30 19:41 bugtrack
2005-12-30 19:34 bugtrack
2005-12-30 19:31 bugtrack
2005-12-30 19:01 bugtrack
2005-12-30 18:48 bugtrack
2005-12-22 1:25 bugtrack
2005-12-09 15:46 bugtrack
2005-12-08 23:51 bugtrack
2005-11-22 6:54 bugtrack
2005-11-21 16:45 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=f9177ce53fdad294c09524151d148f88@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