Red Hat Bugzilla – Bug 132401
Soundcard detection utility produces an error while loading sound card driver
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Description of problem:
When I use the Sound Card Detection Utility provided with the linux
installation, it show me two sound cards. The first one is the Intel
i810 AC97 and the second one is the SBLive Emu10K. But when I try to
play the test sound for any sound card, it displays the message that
it is unable to load the driver for the sound card. When I press OK
on this dialog then if SBLive card is selected, I can hear the sound
played by the utility but if i810 AC97 is selected then no sound is
Selecting the SBLive card as the primary device lets me use sound
applications but still it does displays the 'unable to load driver'
error. I dont know why.
I used RedHat Linux 9 and every thing was perfect there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start Sound Card Detection Utility
2.Click 'Play Test Sound' Button
Actual Results: An error message was displayed specifying the it was
unable to load drivers for the particular sound card
Expected Results: Test sound should be played on the selected sound
card without any errors
I have a Pentium IV 2.80C processor on an Intel 865GBF motherboard.
It has an onboard integrated audio and I have installed another
Creative SBLive 4.1 Channel Sound Card also.
Could you please attach the file /etc/sysconfig/hwconf as well as your
I would also advise you to contact your support representatives to try
and deal with this issue, quoting this bug number.
Created attachment 104303 [details]
Created attachment 104304 [details]
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.