Red Hat Bugzilla – Bug 68183
Soundblaster Audigy not supported
Last modified: 2008-05-01 11:38:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
Description of problem:
redhat-config-soundcard detects SB Audigy but does not know which kernel module
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Limbo on a PC with a SB Audigy soundcard
2. Try to configure sound under the first-time setup wizard
3. Try running redhat-config-soundcard from GNOME's System menu
Actual Results: Trying to configure from the first-time setup wizard does not
work; nothing happens when I click on the configure button. Running redhat-
config-soundcard manually, it identified the soundcard but could not suggest
any kernel modules.
This is my friend's computer; he had the same soundcard configured properly
under Mandrake previously - probably the emu10k1 module.
Expected Results: Sound card configured properly, emu10k1 module loaded on
start-up by /etc/init.d/sound
This is the output of lspci -v for the main device entry; there are two other
entries, one for a FireWire OHCI port and one for the Gameport/MIDI.
00:08.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Subsystem: Creative Labs: Unknown device 0053
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at d000 [size=32]
Capabilities: [dc] Power Management version 2
I've also noticed this in RH7.3 kernel's 2.4.18-3 2.4.18-4 and now 2.4.18-5.
The work around is to compile a kernel from source without the emu10k1 module.
Afterwards use the audigy driver found at sourceforge. I'm currently using
2.4.18-4-athlon successfully with the audigy following this method.
Audigy driver added as extra driver for the next build
audigy drivers are now present with kernel-2.4.18-12.3.