A laptop that works integrally with Sun power .Its totally independent form electricity power
Read more here
Friday 23 August 2013
Monday 19 August 2013
How To Install VMWare Tools v4 on Ubuntu 12.04 LTS Server
How To Install VMWare Tools v4 on Ubuntu 12.04 LTS Server and 12.10 Server
Originally posted by: Justin Schier
Last Updated: October 24, 2012
Tested With: Ubuntu 12.10 Server, Ubuntu 12.04 LTS Server, Ubuntu 12.04.1 LTS Server, Ubuntu 11.10 Server
All the guides I found on the Internet, including VMWare’s website were outdated in some way, so I decided to write a guide of my own. I just went through these steps from start to finish on a fresh server and had no problems. In about 5 minutes, you will be able to install VMWare Tools on Ubuntu Server.
- Use Install VMWare Tools option in VMWare Client to attach media
- Update the server
12sudo apt-get -y updatesudo apt-get -y upgrade - Create the mount point
1sudo mkdir -p /media/cdrom - Mount the ISO
1sudo mount /dev/cdrom /media/cdrom
You should see the message: mount: block device /dev/sr0 is write-protected, mounting read-only - Change Directory
1cd /media/cdrom - Copy the tar file to your /tmp directory
1sudo cp VM*.tar.gz /tmp - Install Build tools if necessary
1sudo apt-get -y install linux-headers-server build-essential - Change Directory
1cd /tmp - Unmount the ISO
1sudo umount /media/cdrom - Expand the tar
1sudo tar xzvf VM*.tar.gz - Change Directory
1cd vmware-tools-distrib - To prevent a potential error in the install script on Ubuntu 11.10+, create a special directory
Unable to create symlink “/usr/lib64/libvmcf.so” pointing to file ”/usr/lib/vmware-tools/lib64/libvmcf.so/libvmcf.so”.
1sudo mkdir -p /usr/lib64 - Run the Install Script. The -d flag automatically answers the default to all questions. To customize it, just omit the -d.
1sudo ./vmware-install.pl -d - Reboot
1sudo reboot
Also, please follow me on Twitter: @justinschier
This is "How to do Computing" for everyday usage ...
Tuesday 30 July 2013
Issues with VMware 8 wont run Kernel 3.8 wont let VMware 8 & 9 work
When I try to launch VMware workstation, I get the following error:
No errors, when I select INSTALL nothing happens just closes.
I install manually:
I will start a bounty to fix this.
Ubuntu 13.04 64bit
I have tried a different Kernel, but end up with the same problem.
Tried this as suggested: here
Before you can run VMware, several modules must be compiled and loaded into the kernel CANCEL / INSTALL
No errors, when I select INSTALL nothing happens just closes.
I install manually:
sudo apt-get install open-vm-tools open-vm-tools-dev open-vm-dkms open-vm-toolbox open-vm-tools-devBut already installed to the latest versions.
I will start a bounty to fix this.
Ubuntu 13.04 64bit
pst007x@pst007x-Serval-Professional:~$ uname -a
Linux pst007x-Serval-Professional 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
I have uninstalled and reinstalled all components, but same problem.I have tried a different Kernel, but end up with the same problem.
Tried this as suggested: here
#!/bin/bash
cd
cp -prn /usr/lib/vmware/modules/source /usr/lib/vmware/modules/source-backup
mkdir fixed
cd fixed
find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
## add missing header on kernels
sed -i '/#include "compat_wait.h"/a\#include "compat_sched.h"' vmnet-only/vnetUserListener.c
sed -i '/#include "compat_page.h"/a\#include "compat_sched.h"' vmci-only/include/pgtbl.h
## comment out an invalid definition
sed -i 's|\(extern void poll_initwait(compat_poll_wqueues \*);\)|//\1|' *-only/include/compat_wait.h
tar cf vmblock.tar vmblock-only
tar cf vmci.tar vmci-only
tar cf vmmon.tar vmmon-only
tar cf vmnet.tar vmnet-only
tar cf vmppuser.tar vmppuser-only
tar cf vsock.tar vsock-only
cp -p *.tar /usr/lib/vmware/modules/source
cd /lib/modules/`uname -r`/build/include/linux
ln -s ../generated/autoconf.h
ln -s ../generated/utsrelease.h
cd
vmware-modconfig --console --install-all
# clean up
cd
rm -rf fixed
cd /lib/modules/`uname -r`/build/include/linux
rm autoconf.h utsrelease.h
cd /usr/lib/vmware/modules/
rm -rf source-backup
cd
Didn't work, results of script in terminal:pst007x@pst007x-Serval-Professional:~/Desktop$ sudo ./run
[sudo] password for pst007x:
sed: can't read vmci-only/include/pgtbl.h: No such file or directory
sed: can't read *-only/include/compat_wait.h: No such file or directory
tar: vmppuser-only: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
ln: failed to create symbolic link ‘./autoconf.h’: File exists
ln: failed to create symbolic link ‘./utsrelease.h’:
File exists
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/modconfig-tGleah/vmmon-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/task.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-tGleah/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-tGleah/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-tGleah/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-tGleah/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmnet-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmnet-only/driver.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/hub.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/userif.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/netif.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/bridge.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/filter.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/procfs.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/smac.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-tGleah/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-tGleah/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-tGleah/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-tGleah/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmblock-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/stubs.o
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:38:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:38:4: warning: (near initialisation for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-tGleah/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/modconfig-tGleah/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/super.o
/tmp/modconfig-tGleah/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-tGleah/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/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/modconfig-tGleah/vmblock-only/linux/control.c:28:
include/linux/fs.h:2040:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
/tmp/modconfig-tGleah/vmblock-only/linux/inode.c:49:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/inode.c:49:4: warning: (near initialisation for ‘RootInodeOps.lookup’) [enabled by default]
LD [M] /tmp/modconfig-tGleah/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-tGleah/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-tGleah/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-tGleah/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-tGleah/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmci-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-tGleah/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciHashtable.o
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: initialiser element is not constant
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: (near initialisation for ‘vmci_driver.remove’)
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1754:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1982:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:2063:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:2137:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1717:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/modconfig-tGleah/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/modconfig-tGleah/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/modconfig-tGleah/vmci-only'
Unable to install all modules. See log for details.
pst007x@pst007x-Serval-Professional:~/Desktop$
Tried as suggested below, but same issue:pst007x@pst007x-Serval-Professional:~$ sudo vmware-modconfig --console --install-all
[sudo] password for pst007x:
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/modconfig-IFjtiM/vmmon-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/task.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-IFjtiM/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-IFjtiM/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmnet-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/hub.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/userif.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/netif.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/bridge.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/filter.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/procfs.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/smac.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-IFjtiM/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-IFjtiM/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmblock-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/stubs.o
/tmp/modconfig-IFjtiM/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-IFjtiM/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/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/modconfig-IFjtiM/vmblock-only/linux/control.c:28:
include/linux/fs.h:2040:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:38:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:38:4: warning: (near initialisation for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-IFjtiM/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/modconfig-IFjtiM/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
/tmp/modconfig-IFjtiM/vmblock-only/linux/inode.c:49:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/inode.c:49:4: warning: (near initialisation for ‘RootInodeOps.lookup’) [enabled by default]
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/super.o
LD [M] /tmp/modconfig-IFjtiM/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-IFjtiM/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-IFjtiM/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmci-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciEvent.o
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: initialiser element is not constant
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: (near initialisation for ‘vmci_driver.remove’)
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1754:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1982:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:2063:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:2137:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1717:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/modconfig-IFjtiM/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/modconfig-IFjtiM/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/modconfig-IFjtiM/vmci-only'
Unable to install all modules. See log for details.
pst007x@pst007x-Serval-Professional:~$ sudo apt-get install build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
pst007x@pst007x-Serval-Professional:~$
Friday 12 July 2013
How to get Fedore 17 to upgrade to Fedore 18 Using Yum !!
Hi Guys !!!
I am using Fedora 17 for quite a while on VMware I decide to give it a go because my older brother advice me to do so.. Since here, most of time I've using CentOS, RedHat, Debian Kali and uBuntu mainly...
But I decided to give it a go on Fedora 17, after some months into it I realize that a new release was launched, therefore I decide to upgrade my machine ... And here is the workout ...
Here are some WORDS of RECOMMENDATION BEFORE YOU DO THIS ...
Upgrading using the yum method described here is not recommended for new users. Use FedUp insteadExtracted from: https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
For upgrades to Fedora 18 and later, the recommended upgrade method is the FedUp tool. This section has instructions on using FedUp to upgrade.
For upgrades to Fedora 17 and earlier, the recommended installation method is with a boot media with the Anaconda installer as detailed in the Installation Guide or via PreUpgrade. PreUpgrade is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer.
Although upgrades with yum do work, they are not explicitly tested as part of the release process by the Fedora QA and are not documented in the Fedora installation guide. If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead
2 Upgrading To Fedora 18 (Desktop & Server)
First we must upgrade the rpm package:# sudo yum clean-all
yum upgrade yum yum install fedup yum -y upgrade fedup-cli --network 18 --debuglog fedup-to-18.log
Than when the install finished .. run on terminal the command " # reboot "
Let the machine boot up and then look into the Grub menu and choose the option that says "fedora fedup upgrade"
Press "Enter" and let the system upgrade start ! When it finish's the system will reboot again and then if all goes well you will boot up on the Fedora 18 ...
For more help here are some links : http://fedoraproject.org/wiki/FedUp , http://tech.saos.co.in/post/2013/02/16/upgrade-fedora-17-to-18-using-yum.aspx
To download Fedora : go here http://fedoraproject.org/get-fedora
Hope this article help you guys somehow .. If you guys got any query please drop me some questions I will very happy to answer them ..
:-) Enjoy
This is another posting showing "how to do computing" for everyday computer usages... For a general public
Thursday 11 July 2013
Solve VMWare Workstation 9 Error on Linux Kernel 3.8.0-26
I have VMware Workstations 9 installed on my uBuntu 13 machine and today without any apparent reason it stop working throwing me the following error, every time I've tried to boot up any VM machine.
To solver the problem .. here is what I have done ... created bash script to handle problems with VMware Player on 13.04 ...
Before write the script I've open the terminal and type " #sudo kate " then when kate opened I entered the script and saved on " /usr/src/open-vm-tools-xxxx.xx.xx" (replace the x with year month and day) and save it. Then close Kate
#!/bin/bash if [[ $UID != 0 ]]; then echo "Please run this script with sudo:" echo "sudo $0 $*" exit 1 fi sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)/include/linux/version.h cd /usr/lib/vmware/modules/source sudo tar -xf vmci.tar cd vmci-only sudo sed '127s/.*/ .remove = vmci_remove_device,/' driver.c > driver.c.tmp mv driver.c.tmp driver.c sudo sed '1753s/.*/static int/' driver.c > driver.c.tmp mv driver.c.tmp driver.c sudo sed '1981s/.*/static void/' driver.c > driver.c.tmp mv driver.c.tmp driver.c cd .. sudo tar -cf vmci.tar vmci-only/ sudo rm vmci-only/ -Rf sudo vmware-modconfig --console --install-all sudo rm /usr/src
The Open terminal again and do the following;
after you should have VMware workstation running...
Subscribe to:
Posts (Atom)
How to Create a Ansible Lab on your Local Machine using Vagrant in 5 min using ChatGPT
This is an exciting experiment of mine as DevOps. As I am experimenting with the Tools available ... So, the quest is to " Vagrantfile ...
-
How To Hide and unhide the hard disk Volumes using CMD Commands : First check how many drives are there in my computer and then s...
-
VMWare Workstation doesn't ship in a deb, so it isn't registered in dpkg (which is why you can't find it in the software center...
-
Issue: You go to activate Microsoft Office 2010 and you receive a message stating, “Your copy of Microsoft Office Professional Plus 2010 ca...