Subject: Re: New to this list, Pismo-user (Kernel mismatch? OpenFirmware mismatch?)
From: Charles McLachlan (cim@uk.research.att.com)
Date: Wed May 10 2000 - 02:50:44 MDT
On Tue, 09 May 2000, you wrote:
> Warning: kernel-module version mismatch
> /usr/lib/mol/modules/mol.o was compiled for kernel version 2.2.14pre9
> while this kernel is version 2.2.15pre14
>
> Warning: kernel-module version mismatch
> /usr/lib/mol/modules/sheep_net.o was compiled for kernel version 2.2.14pre9
> while this kernel is version 2.2.15pre14
>
Oh dear. Kernel mismatch. This might be bad but it might just work....
> ************ WARNING, phandle == 0 ***********
> ofmem_map: Conflicting mapping detected --
> -- mapping inserted with reduced size...
> Replacing old translation (EA 009B1000)
> ofmem_map: Conflicting mapping detected --
> -- mapping inserted with reduced size...
> Replacing old translation (EA 009B2000)
> ofmem_map: Conflicting mapping detected --
> -- mapping inserted with reduced size...
> Replacing old translation (EA 009B3000)
> ofmem_map: Conflicting mapping detected --
> -- mapping inserted with reduced size...
> Replacing old translation (EA 009B4000)
> of1275: Address lookup failure
> of1275: Address lookup failure
> **** of_call_method: cmd 'get-key-map' ih: 00100628 (2/2) Args:
> ----> 'getprop': Invalid phandle FFFFFFFF
> ofmem_map: Conflicting mapping detected --
> -- mapping inserted with reduced size...
> Replacing old translation (EA 009B5000)
> Replacing old translation (EA 80816000)
... but it probaly doesn't. I'm not sure these messages *are* due to the module
being a different version from the kernel, but running with a kernel that
matches the module is always a good idea.
You've got a two options here.
1) Change your kernel. Make sure your /boot/System.map matches your new kernel,
make sure you have a copy of your kernel in /boot (apparently this is a
requirement for some things, I must admit I've never seemed to need it), make
sure that it is some varient of 2.2.14
2) Change your mol. Make sure your kernel headers (in
/usr/src/linux/include/linux and symbolically linked from /usr/include) match
your running kernel. cd to your mol source directory and make. Note: I've only
ever got this to work using 2.2.14pre9 (not any of the 2.2.15 kernels) using
the kernel header rpm from linuxppc.org, so you might be better with option 1.
Another possibility (what with all those symbols starting with "of") is that
this is Open Firmware confusion. I vaguely remember hearing about some cunning
methods of copying your real OF tree into your /lib/mol/oftrees directory, but
I've never needed to do so, so can't really help here.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Charlie McLachlan AT&T Research Lab. Cambridge. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This archive was generated by hypermail 2a24 : Wed May 10 2000 - 03:13:32 MDT