0.9.70 loading kmods failes on ydl3

[Samuel Rydh]

On Mon, Mar 01, 2004 at 11:19:59AM +0100, Eddie Bindt wrote:
> Hi,
> 
> I tried to work around the problem in my previous mail where the februari 
> security update screwed my 10.2.8 in mol ...

Yes, this problem has been fixed in later MOL versions
(it was triggered when enough Mac OS X side KEXTs was
put into the System/Library/Extension directory).

> I pulled BK and rebuilded rpms for my system
> 
> kernel-2.4.22-2g
> mol-0.9.70-1
> mol-kmods-0.9.70-1
> 
> loading modules failes 
> 
>  startmol
> Mac-on-Linux 0.9.70-rc2-vnd-vnd [Mar 1 2004 10:31]
> Copyright (C) 1997-2004 Samuel Rydh
> Starting MOL session 0
> Loading Mac-on-Linux kernel module:
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol force_sig
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol __up
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol find_vma
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol __down
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol 
> misc_register
> /usr/lib/mol/0.9.70/modules/2.4.22-2g/mol.o: unresolved symbol mem_map
> ====================================================================
>   Failed to load the module - try recompiling the MOL kernel

The problem is the kernel source/headers used while compiling
mol-kmods. The above error typically occurs when the kernel headers
used during the compilation has been configured with for
instance CONFIG_SMP off while your running kernel has CONFIG_SMP on
(or vice versa).

MOL looks for the kernel source in /lib/modules/`uname -r`/build.
The main problem is that vendors tend to ship a single kernel 
tree but multiple kernels. The source tree configuration will in general
not match the kernel. By doing distribution specific stuff it may
or may not be possible to recover working kernel headers.

My personally opinion is that /lib/modules/`uname -r` should always
point to working kernel headers and the distro is broken if this
is not the case...

The easiest way to resolve this problem is probably to compile
your own kernel.

/Samuel