On Sat, 30 Mar 2002, Oliver Sampson wrote:
> Hi,
> Thanks for the reply.
>
> I've closed all of my audio apps, but when I do the modprobe -r
> es1371, I get device or resource busy. Is there a way to force it?
hm..., its better to remove the modules in a clean way. somtimes one
module depends
Hi,
Thanks for the reply.
I've closed all of my audio apps, but when I do the modprobe -r
es1371, I get device or resource busy. Is there a way to force it?
And once I do get modprobe to work. How do I set it so that it comes
up like that at every boot?
Many thanks,
Oliver
On Sat, 30 Mar 20
1. set up the path for your executables properly.
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export
PATH
2. kill your OSS sound-modules with: modprobe -r es1371
3. try 'modprobe snd-ens1371' again.
joy
On Fri, 29 Mar 2002, Oliver Sampson wrote:
> So,
> I think the
On Fri, 29 Mar 2002 21:57:20 +0100
Oliver Sampson <[EMAIL PROTECTED]> wrote:
> So,
> I think the culprit here is the ALSA how-to. It says that for the
> ES1371 chipset to use the snd-card-audiopci driver. But the
> (seemingly) more up-to-date soundcard matrix says to use the ens1371
> driver,
So,
I think the culprit here is the ALSA how-to. It says that for the
ES1371 chipset to use the snd-card-audiopci driver. But the
(seemingly) more up-to-date soundcard matrix says to use the ens1371
driver, which *is* in the alsa-drivers directory. Okay, I think I'm
getting up to speed now.
E
