At Sat, 27 Jul 2002 00:46:40 +0200, Ralph Paladur wrote: > > On Fri, Jul 26, 2002 at 03:37:18PM +0200, Takashi Iwai wrote: > > At Wed, 24 Jul 2002 16:15:05 +0200, > > Ralph Paladur wrote: > > > > > > hello! > > > > > > well, i need alsa9 in order to run xine .9.12; so i fetched the rpm's (alsa, > > > alsa-devel, alsa-driver) from ftp://ftp.suse.com/pub/people/tiwai/7.2-i386/ and > > > installed them as outlined in the readme of the site. > > > > > > specifically, here's what i did: > > > > > > rpm -Uvh alsa.rpm --force > > > rpm -Uvh alsa-driver.rpm --force > > > > > > > > > > > > now typing 'rcalsasound start' gives me > > > > > > Starting sound driver: snd-ens1371 /lib/modules/2.4.4-4GB/misc/snd-mixer.o: > > > unresolved symbol snd_register_device > > > /lib/modules/2.4.4-4GB/misc/snd-mixer.o: unresolved symbol snd_kcalloc > > > > you still have old ALSA 0.5.x modules. > > please remove all snd*.o files under /lib/modules/2.4.4-4GB/misc, > > and rerun depmod -ae. > > > thanks for the hint. this might have worked with the config that i had when i > posted the problem. > problem now is that in the meantime, i have deleted the whole /lib/modules for > 2.4.4-4GB, and recompiled kernel and modules, and installed them. > > the strange thing is that now i do not have the /modules/2..../misc folder any > more.
perhaps makefile of kernel removed the module objects. > the menuconfig says that es1371 is compiled modular. this is an OSS driver, not an ALSA! > i once reinstalled alsa5, and it would recognize the card, but rcalsasound would > fail. yep, it must, since it not there :) > ok, so now i again installed the kernel/modules, then the abovementioned rpm's, did >what you said, and > now alsaconf 9 complains that it cannot find a > soundcard. (i have soundblaster pci128, which worked fine under alsa5). > > doing 'insmod es1371' gives me: > Using /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > gameport_register_port > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > ac97_probe_codec > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > unregister_sound_dsp > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > unregister_sound_midi > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > register_sound_dsp > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > register_sound_mixer > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > unregister_sound_mixer > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > register_sound_midi > /lib/modules/2.4.4-4GB/kernel/drivers/sound/es1371.o: unresolved symbol > gameport_unregister_port this is another problem. i guess you didn't enable gameport support on kernel. OSS es1371 module requires gameport support. > Starting sound driver: ens1371modprobe: Can't locate module snd-ens1371 > > somehow, alsa9 still tries to open the old driver? what do i need to get > alsaconf recognize my soundcard? no, your modules are likely gone. that's the reason. at that time, the alsa driver was not integrated into kernel. it was provided as an extra package for modules. the easiest way would be to get alsa-drivers tarball and install it manually. you need to run only cvscompile script there to compile, and run "make install" to install modules. ciao, Takashi ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
