compile problems with 2.4.18
 

hello,
i recently decided to upgrade my slack8 system to slack8.1. it's a laptop, p3 700, yada yada. everything worked perfectly with slack8 running 2.4.17.

i guess my mistake was just deciding to format my partitions (wanted to go with ext3). but now whenever i try to compile the kernel for a few options i need (apm support, sound and video, etc) i get depmod errors in the make modules_install phase of compilation. here is the exact reading:

cd /lib/modules/2.4.18; \
mkdir -p pcmcia; \
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
make: *** [_modinst_post] Error 1
root@nellie:/usr/src/linux#

i don't have pcmcia compiled into the kernel, as i'd rather install the pcmcia-cs package myself. when i do include pcmcia, i get a whole slew (upwards of 30) depmod errors.

i even tried going back to 2.4.17, but after a successful compile the machine still boots into 2.4.18. (perhaps slack8.1 needs a kernel of 2.4.18+, i dunno) anyway, this is a very frustrating problem as i'm unable to install my wireless nic cause it returns depmod errors in the compilation of the pcmcia-cs and linux-wlan package.

does anyone have any suggestions? i've recompiled this kernel like 10 times and simply can't figure out what's going on. absolutely any help is appreciated! :-)

ok, little bit of an update.

i did some googling (i love when you can make websites into verbs :D ) and found that those depmod errors appear to be related to token ring adapters. so i compiled in support for the token ring devices (despite the fact that i didn't want it) and i wasn't receiving any depmod errors on recompile. however, when i run depmod after the fact, i get one error:

root@nellie:/usr/src/linux# depmod
depmod: *** Unresolved symbols in /lib/modules/2.4.18/pcmcia/parport_cs.o.gz
root@nellie:/usr/src/linux#

again, i don't have pcmcia enabled, but i do have parallel port support enabled.

thanx. :-)

Do you have the new modutils? Did you just install a bunch of 8.1 packages, or back up stuff, clean 8.1 install, and restore. The latter is preferred as it pretty much takes care of all the dependencies.

I don't think you need "support for PCMCIA mangement for PC-style port" for your laptop. Unless you have a parallel port that is managed by your pcmcia bus, which I assume it is not the case. You may want to say no to this kernel option (Parallel port support -> Support for PCMCIA management for PC-style ports).

WRT the token rings, since you say you don't have any, you may want to say no to:
Network device support -> Token Ring devices -> Token Ring driver support

AND

Network device support -> PCMCIA network device support -> IBM PCMCIA token ring adapter support

I am pretty sure that will solve your token ring's unwanted presence. . .

then save, and: make clean, make dep, make . . . etc

BTW, as of Slackware 8.1, the kernel boots from the /boot partition, and not "/". I thought I would mention this, since it sounds like you have booting issues (i.e. booting into 2.4.18, when you just compiled 2.4.17) If you want to start your 8.1 with kernel 2.4.17, you have to edit lilo.conf to make changes, or add the 2.4.17 kernel location to it.

Maybe your previous problems are also due to the fact that your may still be loading the original 2.4.18 kernel you had under /boot, where your newly compiled kernel was probably installed under "/".

Just a thought.

GL

Re: compile problems with 2.4.18
 

Before make modules_install rename /lib/modules/2.4.18 directory to something else. I saw this problem twice and renaming directory hopefully should help.

As an option:

I used to be a big proponent of pcmcia-cs, but I've largely made the switch to in-kernel and yenta socket.

If you recompile 2.4.18 with in-kernel pcmcia on, all of the 3 locations for pcmcia modules (in make menuconfig), stick the hermes.conf patch file in /etc/pcmcia, and edit rc.pcmcia so it doesn't try and load pcmcia_core, then cardmgr should try and load the orinco_cs module to drive your prism2 card. I haven't tried to back-hack a pcmcia-cs system to work with in-kernel yenta_socket, but it shouldn't be that hard... I don't think. Regardless, whichever you do go with, the orinoco_cs module will drive that card and uses the wireless_tools API, which beats all of that wlan-ctl goop. Also, the wireless_tools package is included (finally) in Slackware 8.1 somewhere.

Cheers,

Finegan

pcmcia fsck-up in 8.1
 

First of all, you're not alone in having this problem..

I've got the same error when I tried to compile a new kernel
on my stationary computer.. And I'm *certain* it doesn't have
anything attached to it that even reminds of a pcmcia-device :P

So after googling around, without any greater success, I finally
decided to fix it myself....

Solution: Edit the /usr/src/linux-2.4.18/Makefile

These are the lines I've changed:
# Original
.PHONY: _modinst_post
_modinst_post: _modinst_post_pcmcia

# Slackified
.PHONY: _modinst_post
_modinst_post:

And that's it!
My new compiled kernel is up and running ;-))

Please let me know if it worked out ok.. else I'm pretty sure I'll here from you anyway ;P

_ALL_ feedback is appreciated!

pac-man

i also had a problem with the pcmcia thing and also with a directory /net in /lib/modules/kernel/2.4.18. both caused problems with the compiling of the nvidia driver. i just removed both the pmcia and th net directorie and now it works. but it seems like the makefile is broken. i will also trie changing the makefile. maybe i also fid a section for the /net thing.

bass