Red Hat Bugzilla – Bug 265181
Audigy SE soundcard detection fails
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
After upgrading to an Audigy SE soundcard Fedora 7 sound was lost
Version-Release number of selected component (if applicable):
Install an Audigy SE card
Steps to Reproduce:
1. Install audigy se card
2. Run soundcard detection
3. Sound fails to play
sound fails to play
1 [CA0106 ]: CA0106 - CA0106
Audigy SE [SB0570] at 0xdc00 irq 11
alias eth0 8139too
alias scsi_hostadapter pata_via
alias scsi_hostadapter1 usb-storage
options snd cards_limit=8
alias snd-card-1 snd-ca0106
options snd-ca0106 index=1
alias snd-card-7 snd-usb-audio
options snd-usb-audio index=7
------- System Config Soundcard Log --------
Wed Aug 29 16:24:18 EDT 2007
aplay: main:545: audio open error: Device or resource busy
Running from command-line...
Created attachment 179721 [details]
/root/scsconfig.log text file
I did some research on this bug. Alsa's web site suggested recent changes to the
libraries would make the ca0106 cards work. I grabbed the alsa driver,library
and kernel from Fedora 8 repo. Upon reboot and running system-config-sound sound
was functional with the Audigy SE card on Fedora 7. The latest alsa driver fixed
> aplay: main:545: audio open error: Device or resource busy
Your card looks occupied by another application....
Anyway, alsa-drivers should be the same in f7 and f8. So do the f8 packages work
for you and the f7 ones don't?
Created attachment 296510 [details]
scsconfig.log (Alsa play test sound failed!)
Fedora core 8 (Alsa test sound failed!)
Created attachment 296511 [details]
scsrun.log (Alsa sound test failed)
this is the second log generated by alsa sound test!
Which version of ALSA works for you? The current fedora version is 1.0.15, the
latest is 1.0.16.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.