Problem with kernel upgrade and VMware
in [Slackware]
|
Prev: Kernel.org
Next: Alt.OS.Linux.Slackware FAQ pointer
From: tomek on 2 Apr 2010 07:00 Hi, after kernel upgrade to 2.6.33 version i can not run VMware Player. I see this errors modinfo: could not find module vmmon modinfo: could not find module vmnet modinfo: could not find module vmblock modinfo: could not find module vmci modinfo: could not find module vsock VMware Players shows window where i should place path to kernel source. I place there path to directory where i unpacked kernel, it is /usr/src/linux-2.6.33. But after confirmation i see message "C header files matching your running kernel were not found. Refer to your distribution's documentation for installation instructions" What is wrong.
From: Kamil P. on 2 Apr 2010 13:54 On 04/02/2010 12:00 PM, tomek wrote: > Hi, after kernel upgrade to 2.6.33 version i can not run VMware > Player. > I see this errors > modinfo: could not find module vmmon > modinfo: could not find module vmnet > modinfo: could not find module vmblock > modinfo: could not find module vmci > modinfo: could not find module vsock > > VMware Players shows window where i should place path to kernel > source. I place there path to directory where i unpacked kernel, it > is /usr/src/linux-2.6.33. > But after confirmation i see message > "C header files matching your running kernel were not found. > Refer to your distribution's documentation for installation > instructions" > What is wrong. Hi You have to reinstall VWware. It compiles modules depends on your kernel version. Kamil
From: Jim Diamond on 2 Apr 2010 16:38 On 2010-04-02 at 08:00 ADT, tomek <tmkdudek(a)gmail.com> wrote: > Hi, after kernel upgrade to 2.6.33 version i can not run VMware > Player. > I see this errors > modinfo: could not find module vmmon > modinfo: could not find module vmnet > modinfo: could not find module vmblock > modinfo: could not find module vmci > modinfo: could not find module vsock > > VMware Players shows window where i should place path to kernel > source. I place there path to directory where i unpacked kernel, it > is /usr/src/linux-2.6.33. > But after confirmation i see message > "C header files matching your running kernel were not found. > Refer to your distribution's documentation for installation > instructions" > What is wrong. One of the reasons I got tired of vmware and switched to vbox is that virtually every kernel upgrade required me to hunt down the latest version of the vmware-any-any patches and see if they fix the problems with that kernel. Vbox "just works". I don't know if that is the problem here, but you might want to start there. Do a search for vmware 2.6.33 C header files matching your running kernel were not found and maybe you will find the answer. Cheers. Jim
From: tomek on 2 Apr 2010 17:15 At /var/log/packages/ i see kernel-headers file which contains paths to kernel headers files. But this file is for older kernel. Where kernel headers are placed?
From: Grant on 2 Apr 2010 17:34
On Fri, 2 Apr 2010 14:15:27 -0700 (PDT), tomek <tmkdudek(a)gmail.com> wrote: >At /var/log/packages/ i see kernel-headers file which contains paths >to kernel headers files. But this file is for older kernel. Where >kernel headers are placed? I don't think you're on the right track here. Recent linux kernels include the source for the vmware interface module, perhaps you only need to do a make *config and turn that on? As far as headers go, 'make help' has some info. But I don't think you want this. AFAIK the installed kernel-headers file is there to match the installed version of glibc, much around with that very carefully. Grant. -- http://bugs.id.au/ |