Sad: Frustrations with kernel versions 

Forum: PCMCIA Installation and Configuration Issues
Date: 2000, Feb 21
From: ehlarson

Well, after spending about 6 hours working through include files and reinstalls of system components to determine that my previous compile problems were due to a glibc upgrade via autorpm (I don't know yet if it is a compatability issue with PCMCIA and the new GLIBC or if it was a install failure), I was able to get PCMCIA to compile. HOWEVER I have found that I am not out of the woods by a long shot. I am installing PCMCIA on a Redhat 6.1 smp machine in order to test/use a wireless network card (via an IDE card with a Ricoh controller - according to the HOWTO this SHOULD work). The kernel version I am running is the stock RedHat 2.2.12-20smp supplied with their distro. However, whatever I do - including using ./Configure --current I get complaints that my source tree is 2.2.12-20 whilst the kernel I am running is 2.2.12-20smp. Now color me idiot or something, but AFAIK there is no such thing as a 2.2.12-20smp source tree. In my experience smp kernels are generated via compilation with a particular make option set during the configuration process. After setting this bit and performing the compilation I end up with 'symbols not found' during the install and errors like: Starting PCMCIA services: modules/lib/modules/2.2.12-20smp/pcmcia/pcmcia_core.o: kernel-module version mismatch /lib/modules/2.2.12-20smp/pcmcia/pcmcia_core.o was compiled for kernel version 2.2.12-20 while this kernel is version 2.2.12-20smp. /lib/modules/2.2.12-20smp/pcmcia/i82365.o: kernel-module version mismatch /lib/modules/2.2.12-20smp/pcmcia/i82365.o was compiled for kernel version 2.2.12-20 while this kernel is version 2.2.12-20smp. /lib/modules/2.2.12-20smp/pcmcia/ds.o: kernel-module version mismatch /lib/modules/2.2.12-20smp/pcmcia/ds.o was compiled for kernel version 2.2.12-20 while this kernel is version 2.2.12-20smp. cardmgr. Now I read the statement about CONFIG_MODVERSIONS in the HOWTO - the question is, is this a problem with the version checking mechanism, and my installation is actually ok, or is there some other problem that I need to take care of to get a working PCMCIA...?? In the meantime the version that I compiled or my single CPU laptop seems to be at least recognizing the card, and enabling eth0, so I am at least part way there.

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

It is a problem in the PCMCIA Configure script Re: Sad: Frustrations with kernel versions Date: 2000, Feb 21 From: David Hinds <dhinds@pcmcia.sourceforge.org>

The Configure script for PCMCIA is getting confused by the difference in the kernel version names (2.2.12-20 vs 2.2.12-20smp), and I didn't catch this before because I guess few people have tried building PCMCIA on a new Red Hat SMP kernel with the "smp" embedded in the version information. Try the 21-Feb-00 beta on sourceforge.org in /pcmcia/NEW and see if that works better. -- Dave

Configure Script ? Re: It is a problem in the PCMCIA Configure script (David Hinds) Date: 2000, Feb 27 From: ehlarson

Hi - I tried the beta with the configure script changes, and found that it has the problem of placing the resulting modules in the wrong directory. After some further experimentation it seems to me that the best way to deal with it is to edit the kernel makefile version string. This way everybody agrees on exactly what is going on. Also - I found that when compiling for SMP the resulting PCMIA modules are looking for APM functions - this can be fixed by also turning off APM in the kernel makefile, but methinks that PCMCIA should not be looking for them as APM is not going to be around when SMP is active. Thanks.

I'll fix module placement; I disagree on the APM thing Re: Configure Script ? Date: 2000, Feb 28 From: David Hinds <dhinds@pcmcia.sourceforge.org>

I can also fix the problem with module placement, easily enough. I didn't notice that when I made the other changes. Editing the kernel Makefile isn't really an acceptable work-around; I've tried pretty hard to make it so that you can avoid having to touch anything in the kernel source tree, to build PCMCIA. For APM, all that PCMCIA does is to see how your kernel is configured. I think it would be wrong for PCMCIA to ignore APM on an SMP kernel. You've got an APM kernel config option: that is the only sensible thing for PCMCIA to check. Some people might want to build a kernel with SMP and APM, so that they can run the same kernel on their laptops and their desktop SMP boxes. -- Dave

[ Add Message ]  to: "Frustrations with kernel versions"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]