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 on an other, try to remove soundcore or ac97_codec first.
an other cause could be that a daemon helds the sounddevice open. if you
are running on kde it could be artsd or esd. look for artsd or esd as
running process (ps ax | grep artsd). kill them ;)!

an other (last possible) solution would be to delete or remove es1371.o
from /lib/modules/kernelvers/..., you dont need it anyway, and reboot.

>
> And once I do get modprobe to work.  How do I set it so that it comes
> up like that at every boot?

edit your modules.conf as: (from INSTALL)

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ens1371
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

read INSTALL in alsa-driver...

once you have edited your modules.conf the driver will loaded when a
soundapp starts.

____
joy


> Many thanks,
> Oliver
>
>
> On Sat, 30 Mar 2002 14:26:44 +0100 (CET), joy ping <[EMAIL PROTECTED]>
> wrote:
>
> >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 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.
> >>
> >> Except:
> >> [root@friday pci]# /sbin/modprobe snd-ens1371
> >> /lib/modules/2.4.7-10/kernel/sound/pci/snd-ens1371.o: init_module: No
> >> such device
> >> Hint: insmod errors can be caused by incorrect module parameters,
> >> including invalid IO or IRQ parameters
> >> /lib/modules/2.4.7-10/kernel/sound/pci/snd-ens1371.o: insmod
> >> /lib/modules/2.4.7-10/kernel/sound/pci/snd-ens1371.o failed
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_info_unregister_Refee605b
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_iprintf_R163a1266
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_free_one_R4ae59c76
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_device_new_R9e1b7a93
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_control_register_ioctl_R6a91ac50
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_control_unregister_ioctl_Rcea22ad6
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_info_create_entry_Rf1748106
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_info_register_Reabdbd1a
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_register_device_R35abc812
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_unregister_device_R1036b0ad
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_prepare_R00f44f66
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_remove_R55385873
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_add_Reb4d579d
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> __pollwait_R047dd2bd
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_info_free_entry_R36b1ac00
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_control_notify_switch_change_R5a4aa71a
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_new_R74166f9a
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_free_Rb0cb7821
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: unresolved symbol
> >> snd_switch_count_R9ad6deb6
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: insmod
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o failed
> >> /lib/modules/2.4.7-10/misc/snd-mixer.o: insmod snd-ens1371 failed
> >> [root@friday pci]# lsmod
> >> bash: lsmod: command not found
> >> [root@friday pci]# /sbin/lsmod
> >> Module                  Size  Used by
> >> ide-cd                 26592   0  (autoclean)
> >> cdrom                  29504   0  (autoclean) [ide-cd]
> >> es1371                 27616   1  (autoclean)
> >> ac97_codec              8864   0  (autoclean) [es1371]
> >> gameport                1840   0  (autoclean) [es1371]
> >> soundcore               4208   4  (autoclean) [es1371]
> >> r128                   90304   2
> >> agpgart                26272   3
> >> eepro100               17120   1
> >> usb-uhci               20640   0  (unused)
> >> usbcore                49792   1  [usb-uhci]
> >>
> >> (jackd -d alsa won't start with this driver installed either.)
> >>
> >> Any clues as to where I'm going wrong here?


_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to