[mythtv-users] RE: Problems with alsa and SoundBlaster Audigy LS
William H. Gilmore
whgi at gms-online.com
Tue Nov 11 00:33:26 EST 2003
After doing some more research, it appears that the Audigy LS (PCI ID
1102:0007) is not supported by the currently emu10k1 or audigy drivers
available for kernel 2.4.22. And furthermore, I can't find any hits on
the web for any having modified the existing drivers to handle this. I
toyed with the idea of modifying the audigy (PCI ID 1102:0004)driver to
hit the 1102:0007 PCI ID but decided that I really didn't want to go
through the kernel build to make this happen.
So, it is likely that this card will be returned and placed for
something that is supported(:() in the kernel.
But, I'm still open to suggestions if there are any out there:)
Thanks,
William
-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of William H. Gilmore
Sent: Monday, November 10, 2003 9:10 PM
To: Discussion about mythtv
Subject: Problems with alsa and SoundBlaster Audigy LS
All,
I bought a SoundBlaster Audigy LS this afternoon to replace my whining
onboard audio. I have followed Jarod's instructions to a T, twice! But
alas, no luck! I receive the following error when attempting to insmod
the driver (whether by hand or at bootup).
[root at linux2 root]# /sbin/modprobe snd-emu10k1
/lib/modules/2.4.20-20_29.rh9.at/updates/sound/snd-emu10k1.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-20_29.rh9.at/updates/sound/snd-emu10k1.o: insmod
/lib/modules/2.4.20-20_29.rh9.at/updates/sound/snd-emu10k1.o failed
/lib/modules/2.4.20-20_29.rh9.at/updates/sound/snd-emu10k1.o: insmod
snd-emu10k1 failed
The OS is RH9.0 patched per Jarod's directions. alsa worked fine with
the onboard VIA8233 though it whined.
The Audigy is detected by the PCI bus per:
[root at linux2 root]# lspci -v
00:08.0 Multimedia audio controller: Creative Labs: Unknown device 0007
Subsystem: Creative Labs: Unknown device 1002
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at e800 [size=32]
Capabilities: [dc] Power Management version 2
00:08.1 Input device controller: Creative Labs: Unknown device 7005
Subsystem: Creative Labs: Unknown device 1002
Flags: bus master, medium devsel, latency 32
I/O ports at ec00 [size=8]
Capabilities: [dc] Power Management version 2
In reading on the alsa project site, I have found a few other people who
have had similar problems but there is no resolution posted. Do any of
you have any ideas?
Thanks in advance!
William
PS: My /etc/modules.conf is:
path[toplevel]=/lib/modules/`uname -r`/updates
# default path
path[toplevel]=/lib/modules/`uname -r`
# For bttv and saa7134
path[toplevel]=/lib/modules/`uname -r`/v4l2
#
alias eth0 via-rhine
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
# bttv
alias char-major-81 videodev
alias char-major-81-0 bttv
options bttv card=64 tuner=2 radio=1
options tuner debug=1
#alias char-major-81 bttv
alias char-major-195 nvidia
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
# OSS/Free compatability portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# Sound card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
# Save & restore settings
post-install snd-card-0 /usr/sbin/alsactl restore >/dev/null 2>&1 || :
pre-remove snd-card-0 /usr/sbin/alsactl store >/dev/null 2>&1 || :
More information about the mythtv-users
mailing list