All,
I've run into the exact same problem myself, however I've not come up with
a resolution. I, too, am running -22mdk. Rebuilding the kernel and
modules thus far hasn't worked. I've pondered possibly deleting my
present set of modules, then rebuilding them to see what happens as a depmod
produces output that indicates I still have some modules left that weren't
compiled with the last build but were from a previous build and left out
when I did the last make xconfig. Could that be what vmware is pissin'
and moanin' about?
Rich
On Thu, 9 Dec 1999, David van Balen wrote:
>
> I already posted this, but I guess I'll repeat it in case you missed it...
> it may help you figure out what's wrong.
> I upgraded from 7mdk to 22mdk with the update util. Didn't to any extra
> compilation, only updated and reinstalled lilo.
> After rebooting, everything appeared to go fine until I tried to run
> VmWare. VmWare complained that it wasn't configured to run on the current
> kernel and that I should reconfig (which sounded logical to me). However,
> when it tried to recompile its modules based on the kernel headers in
> /usr/src/linux/include, it barfed and complained that there was a "slight
> difference of configuration" between the headers and the actual compiled
> kernel.
> I figure that since you tried to do some extra compiling after you
> installed the kernel, you may have run into the same problem. I figure
> I'll have to recompile from scratch so that my kernel matches my
> headers... if you can figure out some other way, please let me know.
>
> DvB
>
>
