Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 597019 - No sound coming from Soundblaster ca0106 (but works fine via internal audio)
No sound coming from Soundblaster ca0106 (but works fine via internal audio)
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-27 19:17 EDT by John Curcio
Modified: 2011-02-16 19:50 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-02-16 19:50:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Results of dmesg, lspci, /proc/asound/cards & lsmod (67.83 KB, application/octet-stream)
2010-05-27 19:17 EDT, John Curcio
no flags Details

  None (edit)
Description John Curcio 2010-05-27 19:17:20 EDT
Created attachment 417421 [details]
Results of dmesg, lspci, /proc/asound/cards & lsmod

Description of problem: No sound coming from Soundblaster CA0106 add-on sound card

Version-Release number of selected component (if applicable):

How reproducible: All the time

Steps to Reproduce:
1.Use any media player (have tried, banshee, listen and exaile)
2.Select song
Actual results:No sound

Expected results:Sound from speaker

Additional info:
Using GUI tool "System Settings" in KDE, selecting "Multimedia", I can test the card and will hear the test sounds. I have also verified that KMIX is not muting the card and that the volume is set reasonably. [Also verify sound level of speakers are adequate.] I have verified this on two separate speaker systems and have also attempted using Soundblaster Creative X-fi card, but get same results. Internal (Intel?) audio works just fine.

Note You need to log in before you can comment on or make changes to this bug.