Margarita Manterola wrote: > Hi! > > On 2/5/07, Shobhit Jindal <[EMAIL PROTECTED]> wrote: >> On 2/5/07, Bruno Buys <[EMAIL PROTECTED]> wrote: >> > The only >> > catch ins't debian related: vmware seems to not like my >> > /usr/src/include/linux, and asks for a new linux/version.h. >> >> i have been stuck to kernel 2.6.18-1-686 for the very same reason.... >> and >> not upgrading have searched a bit but to no avail. > > I had this problem as well. And as a pointer, I could get the latest > vmware-player to work, where the old vmware-workstation that I had did > not. >
Do you only "have" the sources or did you actually compile your kernel with the sources that you have on your computer? As far as I recall from prior experiences with compiling stuff like VMWare, you should compile the module with the source of the actual running kernel and not an unused copy of source code. I have compiled the necessary VMWare modules both with the 2.6.18 and 2.6.19 sources without any problems at all. A significant difference between the pre-compiled 2.6.18-1-686 kernel and the source code, is that the source code by default creates version 2.6.18 and NOT 2.6.18-1-686. This version difference could cause the compile problem? regards Jan -- ** Do NOT use the reply-to address. You'll end up in the trash can ** Mail me at: jan A.T schledermann D0T org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
