[ Next-in-Thread ]  [ Next Message ] 

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 ] 

Select this message: Frustrations with kernel versions

Messages Inline: [ 1 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

1. It is a problem in the PCMCIA Configure script by David Hinds, 2000, Feb 21
(_ Configure Script ? by ehlarson, 2000, Feb 27
(_ I'll fix module placement; I disagree on the APM thing by David Hinds, 2000, Feb 28

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.

If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination
NO

If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages
NO

Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

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