I'm trying to get my sound working on slackware, but when I do make modules_install, it errors during some pcmcia stuff, I tryed to just disable all pcmcia options in my kernel since I don't need them, but the xconfig won't let me touch any of them. is there anyway I can disable them all?

Unresolved symbols in /lib/modules/2.4.18/pcmcia/parport_cs.o.gz
parport_cs.o.gz seems to be the problem, I didn't make mrproper and took out all pcmcia support, but this still pops up....anyone know where this is in the kernel config?

I think you need to delete the module /lib/modules/2.4.18/pcmcia/parport_cs.o.gz. If all the references are removed from the running kernel, but something is attempting to load the module or build the dependency file (like depmod -a in rc.modules) then the prior existing module will result in unresolved symbols. The make modules_install could be attempting to run depmod as well causing the error.

find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.18; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.18/pcmcia/ibmtr_cs.o.gz
depmod: init_trdev
depmod: tr_type_trans
depmod: register_trdev
depmod: unregister_trdev
depmod: *** Unresolved symbols in /lib/modules/2.4.18/pcmcia/parport_cs.o.gz
depmod: parport_proc_unregister
depmod: parport_pc_probe_port
depmod: parport_unregister_port
make: *** [_modinst_post] Error 1

theres exactly what its saying, so should I just del the .gz?

I would. You could check the date/time stamps on the files first if you like. I do not believe they will match your kernel build time for the System.map that is in reference. The files would be remants from the last build. Personally, I am surprised you are even seeing this problem. I would of thought the process would of deleted them.

Is your system date set correctly? I have seen wierd happenings on systems where a kernel is built at one time, and then the clock is changed back in time prior to the kernel build, then a rebuild is attempted. All the files from the prior build will appear newer than the current build. That will mess up most any make system.

When I migrate from a stock kernel after an install to a custom kernel, I trash the entire tree from the kernel version down. Unless I desire to keep it for a legacy reference, in that case I rename it. The modules_install will create the tree if needed for modules when a module enabled kernel is built and then install just the modules that were built.

I finally got it workin, I did make mrproper and installed a brand new kernel from the cd, edited it, and all went smooth...I donno why it was buggin like that. Ahh well, fixed now, thx for the help.