Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
theblackpigOffline
Post subject: Vmware install problem  PostPosted: 01.10.2013, 22:08



Joined: 01.10.2013
Posts: 24
Location: UK
Status: Offline
OK installed VMware Workstation Full 8.0.3-703057.86_64.bundle in teminal I then used ran a patch in terminal
This is the patch module.sh

#! /bin/bash
# VMWare Workstation/Player _host kernel modules_ patcher v0.6.2 by 2010 Artem S. Tashkinov
# Tailored and fixed vmblock patching for the 2.6.39 patch by Stefano Angeleri (weltall)
# Use at your own risk.

fpatch=vmware3.2.0.patch
vmreqver=8.0.3
plreqver=4.0.3


error()
{
echo "$*. Exiting"
exit
}

curdir=`pwd`
bdate=`date "+%F-%H:%M:%S"` || error "date utility didn't quite work. Hm"
vmver=`vmware-installer -l 2>/dev/null | awk '/vmware-/{print $1substr($2,1,5)}'`
vmver="${vmver#vmware-}"
basedir=/usr/lib/vmware/modules/source
ptoken="$basedir/.patched"
bkupdir="$basedir-$vmver-$bdate-backup"

unset product
[ -z "$vmver" ] && error "VMWare is not installed (properly) on this PC"
[ "$vmver" == "workstation$vmreqver" ] && product="VMWare WorkStation"
[ "$vmver" == "player$plreqver" ] && product="VMWare Player"
[ -z "$product" ] && error "Sorry, this script is only for VMWare WorkStation $vmreqver or VMWare Player $plreqver"

[ "`id -u`" != "0" ] && error "You must be root to run this script"
[ -f "$ptoken" ] && error "$ptoken found. You have already patched your sources"
[ ! -d "$basedir" ] && error "Source '$basedir' directory not found, reinstall $product"
[ ! -f "$fpatch" ] && error "'$fpatch' not found. Please, copy it to the current '$curdir' directory"

tmpdir=`mktemp -d` || exit 1
cp -an "$basedir" "$bkupdir" || exit 2

cd "$tmpdir" || exit 3
find "$basedir" -name "*.tar" -exec tar xf '{}' \; || exit 4

patch -p1 < "$curdir/$fpatch" || exit 5
tar cf vmci.tar vmci-only || exit 6
tar cf vsock.tar vsock-only || exit 7
tar cf vmnet.tar vmnet-only || exit 8
tar cf vmmon.tar vmmon-only || exit 9
tar cf vmblock.tar vmblock-only || exit 10

cp -a *.tar "$basedir" || exit 11
rm -rf "$tmpdir" || exit 12
touch "$ptoken" || exit 13
cd "$curdir" || exit 14

vmware-modconfig --console --install-all

echo -e "\n"
echo "All done, you can now run $product."
echo "Modules sources backup can be found in the '$bkupdir' directory"

And this is the patch

diff -u -r source802/vmblock-only/linux/filesystem.c source/vmblock-only/linux/filesystem.c
--- source802/vmblock-only/linux/filesystem.c 2012-01-18 22:01:07.000000000 +0100
+++ source/vmblock-only/linux/filesystem.c 2012-04-01 11:48:24.000000000 +0200
@@ -525,7 +525,11 @@
return -EINVAL;
}

+#if LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 2, 0)
+#include <linux>
+#endif
+
// VNet_FilterLogPacket.action for dropped packets
#define VNET_FILTER_ACTION_DRP (1)
#define VNET_FILTER_ACTION_DRP_SHORT (2)
diff -u -r source802/vmnet-only/netif.c source/vmnet-only/netif.c
--- source802/vmnet-only/netif.c 2012-01-18 23:22:02.000000000 +0100
+++ source/vmnet-only/netif.c 2012-01-26 13:41:18.000000000 +0100
@@ -62,7 +62,9 @@
static int VNetNetifStartXmit(struct sk_buff *skb, struct net_device *dev);
static struct net_device_stats *VNetNetifGetStats(struct net_device *dev);
static int VNetNetifSetMAC(struct net_device *dev, void *addr);
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 42, 0) || (LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 0, 0))
static void VNetNetifSetMulticast(struct net_device *dev);
+#endif
#if 0
static void VNetNetifTxTimeout(struct net_device *dev);
#endif
@@ -131,7 +133,9 @@
.ndo_stop = VNetNetifClose,
.ndo_get_stats = VNetNetifGetStats,
.ndo_set_mac_address = VNetNetifSetMAC,
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 42, 0) || (LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 0, 0))
.ndo_set_multicast_list = VNetNetifSetMulticast,
+#endif
/*
* We cannot stuck... If someone will report problems under
* low memory conditions or some such, we should enable it.
@@ -611,12 +615,12 @@
*
*----------------------------------------------------------------------
*/
-
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 42, 0) || (LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 0, 0))
void
VNetNetifSetMulticast(struct net_device *dev) // IN: unused
{
}
-
+#endif

/*
*----------------------------------------------------------------------
diff -u -r source802/vmnet-only/userif.c source/vmnet-only/userif.c
--- source802/vmnet-only/userif.c 2012-01-18 23:22:02.000000000 +0100
+++ source/vmnet-only/userif.c 2012-01-26 13:28:48.000000000 +0100
@@ -517,10 +517,18 @@
unsigned int tmpCsum;
const void *vaddr;

+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 42, 0) && LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 2, 0)
+ vaddr = kmap(skb_frag_page(frag));
+#else
vaddr = kmap(frag->page);
+#endif
tmpCsum = csum_and_copy_to_user(vaddr + frag->page_offset,
curr, frag->size, 0, &err);
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 42, 0) && LINUX_VERSION_CODE <KERNEL_VERSION>= KERNEL_VERSION(3, 2, 0)
+ kunmap(skb_frag_page(frag));
+#else
kunmap(frag->page);
+#endif
if (err) {
return err;
}

Now when I launch VMware I get this



But when Iclick on install that disappears and nothing happens
any help would be appreciated.
I should add this has never happened before when installing into a Debian system.
 
 View user's profile Send private message  
Reply with quote Back to top
diblOffline
Post subject: RE: Vmware install problem  PostPosted: 02.10.2013, 00:24
Moderator


Joined: 22.12.2011
Posts: 761
Location: Dayton, Ohio, USA
Status: Offline
Having maintained my VMware installations for a couple years, and patched my way since 2.9, I'm not sure exactly what happens if you try a VMware installation on a brand new siduction system.

Having said that, I seriously doubt that there is any need to go as far back as the 2.6.39 patch. But I would think you do need the more recent patches -- perhaps the 3.10 and the 3.11 ones in my recent posts.

Also, I would think the new ver. 10 Workstation would be less in need of patching than your ver. 8. It looks like your error is caused by the failure of gksu to launch the request for root privileges, which is an issue I saw and posted here.

In a root terminal, try these:

      Code:
service vmware stop


      Code:
vmware-modconfig --console --install-all


and post back with any error output.

_________________
Asus P6X58D-E, i7-950, Nvidia GTX-480, OCZ Revodrive, 2@WD1002FAEX in BTRFS
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
theblackpigOffline
Post subject:   PostPosted: 02.10.2013, 11:31



Joined: 01.10.2013
Posts: 24
Location: UK
Status: Offline
Output
john@john:~$ su
Password:
root@john:/home/john# service vmware stop
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
root@john:/home/john# vmware-modconfig --console --install-all
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.9-3.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.9-3.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
/tmp/vmware-root/modules/vmnet-only/driver.c: In function ‘VNetFileOpIoctl.isra.5’:
/tmp/vmware-root/modules/vmnet-only/driver.c:999:17: warning: ‘hubJack’ may be used uninitialized in this function [-Wmaybe-uninitialized]
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.9-3.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
/tmp/vmware-root/modules/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/vmware-root/modules/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
In file included from include/linux/proc_fs.h:5:0,
from /tmp/vmware-root/modules/vmblock-only/linux/control.c:28:
include/linux/fs.h:2044:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/vmware-root/modules/vmblock-only/vmblock.ko] undefined!
CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.9-3.towo-siduction-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
/tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: initializer element is not constant
/tmp/vmware-root/modules/vmci-only/linux/driver.c:127:4: error: (near initialization for ‘vmci_driver.remove’)
/tmp/vmware-root/modules/vmci-only/linux/driver.c:1745:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
/tmp/vmware-root/modules/vmci-only/linux/driver.c:1973:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_host’:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_guest’:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msi’:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_msix’:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c: At top level:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2054:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2128:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
/tmp/vmware-root/modules/vmci-only/linux/driver.c:1708:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root/modules/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.9-3.towo-siduction-amd64'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Unable to install vmci
root@john:/home/john#

Could last line be the problem ?
 
 View user's profile Send private message  
Reply with quote Back to top
diblOffline
Post subject:   PostPosted: 02.10.2013, 14:20
Moderator


Joined: 22.12.2011
Posts: 761
Location: Dayton, Ohio, USA
Status: Offline
I think you went wrong to use the 2.6.39 patch. I'm not 100% certain, but if it were me, with Workstation 8, this is what I would try:

1. Use the vmware uninstaller to uninstall it (I can't remember that command off the top of my head, but I have it if you need it), go to the /usr/lib/vmware/modules directory and rm -rf * the module source files.

2. Install Workstation 8 again.

3. Follow this post to patch for kernel 3.10.

4. Then follow this post to patch for kernel 3.11.

5. Then run the command to build the modules in a root terminal:

      Code:
vmware-modconfig --console --install-all


and let's see what you get. If the vmci module still doesn't build and install correctly, we might need to go back to pick up the 3.8 patch, which addressed that module.

_________________
Asus P6X58D-E, i7-950, Nvidia GTX-480, OCZ Revodrive, 2@WD1002FAEX in BTRFS
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
theblackpigOffline
Post subject:   PostPosted: 02.10.2013, 21:44



Joined: 01.10.2013
Posts: 24
Location: UK
Status: Offline
Thanks dibi , will give it a go . It will have to wait till November as I'm off on my summer hols shortly but will let you know how it goes.
 
 View user's profile Send private message  
Reply with quote Back to top
absolutOffline
Post subject:   PostPosted: 03.10.2013, 13:43



Joined: 16.01.2012
Posts: 79

Status: Offline
sorry to jump into this thread. i'd like to suggest that for scripts or console output we stick to using [ code ] [/ code ] tags...

theblackpig, you can add them to your earlier posts by editing them
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 11 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio