Thanks for your answer.
I checked dmesg and syslog after running modprobe.
Indeed, in /etc/modules.conf I don`t have sound-slot-1 and sound-service-1-0.
In /proc/modules I don`t have it too.
Instead I have esssolo1 in /proc/modules and alias to in /etc/modules.conf
(sound-slot-0).
What`s next ?
from dmesg: solo1: version v0.20 time 17:27:43 Mar 13 2003 PCI: Found IRQ 5 for device 00:0a.0 solo1: joystick port at 0xe001 solo1: ddma base address: 0xd800 ESS Maestro soundcard not found or device busy
from /var/log/messages:
May 15 13:07:09 arkadi kernel: solo1: version v0.20 time 17:27:43 Mar 13 2003
May 15 13:07:09 arkadi kernel: PCI: Found IRQ 5 for device 00:0a.0
May 15 13:07:09 arkadi kernel: solo1: joystick port at 0xe001
May 15 13:07:10 arkadi modprobe: modprobe: Can't locate module sound-slot-1
May 15 13:07:10 arkadi modprobe: modprobe: Can't locate module sound-service-1-0
May 15 13:07:10 arkadi modprobe: modprobe: Can't locate module sound-slot-1
May 15 13:07:10 arkadi modprobe: modprobe: Can't locate module sound-service-1-0
From: Frans Ketelaars <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Alsa-user] problem with snd-es1968 Date: Sat, 15 May 2004 17:50:20 +0200
On Saturday 15 May 2004 01:55, Arkadi Kagan wrote: > Hello. > > I have a problem to run alsa-driver. > When I try '/sbin/insmod snd-es1968', I get unresolved symbols error. > /proc/ksyms don`t have nothing close to missing entries. > > Any advice is wellcome. > > Thanks. > Arkadi. > > --------------------------------------------------------------------- >------------- My hardware: > snd-ess solo1 1969 > ( I hope it does not go too far from 1968 ) > > My system: > Red-Hat 9. Kernel 2.4.20.8. > > Driver version: > driver "alsa-driver-1.0.4.tar.bz2" > utils "alsa-utils-1.0.4.tar.bz2" > libs "alsa-lib-1.0.4.tar.bz2" > > Installation process I tried: > ./configure --with-cards=es1968 --with-sequencer=yes > ( no errors ) > make > ( no errors ) > su > make install > ( no errors > warning: > --------------------------------------------------------------------- >---------- WARNING!!! The mixer channels for the ALSA driver are muted > by default!!! > ********************************************************************* >***** You would use some ALSA or OSS mixer to set the appropriate > volume. > --------------------------------------------------------------------- >---------- ) > cd ../alsa-lib-1.0.4 > ./configure > make > make install > > cd ../alsa-utils-1.0.4 > ./configure > make > make install > > /sbin/modprob snd-es1968 > ( > error: > --------------------------------------------------------------------- >---------- /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.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-8/kernel/sound/pci/snd-es1968.o: insmod > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o failed > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o: insmod > snd-es1968 failed > --------------------------------------------------------------------- >---------- ) > # insmod failed, therefore, I looked on: > /sbin/insmod snd-es1968 > ( > error: > --------------------------------------------------------------------- >---------- Using /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o: unresolved > symbol snd_dma_alloc_pages_fallback_R18d33983 > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o: unresolved > symbol snd_mpu401_uart_new_R5fb57a92 > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o: unresolved > symbol snd_pcm_suspend_all_R9e381a38 > /lib/modules/2.4.20-8/kernel/sound/pci/snd-es1968.o: unresolved > symbol snd_dma_set_reserved_R77de065d
<snip>
You must use modprobe to ensure other needed modules are loaded first.
The error:
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
means the driver didn't recognize the card. Did you find more information in syslog or the output from dmesg?
HTH,
-Frans
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
