On Fri, 7 Jun 2002 22:24:59 +0100
David Jarvie <[EMAIL PROTECTED]> wrote:

> On Friday 07 Jun 2002 6:12 pm, Brent Cook wrote:
> > On Fri, 7 Jun 2002 [EMAIL PROTECTED] wrote:
> > > On Fri, 7 Jun 2002 12:22:29 +0200, Frans Ketelaars wrote:
> > > >On Fri, 7 Jun 2002 09:48:18 +0100
> > > >
> > > >[EMAIL PROTECTED] wrote:
> > > >> I have built alsa-driver 0.9.0rc1 on kernel 2.4.18, but I get the
> > > >> following error messages when trying to do 'insmod' on the emu10k1
> > > >> module. The
> > >
> > > 'snd'
> > >
> > > >> module shows up in the list produced by 'lsmod'. Any ideas on a cure?
> > > >>
> > > >> insmod /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.o
> > > >> /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.o: unresolved
> > > >
> > > >symbol
> > > >
> > > >> snd_pcm_new
> > > >> /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.o: unresolved
> > > >
> > > >symbol
> > > >
> > > >> snd_hwdep_new
> > > >
> > > ><snip>
> > > >
> > > >Try 'modprobe snd-emu10k1' :) HTH,
> > >
> > > I actually tried insmod only after 'modprobe snd-emu10k1' didn't work.
> > > insmod seems to give more details on what is wrong than modprobe does.
> >
> > Have you tried 'depmod -a' ? This will scan all of the available modules
> > to determine which ones are missing symbols (usually supplied by other
> > modules). It is also used by modprobe to determine which modules need to
> > be installed.
> 
> depmod -a runs without reporting any errors. The errors reported by modprobe 
> are as follows:
> 
> # modprobe snd-emu10k1
> /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.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.18/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod 
> /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.o failed
> /lib/modules/2.4.18/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod snd-emu10k1 
> failed

1. sent your /etc/modules.conf to the list.
2. make sure in the BIOS 'PnP OS installed' or something like that is set 
   to 'no'. 
3. a PCI soundcard right next to the AGP slot may cause problems. there may 
   be an IRQ problem: 'lspci -v' lists PCI cards IRQ's and 
   'cat  /proc/interrupts' lists the IRQ's registered by the loaded drivers 
   AFAIK. Some BIOS's allow you to change IRQ's for PCI slots; if not you will
   have to move the card to a different slot. Btw: PCI cards should be able
   to share IRQ's ......

HTH and good luck :)

    -Frans

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

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

Reply via email to