Hi list,

up to kernel 2.6.18.5 all is ok but using
2.6.19 and 2.6.19.1 I can't compile vmware modules
for vmware server in my host running slackware 11.00.

Same failure on centrino dual and sempron.

In your experience is Slackware problem or kernel/vmware?

thanks for any suggestion/comment

/usr/bin/vmware-config.pl --compile

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.19.1/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19.1'
CC [M] /tmp/vmware-config0/vmnet-only/driver.o
CC [M] /tmp/vmware-config0/vmnet-only/hub.o
CC [M] /tmp/vmware-config0/vmnet-only/userif.o
/tmp/vmware-config0/vmnet-only/userif.c: In function
`VNetCopyDatagramToUser':
/tmp/vmware-config0/vmnet-only/userif.c:629: error: `CHECKSUM_HW'
undeclared (first use in this function)
/tmp/vmware-config0/vmnet-only/userif.c:629: error: (Each undeclared
identifier is reported only once
/tmp/vmware-config0/vmnet-only/userif.c:629: error: for each function
it appears in.)
make[2]: *** [/tmp/vmware-config0/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19.1'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
Unable to build the vmnet module.
Execution aborted.

On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:

>Hi list,
>
>up to kernel 2.6.18.5 all is ok but using
>2.6.19 and 2.6.19.1 I can't compile vmware modules
>for vmware server in my host running slackware 11.00.
>
>Same failure on centrino dual and sempron.
>
>In your experience is Slackware problem or kernel/vmware?

Update vmware to latest:

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/home/grant/linux/linux-2.6.19.1a'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/home/grant/linux/linux-2.6.19.1a'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.

Grant.
--
http://bugsplatter.mine.nu/

Grant wrote:
> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>
> Update vmware to latest:
>
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vmmon-only'
> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

Thanks Grant but I don't find any new version.
I have VMware-server-1.0.1-29996.i386.tgz.
Probably I can try with a new install of both
Slackware and Vmware. Now I know that I have
some problem. :-)

On Tue, 19 Dec 2006 18:22:41 +0100, kojak wrote:

> Grant wrote:
>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>
>> Update vmware to latest:
>>
>> Using 2.6.x kernel build system.
>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
>
> Thanks Grant but I don't find any new version.
> I have VMware-server-1.0.1-29996.i386.tgz.
> Probably I can try with a new install of both
> Slackware and Vmware. Now I know that I have
> some problem. :-)

I suggest reading through the forums and KB because the date on this
predates 2.6.19 and almost certainly won't compile. VMWare Workstation,
for example, was redone for the new kernels.

http://kb.vmware.com/vmtnkb/search.d...=Forum%20Posts

may help shed some light.


--
Peter

On Tue, 19 Dec 2006 18:22:41 +0100, kojak wrote:

> Grant wrote:
>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>
>> Update vmware to latest:
>>
>> Using 2.6.x kernel build system.
>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
>
> Thanks Grant but I don't find any new version.
> I have VMware-server-1.0.1-29996.i386.tgz.
> Probably I can try with a new install of both
> Slackware and Vmware. Now I know that I have
> some problem. :-)

I suggest reading through the forums and KB because the date on this
predates 2.6.19 and almost certainly won't compile. VMWare Workstation,
for example, was redone for the new kernels.

http://kb.vmware.com/vmtnkb/search.d...=Forum%20Posts

may help shed some light.


--
Peter

Peter wrote:
> On Tue, 19 Dec 2006 18:22:41 +0100, kojak wrote:
>
>> Grant wrote:
>>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>>
>>> Update vmware to latest:
>>>
>>> Using 2.6.x kernel build system.
>>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
>> Thanks Grant but I don't find any new version.
>> I have VMware-server-1.0.1-29996.i386.tgz.
>> Probably I can try with a new install of both
>> Slackware and Vmware. Now I know that I have
>> some problem. :-)
>
> I suggest reading through the forums and KB because the date on this
> predates 2.6.19 and almost certainly won't compile. VMWare Workstation,
> for example, was redone for the new kernels.
>
> http://kb.vmware.com/vmtnkb/search.d...=Forum%20Posts
>
> may help shed some light.
>
Thanks Peter,
but at the present I use kernel 2.6.18.5 without problem, and Grant
show that 2.6.19.1 can be used to, so I have probably to recompile my
kernel firs (make olconfig) becouse vmware-server-29996 work perfecly.

On Tue, 19 Dec 2006 18:22:41 +0100, kojak <kojak@freemail.it> wrote:

>Grant wrote:
>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>
>> Update vmware to latest:
>>
>> Using 2.6.x kernel build system.
>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
>
>Thanks Grant but I don't find any new version.
>I have VMware-server-1.0.1-29996.i386.tgz.
>Probably I can try with a new install of both
>Slackware and Vmware. Now I know that I have
>some problem. :-)

I tested with VMware-workstation-5.5.3-34685

Grant.
--
http://bugsplatter.mine.nu/

Grant wrote:
> On Tue, 19 Dec 2006 18:22:41 +0100, kojak <kojak@freemail.it> wrote:
>
>> Grant wrote:
>>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>>
>>> Update vmware to latest:
>>>
>>> Using 2.6.x kernel build system.
>>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
>> Thanks Grant but I don't find any new version.
>> I have VMware-server-1.0.1-29996.i386.tgz.
>> Probably I can try with a new install of both
>> Slackware and Vmware. Now I know that I have
>> some problem. :-)
>
> I tested with VMware-workstation-5.5.3-34685
>
> Grant.

Oh I see but I never tryed this. I know that WS have a new relase.
In any case I'm recompiling 2.6.19.1 try again with vmware server
1.0.1 and revert.

tanks for your input Grant.

Paolo

kojak wrote:
> Grant wrote:
>> On Tue, 19 Dec 2006 18:22:41 +0100, kojak <kojak@freemail.it> wrote:
>>
>>> Grant wrote:
>>>> On Tue, 19 Dec 2006 16:40:43 +0100, kojak <kojak@freemail.it> wrote:
>>>>
>>>> Update vmware to latest:
>>>>
>>>> Using 2.6.x kernel build system.
>>>> make: Entering directory `/tmp/vmware-config0/vmmon-only'
>>>> make -C /lib/modules/2.6.19.1a/build/include/.. SUBDIRS=$PWD
>>>> SRCROOT=$PWD/. modules
>>> Thanks Grant but I don't find any new version.
>>> I have VMware-server-1.0.1-29996.i386.tgz.
>>> Probably I can try with a new install of both
>>> Slackware and Vmware. Now I know that I have
>>> some problem. :-)
>>
>> I tested with VMware-workstation-5.5.3-34685
>>
>> Grant.
>
> Oh I see but I never tryed this. I know that WS have a new relase.
> In any case I'm recompiling 2.6.19.1 try again with vmware server 1.0.1
> and revert.

well I found this http://nerdbynature.de/bits/2.6.19-rc5/
so for the moment I remain with 2.6.18.5 waiting for vmware-server-1.0.2

thank again also to Peter

kojak wrote:
> well I found this http://nerdbynature.de/bits/2.6.19-rc5/

Just for curiosity I try the pach and now I can compile.
But for the moment I will continue with 2.6.18.5 and
with 2.6.16.36 for the guest.

-----------------------------------
[root@centrino/tmp/test/vmnet-only]# patch -p1
<../vmnet_CHECKSUM_PARTIAL.diff
patching file Makefile.kernel
patching file bridge.c
patching file userif.c
[root@centrino/tmp/test/vmnet-only]# make
Using 2.6.x kernel build system.
make -C /lib/modules/2.6.19.1/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.19.1'
CC [M] /tmp/test/vmnet-only/driver.o
CC [M] /tmp/test/vmnet-only/hub.o
CC [M] /tmp/test/vmnet-only/userif.o
CC [M] /tmp/test/vmnet-only/netif.o
CC [M] /tmp/test/vmnet-only/bridge.o
CC [M] /tmp/test/vmnet-only/procfs.o
CC [M] /tmp/test/vmnet-only/smac_compat.o
SHIPPED /tmp/test/vmnet-only/smac_linux.x386.o
LD [M] /tmp/test/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/test/vmnet-only/vmnet.mod.o
LD [M] /tmp/test/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.19.1'
cp -f vmnet.ko ./../vmnet.o