I got past this (stuck elsewhere but that's another issue). For anyone else who has this issue:
VMware forum: http://kb.vmware.com/vmtnkb/search.do?cmd=displayKC&docType=kc&externalId=VMTN-F219-T41713-M434746&sliceId=M434746&dialogID=9449162&stateId=0%200%209441841&doctag=Forum%20Posts I changed references to linux/version.h "A somewhat cleaner solution is to edit vmware-config-tools.pl - go to check_answer_headerdir() line 1293 (in my version), change references to linux/version.h to linux/utsrelease.h " Thanks. On Friday 02 February 2007 08:25, Joe Morris (NTM) wrote: > [EMAIL PROTECTED] wrote: > > Thanks. I'll check it out. By not installed properly can you expand on > > that. The kernel is in /boot - in fact it's my default kernel I boot to. > > Did you name the kernel for instance vmlinuz-(name of the modules > directory under /lib/modules) and is your initrd also named > initrd-(modules directory name)? Did you copy the System.map there > named System.map-(modules directory name)? It seems that these names > must match the modules directory. When you run make modules_install, it > looks for those files in /boot. It also creates a link to the source > directory. You can boot a kernel and it seems able to find it's modules > even if the names don't match, but it causes a symbol lookup failure and > causes some things to break. HTH. -- Brett I. Holcomb -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
