public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
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: Sat, 31 Dec 2005 08:54:15 +0100	[thread overview]
Message-ID: <1b9fb14c8f5b29e99548ecd28327de83@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-31-2005 08:54 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. 

======================================================================

----------------------------------------------------------------------
 smithbone - 12-31-05 07:10 
----------------------------------------------------------------------
yes they both get called:

Dec 31 00:06:14 Vedit kernel: snd_usb_pcm_playback_trigger()
Dec 31 00:06:17 Vedit kernel: prepare_startup_playbak_urb()
Dec 31 00:06:17 Vedit kernel: prepare_startup_playbak_urb()
Dec 31 00:06:17 Vedit kernel: snd_usb_pcm_playback_trigger()

----------------------------------------------------------------------
 afran - 12-31-05 08:54 
----------------------------------------------------------------------
Just wanted to let you know, I've got the same problem here with my
Terratec Phase 26 USB (since kernel release 2.6.15-rc1, now running
2.6.14.4 and ALSA 1.0.10rc1 without problems): Everything loads up fine
but no sound is played, not even at the card's own headphone connector (so
it's not a problem with SPDIF).

But there is some other yet similar problem, I've recognized earlier:
Sometimes (perhaps once in 2 weeks, happens quite randomly) everything
would load up fine, but the card would not give any sound (as above). When
this happens I have to plug the card's USB cable and reconnect (just
resetting volume level and mute doesn't work, I've not been able to check
whether reloading the driver as kernel module would help).

Unfortunately, I've not been able to reproduce the latter problem as it
seems to be happening without any clue as to what may have caused it, plus
it only occurs very seldomly, about every 30th or 40th reboot.

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                          
12-30-05 20:31 sailfrog       Note Added: 0007256                          
12-30-05 20:34 rlrevell       Note Added: 0007257                          
12-30-05 20:41 sailfrog       Note Added: 0007258                          
12-30-05 20:43 rlrevell       Note Added: 0007259                          
12-31-05 02:32 smithbone      Note Added: 0007319                          
12-31-05 03:45 rlrevell       File Added: alsa-git-2005-11-07-usbaudio.patch    
               
12-31-05 03:47 rlrevell       Note Added: 0007331                          
12-31-05 05:31 smithbone      Note Added: 0007343                          
12-31-05 05:33 rlrevell       Note Added: 0007344                          
12-31-05 05:37 rlrevell       Note Added: 0007345                          
12-31-05 07:10 smithbone      Note Added: 0007347                          
12-31-05 08:54 afran          Note Added: 0007354                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-12-31  7:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31  7:54 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  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:08 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=1b9fb14c8f5b29e99548ecd28327de83@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