Thanks for the response!
I responded to your points below. modprobe can find the driver, but doesn't
likeit. aumix can't open /dev/mixer.
Any recommendations for a next step?
Regards, Frank K
On Monday 16 June 2003 01:17 am, John Haxby wrote:
> Frank K wrote:
> >KDE flashes every login: "can't open /dev/dsp". That looks like this:
> >crw------- 1 frankk root 14, 3 Jan 30 02:24 /dev/dsp
> >(I don't know what the "c" means) I haven't tried to chmod this.
> >The audio, mixer, etc have the same ACLs.
>
> The "c" means "character special" -- it's one of two types of device file.
>
> >lspci tells me I have a Creative SB Live that needs the EMU10k1X driver:
> >02:02.0 Multimedia audio controller: Creative Labs [SB Live! Value]
> > EMU10k1X
>
> So far so good.
>
> >I built the driver module and installed it in
> >/lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/ as emu10k1.o
>
> Why? It's already there isn't it?
>
>From sndconfig:
A PCI sound card was found in your system. The details are:
Model: Creative Labs|[SB Live! Value] EMU10k1X
EMU10k1X is not supported.
The driver tarball is available from sourceforge.
> >I added "alias sound emu10k1" to /etc/modules.conf. That line shows up in
> >modprobe --showconfig.
>
> Ahh. This is probably where you are going wrong. To check just do
>
> modprobe emu19k1
root[2163] modprobe emu10k1
/lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/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-6/kernel/drivers/sound/emu10k1/emu10k1.o:
insmod /lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/emu10k1.o:
insmod emu10k1 failed
root[2164] ll /lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/emu10k1.o
-rw-rw-r-- 1 root root 84428 Jun 14 23:27
/lib/modules/2.4.20-6/kernel/drivers/sound/emu10k1/emu10k1.o
>
> (as root), run "dmesg | tail" and check for error messages. I forget
> what the driver reports if everything is OK, I think it's silent (I
> can't check at the moment, sorry). Now run
>
There was no sound messages in /var/log/dmesg or /etc/sysconfig/syslog
> aumix -q
>
9:28AM[2157] aumix -q
aumix: error opening mixer
9:29AM[2158] ll /dev/mixer
crw------- 1 frankk root 14, 0 Jan 30 02:24 /dev/mixer
> which will either report a set of mixer settings or say "/dev/...: no
> such device" (or something like that). If all is well then you just
> need to change your /etc/modules.conf. It should say
>
> alias sound-slot-0 emu10k1
>
> which is what this is trying to tell you:
> >Jun 15 19:25:10 frankk-server1 modprobe: modprobe:
> >Can't locate module sound-slot-0
> >Jun 15 19:25:10 frankk-server1 modprobe: modprobe:
> >Can't locate module sound-service-0-0
>
> jch
