[SOLVED] open-vm-tools-modules out of date

open-vm-tools-modules has been flagged out-of-date today because it requires < 3.3 kernel.
This is stopping me from updating to 3.3-ARCH.
Can anyone advise what it would take to update this? If it's complicated, how long would it normally be before it is updated by the maintainer?
Thanks in advance.
--Ja'far
Last edited by jr0 (2012-04-08 21:53:51)

The NEWS file in ~/abs/open-vm-tools-modules/.../src/ said
Targets (1): open-vm-tools-modules-2012.03.13-1
open-vm-tools 2012.03.13 changes:
        * Updates for newer Linux kernel releases (3.3).
so I thought it was worth risking removing the requires <3.3 from PKGBUILD, like so (I didn't mean to comment the second "depends=" line):
package() {
_kernver=`pacman -Q linux | cut -d . -f 2 | cut -f 1 -d -`
# depends=("linux>=3.${_kernver}" "linux<3.`expr ${_kernver} + 1`")
# depends=("linux>=3.${_kernver}")
KERNEL_VERSION=`cat /lib/modules/extramodules-3.${_kernver}-ARCH/version`
msg "Kernel = $KERNEL_VERSION"
Seems to be working, so marking SOLVED.

Similar Messages

  • Open-vm-tools-modules and kernel rebuild

    Initially when I installed open-vm-tools-modules the wiki instructed me to rebuild the kernel to include the VMWare drivers.
    Today there was an upgrade to open-vm-tools-modules and I was wondering if a kernel rebuild is required every time this package is upgraded.

    I would just like to note that I  am having the same problem in VMware Fusion 4. But this is an update. I read what you said about having a problem doing pacman -S open-vm-tools-modules: when I enter the command it succeeds. But despite this, when I do sudo /etc/rc.d/open-vm-tools start it still fails, but it doesn't print anything about the vmblock. Doing strace produces some output that I really can't understand at all.
    You should see my post here https://bbs.archlinux.org/viewtopic.php … 0#p1048450

  • When Firefox opens my MSN homepage is out of date and will not update

    When Firefox (v 4) opens my homepage is out of date and will not update to the current date even when reloaded

    I'd recommend you delete the URL to your homepage which is causing the problem via Tools | Options | General and then go to the MSN homepage again and click the button "Use Current Page".
    MSN may have changed the coding in the URL which is causing Firefox to load an outdated page with your current settings.

  • [SOLVED] How to really install Open VMware Tools?

    I tried the steps shown in the wiki, but it's not working at all. I have Arch+KDE installed in VMware Player 5. The steps I followed for the installation of VMware tools are:
    pacman -S open-vm-tools open-vm-tools-modules
    systemctl enable vmtoolsd.service
    But after a reboot the Tools doesn't seem to work properly, even If I try to restart with the tools enabled the systems hangs on the process.
    Some help will be really appreciated.
    Cheers.
    Last edited by AurosGamma (2012-12-02 05:09:42)

    There are some known issues regarding the current versions of the open VMWare tools, check this topic.
    The steps you took provide minimal functionality, at least keeping the clock in sync with the host and handling screen resizing. For copy and paste and shared folders, the wiki has some additional info.
    The system seems to hang on reboot, but proceeds normally after about 90 seconds (it's how long systemd waits before forcefully killing the vmtoolsd daemon).
    Some tips to work around current issues:
    - don't use the latest version of xorg-server (use xorg-server 1.13.0-3 instead)
    - issue a 'killall -9 vmtoolsd; systemctl poweroff' to power off the system

  • Open-vm-tools/official vmware tools not installing.

    I'm trying to install the latest offical vmware tools (16/9/2013) and open-vm-tools but both seem to always fail. I tried some of the patches listed on the wiki, but nothing got me anywhere. The big thing I'm trying to accomplish is to be able to use vmhgfs but, I'd like to have all the tools if possible. Here is what I did.
    Open Vm Tools
    #[root@localhost] - [14-01-01 18:09:33] - [/home/toxicarrow/Documents/firewall] - [R:0]
    pacman -S open-vm-tools open-vm-tools-dkms
    resolving dependencies...
    looking for inter-conflicts...
    Packages (2): open-vm-tools-5:2013.09.16-5 open-vm-tools-dkms-5:2013.09.16-5
    Total Installed Size: 8.21 MiB
    :: Proceed with installation? [Y/n]
    (2/2) checking keys in keyring [#####################################################################################################################] 100%
    (2/2) checking package integrity [#####################################################################################################################] 100%
    (2/2) loading package files [#####################################################################################################################] 100%
    (2/2) checking for file conflicts [#####################################################################################################################] 100%
    (2/2) checking available disk space [#####################################################################################################################] 100%
    (1/2) installing open-vm-tools [#####################################################################################################################] 100%
    >>>
    >>> You can mount VMware Shared Folders via:
    >>> mount -t vmhgfs .host:/ /mnt/hgfs
    >>>
    >>> or by adding this line to /etc/fstab:
    >>> .host:/ /mnt/hgfs vmhgfs defaults 0 0
    >>>
    Optional dependencies for open-vm-tools
    gtkmm [installed]
    libnotify [installed]
    libxtst [installed]
    fuse [installed]
    libsm [installed]
    open-vm-tools-modules: for linux kernel
    open-vm-tools-dkms: for linux-lts and other kernels [pending]
    netctl: suspend-resume network state [installed]
    networkmanager: suspend-resume network state
    (2/2) installing open-vm-tools-dkms [#####################################################################################################################] 100%
    >>> Enable building of open-vm-tools modules:
    >>> $ dkms add open-vm-tools/2013.09.16
    >>>
    >>> Enabling vmxnet driver in /usr/lib/modprobe.d/open-vm-tools-modules.conf
    >>> (this will disable pcnet32 driver)
    >>>
    >>> If vmxnet driver doesn't handle your NIC, you have to manually
    >>> disable loading of pcnet32 driver
    >>>
    #[root@localhost] - [14-01-01 18:09:47] - [/home/toxicarrow/Documents/firewall] - [R:0]
    pacman -S open-vm-tools-modules
    warning: open-vm-tools-dkms-5:2013.09.16-5 is up to date -- reinstalling
    resolving dependencies...
    looking for inter-conflicts...
    Packages (1): open-vm-tools-dkms-5:2013.09.16-5
    Total Installed Size: 5.57 MiB
    Net Upgrade Size: 0.00 MiB
    :: Proceed with installation? [Y/n]
    (1/1) checking keys in keyring [#####################################################################################################################] 100%
    (1/1) checking package integrity [#####################################################################################################################] 100%
    (1/1) loading package files [#####################################################################################################################] 100%
    (1/1) checking for file conflicts [#####################################################################################################################] 100%
    (1/1) checking available disk space [#####################################################################################################################] 100%
    (1/1) reinstalling open-vm-tools-dkms [#####################################################################################################################] 100%
    >>> Enable building of open-vm-tools modules:
    >>> $ dkms add open-vm-tools/2013.09.16
    >>>
    #[root@localhost] - [14-01-01 18:10:14] - [/home/toxicarrow/Documents/firewall] - [R:0]
    dkms install -m open-vm-tools -v 2013.04.16 -k $(uname -r)
    Error! Could not find module source directory.
    Directory: /usr/src/open-vm-tools-2013.04.16 does not exist.
    #[root@localhost] - [14-01-01 18:13:14] - [/home/toxicarrow/Documents/firewall] - [R:2]
    dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
    Kernel preparation unnecessary for this kernel. Skipping...
    Building module:
    cleaning build area....
    make KERNELRELEASE=3.12.6-1-ARCH VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock........
    Error! Build of vmblock.ko failed for: 3.12.6-1-ARCH (x86_64)
    Consult the make.log in the build directory
    /var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
    #[root@localhost] - [14-01-01 18:13:45] - [/home/toxicarrow/Documents/firewall] - [R:7]
    Official Tools
    Before patches
    #[root@localhost] - [14-01-02 2:40:49] - [/home/toxicarrow/vmware/vmware-tools-distrib] - [R:32]
    ./vmware-install.pl
    A previous installation of VMware Tools has been detected.
    The previous installation was made by the tar installer (version 4).
    Keeping the tar4 installer database format.
    You have a version of VMware Tools installed. Continuing this install will
    first uninstall the currently installed version. Do you wish to continue?
    (yes/no) [yes]
    Uninstalling the tar installation of VMware Tools.
    Stopping services for VMware Tools
    Stopping VMware Tools services in the virtual machine:
    Guest operating system daemon: done
    Unmounting HGFS shares: done
    Guest filesystem driver: done
    VM communication interface socket family: done
    VM communication interface: done
    Stopping Thinprint services in the virtual machine:
    Stopping Virtual Printing daemon: done
    The removal of VMware Tools 9.6.1 build-1378637 for Linux completed
    successfully.
    Installing VMware Tools.
    In which directory do you want to install the binary files?
    [/usr/bin]
    What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
    [/etc/init.d]
    What is the directory that contains the init scripts?
    [/etc/init.d]
    In which directory do you want to install the daemon files?
    [/usr/sbin]
    In which directory do you want to install the library files?
    [/usr/lib/vmware-tools]
    The path "/usr/lib/vmware-tools" does not exist currently. This program is
    going to create it, including needed parent directories. Is this what you want?
    [yes]
    In which directory do you want to install the documentation files?
    [/usr/share/doc/vmware-tools]
    The path "/usr/share/doc/vmware-tools" does not exist currently. This program
    is going to create it, including needed parent directories. Is this what you
    want? [yes]
    The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
    successfully. You can decide to remove this software from your system at any
    time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
    Before running VMware Tools for the first time, you need to configure it by
    invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
    this program to invoke the command for you now? [yes]
    Initializing...
    Making sure services for VMware Tools are stopped.
    Stopping VMware Tools services in the virtual machine:
    Guest operating system daemon: done
    Unmounting HGFS shares: done
    Guest filesystem driver: done
    VM communication interface socket family: done
    VM communication interface: done
    Stopping Thinprint services in the virtual machine:
    Stopping Virtual Printing daemon: done
    sh: : command not found
    sh: : command not found
    Before you can compile modules, you need to have the following installed...
    make
    gcc
    kernel headers of the running kernel
    Searching for GCC...
    Detected GCC binary at "/bin/gcc".
    The path "/bin/gcc" appears to be a valid path to the gcc binary.
    Would you like to change it? [no]
    Searching for a valid kernel header path...
    Detected the kernel headers at "/lib/modules/3.12.6-1-ARCH/build/include".
    The path "/lib/modules/3.12.6-1-ARCH/build/include" appears to be a valid path
    to the 3.12.6-1-ARCH kernel headers.
    Would you like to change it? [no]
    make: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-lyoMIO/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-lyoMIO/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
    make: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-VlEWPD/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-VlEWPD/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
    make: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/af_vsock.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/vsockAddr.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notifyQState.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/util.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/stats.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notify.o
    CC [M] /tmp/modconfig-VlEWPD/vsock-only/driverLog.o
    LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-VlEWPD/vsock-only/vsock.mod.o
    LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
    The module vmxnet3 from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The module pvscsi from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The module vmmemctl from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The VMware Host-Guest Filesystem allows for shared folders between the host OS
    and the guest OS in a Fusion or Workstation virtual environment. Do you wish
    to enable this feature? [yes]
    make: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-C1YUSD/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-C1YUSD/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
    make: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/message.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/rpcout.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpName.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/request.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/stubs.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/link.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/bdhandler.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/transport.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/module.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/file.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/super.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmci.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dir.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/fsutil.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsBd.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/filesystem.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/page.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoorGcc64.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoor.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsEscape.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/inode.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dentry.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLite.o
    CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/kernelStubsLinux.o
    LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.mod.o
    LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
    cp -f vmhgfs.ko ./../vmhgfs.o
    make: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
    The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
    upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
    The vmblock enables dragging or copying files between host and guest in a
    Fusion or Workstation virtual environment. Do you wish to enable this feature?
    [yes]
    NOTICE: It appears your system does not have the required fuse packages
    installed. The VMware blocking filesystem requires the fuse packages and its
    libraries to function properly. Please install the fuse or fuse-utils package
    using your systems package management utility and re-run this script in order
    to enable the VMware blocking filesystem.
    VMware automatic kernel modules enables automatic building and installation of
    VMware kernel modules at boot that are not already present. This feature can be
    enabled/disabled by re-running vmware-config-tools.pl.
    Would you like to enable VMware automatic kernel modules?
    [no]
    Detected X server version 1.14.5
    Distribution provided drivers for Xorg X server are used.
    Skipping X configuration because X drivers are not included.
    Warning: This script could not find mkinitrd or update-initramfs and cannot
    remake the initrd file!
    Checking acpi hot plug done
    Starting VMware Tools services in the virtual machine:
    Switching to guest configuration: done
    VM communication interface: done
    VM communication interface socket family: failed
    Guest filesystem driver: failed
    Mounting HGFS shares: failed
    VMware User Agent: done
    Guest operating system daemon: done
    Unable to start services for VMware Tools
    Execution aborted.
    After patches
    #[root@localhost] - [14-01-02 2:44:39] - [/home/toxicarrow/vmware] - [R:0]
    git clone https://github.com/rasa/vmware-tools-patches.git
    Cloning into 'vmware-tools-patches'...
    remote: Reusing existing pack: 134, done.
    remote: Total 134 (delta 0), reused 0 (delta 0)
    Receiving objects: 100% (134/134), 22.06 KiB | 0 bytes/s, done.
    Resolving deltas: 100% (74/74), done.
    Checking connectivity... done.
    #[root@localhost] - [14-01-02 2:44:55] - [/home/toxicarrow/vmware] - [R:0]
    ls
    = VMwareTools-9.6.1-1378637.tar.gz manifest.txt* run_upgrader.sh vmware-tools-distrib/ vmware-tools-patches/ vmware-tools-upgrader-32* vmware-tools-upgrader-64*
    #[root@localhost] - [14-01-02 2:44:57] - [/home/toxicarrow/vmware] - [R:0]
    cp VMwareTools-9.6.1-1378637.tar.gz vmware-tools-patches
    #[root@localhost] - [14-01-02 2:45:13] - [/home/toxicarrow/vmware] - [R:0]
    cd vmware-tools-patches
    #[root@localhost] - [14-01-02 2:45:17] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
    ls
    LICENSE VMwareTools-9.6.1-1378637.tar.gz patch-module.sh* patches/ untar-and-patch-and-compile.sh*
    README.md download-patches.sh* patch-modules.sh* untar-all-and-patch.sh* untar-and-patch.sh*
    #[root@localhost] - [14-01-02 2:45:18] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
    ./untar-and-patch-and-compile.sh
    === Patching ./VMwareTools-9.6.1-1378637.tar.gz ...
    --- Applying vmci/vmware9.k3.8rc4.patch ...
    patching file linux/driver.c
    Hunk #1 FAILED at 124.
    Hunk #2 FAILED at 1750.
    Hunk #3 FAILED at 1978.
    3 out of 3 hunks FAILED -- saving rejects to file linux/driver.c.rej
    --- Applying vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch ...
    patching file file.c
    patching file filesystem.c
    patching file fsutil.c
    patching file inode.c
    Hunk #1 succeeded at 514 (offset -3 lines).
    Hunk #2 succeeded at 617 (offset -3 lines).
    Hunk #3 succeeded at 1216 (offset -3 lines).
    patching file shared/compat_cred.h
    --- Applying vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch ...
    patching file inode.c
    Hunk #1 succeeded at 31 with fuzz 1.
    Hunk #2 FAILED at 1893.
    Hunk #3 FAILED at 1946.
    2 out of 3 hunks FAILED -- saving rejects to file inode.c.rej
    --- Applying vmhgfs/vmware9.compat_mm.patch ...
    patching file shared/compat_mm.h
    Hunk #1 FAILED at 91.
    Hunk #2 FAILED at 100.
    2 out of 2 hunks FAILED -- saving rejects to file shared/compat_mm.h.rej
    --- Applying vmhgfs/patch_inode.c.patch ...
    patching file inode.c
    Hunk #1 FAILED at 1798.
    Hunk #2 FAILED at 1818.
    2 out of 2 hunks FAILED -- saving rejects to file inode.c.rej
    --- Applying vmblock/vmblock.3.11.patch ...
    patching file linux/file.c
    --- Applying vmblock/vmblock.3.10.patch ...
    patching file linux/control.c
    Creating a new VMware Tools installer database using the tar4 format.
    Installing VMware Tools.
    In which directory do you want to install the binary files?
    [/usr/bin]
    What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
    [/etc/init.d]
    What is the directory that contains the init scripts?
    [/etc/init.d]
    In which directory do you want to install the daemon files?
    [/usr/sbin]
    In which directory do you want to install the library files?
    [/usr/lib/vmware-tools]
    The path "/usr/lib/vmware-tools" does not exist currently. This program is
    going to create it, including needed parent directories. Is this what you want?
    [yes]
    In which directory do you want to install the documentation files?
    [/usr/share/doc/vmware-tools]
    The path "/usr/share/doc/vmware-tools" does not exist currently. This program
    is going to create it, including needed parent directories. Is this what you
    want? [yes]
    The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
    successfully. You can decide to remove this software from your system at any
    time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
    Before running VMware Tools for the first time, you need to configure it by
    invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
    this program to invoke the command for you now? [yes]
    Initializing...
    Making sure services for VMware Tools are stopped.
    Stopping VMware Tools services in the virtual machine:
    Guest operating system daemon: done
    Unmounting HGFS shares: done
    Guest filesystem driver: done
    Stopping Thinprint services in the virtual machine:
    Stopping Virtual Printing daemon: done
    sh: : command not found
    sh: : command not found
    make: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-HrsGw6/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-HrsGw6/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
    make: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-pVUBEq/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-pVUBEq/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
    make: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/af_vsock.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/vsockAddr.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notifyQState.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/util.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/stats.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notify.o
    CC [M] /tmp/modconfig-pVUBEq/vsock-only/driverLog.o
    LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-pVUBEq/vsock-only/vsock.mod.o
    LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
    The module vmxnet3 from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The module pvscsi from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The module vmmemctl from this package is not supported for kernels >= 3.10.
    Please enable this module in your kernel. You may also have to enable
    HYPERVISOR_GUEST.
    The VMware Host-Guest Filesystem allows for shared folders between the host OS
    and the guest OS in a Fusion or Workstation virtual environment. Do you wish
    to enable this feature? [yes]
    make: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/driver.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDriver.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciResource.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciContext.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciEvent.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQPair.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciRoute.o
    CC [M] /tmp/modconfig-ukgHfB/vmci-only/driverLog.o
    LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-ukgHfB/vmci-only/vmci.mod.o
    LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
    make: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
    Using 2.6.x kernel build system.
    /bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoorGcc64.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/message.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/request.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/filesystem.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpName.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dentry.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/rpcout.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/stubs.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsEscape.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/link.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/transport.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/module.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/file.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/super.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmci.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/bdhandler.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dir.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/fsutil.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsBd.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/page.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoor.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/inode.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLite.o
    CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/kernelStubsLinux.o
    LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.mod.o
    LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.ko
    make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
    /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
    cp -f vmhgfs.ko ./../vmhgfs.o
    make: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
    The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
    upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
    The vmblock enables dragging or copying files between host and guest in a
    Fusion or Workstation virtual environment. Do you wish to enable this feature?
    [yes]
    NOTICE: It appears your system does not have the required fuse packages
    installed. The VMware blocking filesystem requires the fuse packages and its
    libraries to function properly. Please install the fuse or fuse-utils package
    using your systems package management utility and re-run this script in order
    to enable the VMware blocking filesystem.
    VMware automatic kernel modules enables automatic building and installation of
    VMware kernel modules at boot that are not already present. This feature can be
    enabled/disabled by re-running vmware-config-tools.pl.
    Would you like to enable VMware automatic kernel modules?
    [no]
    Detected X server version 1.14.5
    Distribution provided drivers for Xorg X server are used.
    Skipping X configuration because X drivers are not included.
    Warning: This script could not find mkinitrd or update-initramfs and cannot
    remake the initrd file!
    Checking acpi hot plug done
    Starting VMware Tools services in the virtual machine:
    Switching to guest configuration: done
    VM communication interface: done
    VM communication interface socket family: failed
    Guest filesystem driver: failed
    Mounting HGFS shares: failed
    Guest operating system daemon: done
    Unable to start services for VMware Tools
    Execution aborted.
    #[root@localhost] - [14-01-02 2:46:53] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
    Any idea what I should be doing?

    I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
    Did you make any progress ??
    Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
    Consult the make.log in the build directory
    /var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
    make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
    Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
    make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
    make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
    Makefile:120: recipe for target 'vmblock.ko' failed
    Last edited by crankshaft (2014-01-10 11:32:32)

  • Open-vm-tools installation

    I have installed Arch linux inside VMware. ArchLinux image (archlinux-2011.08.19-core-i686.iso) is downloaded from net.
    This image has Linux kernel 3.0 inside it. With this, am trying to install open-vm-tools.
    pacman -S open-vm-tools with this command..
    Resolving dependencies...
    looking for inter-conflicts..
    Targets (8): libdnet-1.12-6 libsigc++-2.2.10-1 libxss-1.2.1-1 linux-3.2.1-1
                     open-vm-tools-modules-2011.12.20-3 scrnsaverproto-12.1-1
                     uriparser-0.7.5-1 open-vm-toos-2011.12.20-1
    As you see above -depdency lists linux 3.2.1-1. This is due to the fact that open-vm-tools-modules-2011.12.20-3 has a dependency on linux >=3.2
    I am new to Linux. I dont understand this. Where i can get the open-vm-tools package that can run with Linux 3.0 kernel image?
    any help would be greatly appreciated.

    Thanks for your quick reply.
    I am trying this for the last one week. I updated all my packages before I started with this exercise.
    I try to do that now once again. Now the list includes "linux 3.2" also? I want my base image as Linux 3.0 kernel. On top of this, i would like to install open-vm-tools.
    how do i get the open-vm-tools package specifically for linux 3.0?

  • Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Back up all data.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
    Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
    When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    resetpassword
    That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • My Mac refuses to open certain pages e.g. google/facebook for a weird reason "Your flash player may be out of date and you need to update it", but my flash player is up to date.

    My Mac refuses to open certain pages e.g. google/facebook for a weird reason "Your flash player may be out of date and you need to update it", but my flash player is up to date. I tried to install a new flash player version "setup.exe" but it said the file cannot be opened because the application is not supported on MAC OS X, does anyone have same problem? please help.
    Thanks

    i dont use google chrome,

  • Program or Function module to delete data from Open Hub Destination Table

    Hi All,
    Can anybody suggest me a Program or Function module to delete data from Open Hub Destination Table.
    Thanks & Regards,
    Vinay Kumar

    You can simply goto t-code SE14 mention the open hub destination table and Delete data by clicking on "Activate and Adjust database" with radio button "Delete Data".
    Regards,
    Arminder

  • On opening gogle I get the message:"WARNING! Your Flash Player may be out of date. Please update to continue" - on clicking ok I am diverted to Flash Player Pro download site?? Is this a Adobe product? And why even though i have the latest flash player ve

    On opening google I get the message:"WARNING! Your Flash Player may be out of date. Please update to continue" - on clicking ok I am diverted to Flash Player Pro download site?? Is this a Adobe product? And why even though i have the latest flash player version I repeatedly get the message?

    This is not a message that Adobe is providing, and I recommend that you not click on the link. It sounds as though you might have malware on your computer.
    For more information, see: http://malwaretips.com/blogs/warning-your-flash-player-may-be-out-of-date-virus/ or http://wasconet.com/how-to-remove-warning-your-flash-player-may-be-out-of-date/

  • My MacKeeper says iPhoto is out of date.  When I try to update the App Store says I need IOS 10.9 or later.  I have 10.7.5 and when I check for updates my Mac says the software is up to date.  How do I solve this problem??

    My MacKeeper says iPhoto is out of date.  When I try to update it, the App Store says I need IOS 10.9 or later.  I have 10.7.5 and when I check for updates my Mac says the OS software is up to date.  How do I solve this problem??

    1. First step to solving the Problem: Trash MacKeeper. It's a pile of trash that does far more harm to your computer than good.
    https://discussions.apple.com/docs/DOC-3691
    2. What version of iPhoto do you have? (iPhoto Menu -> About iPhoto)

  • I've upgraded to Yosemite. Iphoto is out of date and won't open. I'm being directed to the app store for a free upgrade but there is nothing there. being told 'upgrade is not available in the US'

    I've upgraded to Yosemite. Iphoto is out of date and won't open. I'm being directed to the app store for a free upgrade but there is nothing there. being told 'upgrade is not available in the US'

    iPhoto is no longer available from the Mac App Store. Update to 10.10.3 and use Photos.
    (125792)

  • I just installed Photoshop elements 11. Install fine. When I clicked to open Organizer, I received a messaging indicating that it was out of date and coudl not be upgraded. How can I address/fix this?

    I just installed Photoshop elements 11. Install of the application was fine. When I clicked to open Organizer, I received a messaging indicating that it was out of date and coudl not be upgraded. How can I address/fix this?

    Thank you for the replies. I'm afraid neither one helped.
    kglad, I never get to any error code so your link can't help.
    Jeff, I looked at your link and
    a) again, I never make it to an error code
    b) I'm definitely connected to the internet
    c) I can access secure sites; I tried connecting with the firewall disabled and the same thing happened, so I don't believe it's a firewall issue.
    d) I don't understand the checking host sites - this is far too complicated for a novice user. It should not be this difficult to get a software running. I don't want to mess with these kinds of settings.
    e) I followed the steps for the global sign in root CA and my screen looks the same as the picture here.
    I can't activate the software offline as there is no option to generate a response code when I click on having trouble connecting to the internet. All I get is a prompt to change my password.
    If the problem were simply connectivity from my computer, then why does the box completely freeze? Can't cancel, can't click on the little X to close it, can't right click on the box to close it. I have to reboot every single time. I know others have had the same problem and I haven't found any answers that I could apply.
    I don't understand for the life of me why Adobe does not have TELEPHONE customer support. I have spent 2 days on this, this is crazy.

  • WARNING! Your Flash Player may be out of date.   how can i solve this problem/

    WARNING! Your Flash Player may be out of date.   how can i solve this problem/

    The Flash update alerts are fake, and are intended to mislead you into installing malware and/or to steal your identity. They're the result of an attack on your router that has caused you to get false results from looking up the addresses of Internet servers. Requests sent to well-known websites such as Google and YouTube are redirected to a server controlled by the attacker.
    The router's documentation should tell you how to reset it to the factory default state. Usually there's a pinhole switch somewhere in the back. It may be labeled "RESET." Insert a paper clip and press the button inside for perhaps 15 seconds, or as long as the instructions specify.
    Then go through the initial setup procedure. I can't be specific, because it's different for every model. The key points are these:
    1. Don't allow the router to be administered from the WAN (Internet) port, if it has that option.
    2. Set a strong password to protect the router's settings: at least ten random upper- and lower-case letters and digits.Don't use the default password or any other that could be guessed.
    3. If the router is wireless, or if you have a wireless access point on the network, use "WPA 2 Personal" security and set another strong password to protect the network. If the router or access point doesn't support WPA 2, it's obsolete and must be replaced.
    During the time the router was compromised, you were redirected to bogus websites. If you ever connected to a secure site and got a warning from your browser that the identity of the server could not be verified, and you dismissed that warning in order to log in, assume that your credentials for the site have been stolen and that the attacker has control of the account. This warning also applies to all websites on which you saw the fake update alerts.

  • I can't open up my Elements 8. Is it too out of date?

    I can't open up my Elements 8? I haven't used it in a while. Is it out of daye and I can'y use it anymore?

    No it is not out of date. I am using it on W7.

Maybe you are looking for