Thanks for the response. I went through the sound howto and also alsa-sound-mini how to. alsa needs kernel source. I don't have src for 2.2.13 which comes with suse6.3 as i got suse6.3 from a mag CD. However now sound works in suse 6.3 but midi doesnot work. My corrected modules.conf is below. alias char-major-14 opl3sa2 post-install opl3sa2 modprobe "-k" alias midi opl3 post-install opl3 modprobe "-k" options opl3 io=0x388 irq=9 options opl3sa2 io=0x220 mss_io=0x530 irq=5 dma=0 dma2=1 mpu_io=0x388 now it works for for me. Still problem is not solved for midi. when i start kmid, I get msg saying 'can't locate module synth0' When I start playing any midi file, i get msg saying 'mpu 401: device not initialized properly. sequencer error: unable to open midi0' Any suggestion welcome' Tim Duggan wrote:
-----Original Message----- From: L.V.Gandhi [SMTP:lvgandhi@md3.vsnl.net.in] Sent: Saturday, April 29, 2000 11:46 AM
Tim Duggan wrote:
To sync them up do # depmod -a
yes that got rid of the msg. But now I get msgs like this when i run it. unresolved symbols in /lib/modules/2.2.13/block/ide-probe-mod.o unresolved symbols in /lib/modules/2.2.13/pcmcia/mpsuni-cs.o
My understanding is that these are extra modules. When you run depmod it checks the kernel and the modules and reports anything that doesn't match. They were probably either put into the kernel or not compiled at the same time as the current kernel. I don't think it will do any harm but those modules may not load if there is a dependant module missing (pcmcia modules sometimes need two or three others to be loaded beforehand).
That should get rid of the message at boot, then double check that the right modules for the card exist.
isapnp is working and is getting configured during boot. This can be seen during boot. Modules.conf file sound off msgs are commented >out. Still sound is not working. I get msgs 'could not locate module sound-slot-0 'couldnot locate module sound-service-0-3' in console log. This happens if I comment all sound concerned lines or i put lines as in conf.modules of RH6.1. In RH61. sound works withese lines. alias sound opl3sa2 pre-install sound /sbin/insmod sound dmabuf=1 alias midi opl3 options opl3 io=0x388 options opl3sa2 mss_io=0x530 irq=5 dma=0 dma2=1 mpu_io=0x388 >io=0x370
What to further to look for.
I don't have much experience with isapnp or sound but I'll try. Sound in linux is fairly confusing right now since there are at least three different ways to get it working. Check the RH configuration to see which method is being used. Current choices (that I know of) are 1) Kernel sources, can be either compiled into the kernel or as modules. 2) OSS, kernel modules (commercial but some are free, advanced drivers cost a couple of dollars) 3) ALSA, kernel modules that are aiming to be the next generation of sound drivers for linux (free, hardware support is quite good and getting better) My first guess is that the two distros might be using different methods and thereby have different sound modules. See if you can find out which are installed under each distro (I think you can do this with YaST (on SuSE) or kpackage (either distro)).
You can also dig through /proc to see if something is getting initialized in the wrong order and using your sound cards irq's and i/o space by mistake. On both distros you can use cat to display most of the info in /proc/<filename>
About the only other thing I can recommend is the Sound Howto (it's on the CD's).
Good luck, Tim
-- L.V.Gandhi MECON, 5th Floor, RTC Complex, Visakhapatnam AP 530020 INDIA http://www.poboxes.com/lvgandhi lvgandhi@poboxes.com, lvgandhi@vsnl.com, 31882656@pager.mirabilis.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/