[NBLUG/talk] pcmcia: CardServices release does not match!

[ME]

Dave Sisley said:
> Thanks for the reply, ME.
>
> I think I understand you, so I will refine my question(s) a bit:
>
> I have a fresh install of SuSE 8.2, no updates. I went back and add
> the kernel-source and pcmcia source from the install cd's.  I would
> think therefore that kernel and card services should be in sync,
> right?
>
> Then I installed the Atmel wireless network card driver, which
> includes a few modules, depending on the model card you are using.  My
> card apparantly requires me to load the pcmf502rd module.  When I try
> to load it via insmod, I get an error that tells me to look in dmesg
> and the syslog.  It is there that I see the 'CardServices release does
> not match!' message.
>
> Is this because of some conflict between the kernel version and
> pcmcia_cs? or between the pcmf502rd module and pcmcia_cs?

This sounds like a problem with the module/driver(s) provided by the
vendor. (The ones installed after SuSE was running.)

Your kernel and pcmcia-cs are likely just fine with each other as they
were part of a package installed from your CD (as you said.)
> More to the point, how do I fix it?

See if the vendor has a module  for your system or maybe source code.
Maybe theybuilt their module in such a way that it wold work with a RedHat
system kernel, but nothing else. If this is the case, I would hope they
would include the source for their module to permit you to build a module
for system.

I would expect SuSE to install a SUPPORTED.CARDS file with the pcmcia-cs.
Check this file to see if your card was supported. (Sometimes, there is no
need to install the drivers/modules provided by a vendor with their
hardware.) If this is the case, it is possible that there were modules for
your card that came with SuSE's pcmcia-cs and the installation of the
vendors drivers overwrote the modules that came with pcmcia-cs. As far as
how to fix this, I am not sure how SuSE might encourage a user to do it,
but I would expect that you should be able to uninstall the pcmcia-cs
package and then re-install it -- though I would expect that SuSE would
have a procedure to have a packe just force-reinstall all files
overwritting existing files.

Another thing that is worth a try, but is very unlikely to fix anything is:
* stop yoru pcmcia-cs daemon/service
* as root tyep:  depmod -a
* restart your pcmcia-cs services

> How do I find out where the
> conflict is?

The conflict is almost certainly with the file that was added after the
SuSE install  from the new hardware vendor.

> I resisted the urge to just download the latest version
> of pcmcia_cs, but maybe that's what I need to do.

Building pcmcia-cs by hand is some work, and if you can make this work
without going that route, I think you will find  it much easier.

Another thing to try is to visit the website of the new hardware vendor to
see if they have a newer release of driver/module installer. (I would try
this after checking to see if pcmcia-cs supports your card without the
drivers from the vendor.)


>
> -dave.
>
>
> On Sun, Nov 30, 2003 at 12:04:53PM -0800, ME wrote:
>> There are several parts to pcmcia_cs, and they should match:
>> 1) The version of pcmcia_cs is compiled against a specific kernel. Do
>> not
>> mix/match compiled pcmcia_cs with different kernels.
>> This means, you either go with packaged versions of your kernel and
>> pcmcia-cs in such a way that the packages were built to work with each
>> other or you find some other way to build thepcmcia-cs  from source and
>> have it "Read from the presently running kernel" that was a packaged
>> kernel or get a copy of the source-built kernel in the package or build
>> your own kernel from source.
>>
>> 2) If you have a packaged pcmcia-cs, and then you decide to download,
>> build and install a pcmcia-cs package from source, then the modules used
>> by the pcmcia-cs as installed into the kernel module dirs, then the
>> system
>> may not start the cardmgr that you build but instead start the packaged
>> one and the packaged cardmgr may find the modules you built do not matc
>> h
>> the version of cardmgr that is running (the daemon)
>>
>> There are other items to consider, but the two above are common for
>> version problems.
>>
>>
>> There should be sub-versions to the kernel and pcmcia-cs if used as
>> packaged, and I would expect the sub-versions to match.
>> Dave Sisley said:
>> > Forgive me, luggers, but I need some help with my...
>> >
>> > [cue scary shower-scene-from-psycho music]
>> >
>> > ...Belkin wireless network card! <scream!>
>> >
>> > Actually, I am hoping that this is a simple question (as if!).
>> >
>> > I have most of the configuration in place, and the card is now
>> > recognized.  The problem comes when the module is loaded.
>> >
>> > The module is called pcmf502rd, and when it supposed to load, the
>> > following error message (amongst others) appears in my log:
>> >
>> > ...kernel: pcmf502rd: CardServices release does not match!
>> >
>> > I am running a fresh install of SuSE 8.2, and I believe I am running
>> > card services version 3.2.3 (part of the trouble is that I am unsure
>> > what 'card services' is - my best guess is that it is the pcmcia_core
>> > module?).
>> >
>> > I built the most recent version of the Atmel driver, but I don't know
>> > which version of cardservices it would like to find.
>> >
>> > I've been googling a bunch, but I'm not sure now what to even look
>> > for.
>> >
>> > Thanks in advance for any help.
>> >
>> > -dave.
>> > _______________________________________________
>> > talk mailing list
>> > talk at nblug.org
>> > http://nblug.org/mailman/listinfo/talk
>> >
>> >
>>
>> _______________________________________________
>> talk mailing list
>> talk at nblug.org
>> http://nblug.org/mailman/listinfo/talk
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/mailman/listinfo/talk
>
>