Thanks for the info Mike, I went to the VMware site to check it out -
here is what it said:
Software requirements
1.VMware host operating system requirements
glibc2 to glibc6 (glibc1 does not work)
Linux kernel 2.0.32 to 36
Linux kernel 2.2.0 and higher for SMP systems
VMware will not run on systems that do not meet these
requirements.
Does this mean that I need to find a copy of kernel version 2.0.32 to
36, or should it work with 2.2.9-19mdk? If I only need to go back to
2.2.9-19mdk, is it easier to do an "upgrade" install to go back to this
kernel version, or won't this work and will I be stuck with doing an
install from scratch? I don't think I made a backup of the old kernel -
if I did, I don't know where I put it. Is there any way to find out?
BTW, what does the -19mdk mean?
Thanks,
Chris.
Mike Fieschko wrote:
> >>> "Chris" == Chris Smallhorne <[EMAIL PROTECTED]> writes:
>
> [snip]
>
> Chris> The directory of kernel headers (version 2.2.9-19mdk) does
> Chris> not match your running kernel (version
> Chris> 2.2.9-27mdk). Consequently, even if the compilation of the
> Chris> module was successful, the module would not load into the
> Chris> running kernel."
>
> [snip]
>
> Chris> messages during boot-up). Can someone tell me (in simple
> Chris> terms) how I might be able to fix this error? If you
>
> [snip]
>
> Upgrade kernel-headers to 2.2.9-27mdk.
>
> But, you might want to check the VMware pages, since I believe vmware
> doesn't work with 2.2.9-27. It does work with other kernel versions.
>
> --
> Mike Fieschko, West Orange, NJ, USA
> X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el
> X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html
> Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED]
> http://www.viconet.com/fieschko/home.htm
> Sep 21 St Matthew
> "Truth is sacred; and if you tell the truth too often nobody will
> believe it." - [G.K. Chesterton, in ILN, 2/24/06]
