Fedora 19 with kernel 3.10 fail to install vmplayer module.

-
If you are having problem start up vmware player on Fedora 19 after upgrade kernel to 3.10, here is the solution.

Basically it is due to the procfs interface and vmnet not able to compiles.

First download the procfs patch from http://communities.vmware.com/thread/446113?start=0&tstart=0 .If you don't have time to read the forum, here is the link of the procfs patch.

Or you can use the following command:

# tar xf /usr/lib/vmware/modules/source/vmnet.tar
# cd vmnet-only
# wget  http://communities.vmware.com/servlet/JiveServlet/download/2239207-108590/procfs.patch
# patch -p1 < procfs.patch
# cd ..
# tar -cvf vmnet.tar vmnet-only/
# cp vmnet.tar /usr/lib/vmware/modules/source/


This will patch the procfs interface.

Secondly download the vmnet patch from http://mysticalzero.blogspot.com/2013/07/vmblock-patch-for-linux-310-vmware.html. The link of the patch is here.

Or you can use the following command:

# tar xf /usr/lib/vmware/modules/source/vmblock.tar
# cd vmblock-only
# wget  https://sites.google.com/site/mysticalzerotmp/vmblock.3.10.patch
# patch -p1 < vmblock.3.10.patch
# cd ..
# tar -cvf vmblock.tar vmblock-only/
# cp vmblock.tar /usr/lib/vmware/modules/source/

then issue this command to compile and install the vmware player module

# sudo vmware-modconfig --console --install-all

I believe these steps not only work on Fedora 19, it should work on most of the Linux distro with kernel 3.10.

Please let me know if these steps didn't work for your linux.



---

Comments

  1. Hakan DuranAugust 11, 2013 at 10:41 AM

    Hi,

    It did not work for me. Here is the last part of the output from the last command:
    ...
    make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Error 2
    make[1]: Leaving directory `/usr/src/kernels/3.10.5-201.fc19.x86_64'
    make: *** [vmnet.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
    Unable to install vmnet

    Please let me know if you need more information.

    ReplyDelete
    Replies
    1. 墮天使 - 祥August 12, 2013 at 11:35 AM

      Hi Hakan Duran,

      May I know what distribution you are using ? Which version of vmplayer that you are running ?

      Can you post more detail of the error message?

      Delete
    2. Hakan DuranAugust 21, 2013 at 8:40 AM

      VMware Player 4.0.3 build-703057

      http://pastebin.com/f60b961G

      Delete
    3. Hakan DuranAugust 21, 2013 at 8:41 AM

      And also Fedora 19 x86_64...

      Delete
    4. Hakan DuranAugust 21, 2013 at 8:42 AM

      VMware Player 4.0.3 build-703057

      Fedora 19 x86_64

      http://pastebin.com/f60b961G

      Delete
    5. Hakan DuranSeptember 2, 2013 at 10:24 AM

      I recently noticed that when I give the patch command there appears several messages of same kind:
      "Reversed (or previously applied) patch detected! Assume -R?"
      Can it be the source of the problem? In other words, am I trying to re-patch a patched source file or something?
      If so, how can I find the unpatched source file to give this solution a shot again?
      Thanks for your thoughts.

      Delete
  2. Righteous JesterAugust 13, 2013 at 2:01 PM

    Thank you very much. Worked without a hitch.

    ReplyDelete
  3. AnonymousAugust 15, 2013 at 1:05 PM

    Worked for me. Thanks.

    ReplyDelete
  4. AnonymousAugust 16, 2013 at 11:26 PM

    Worked like a charm in Fedora 18 in 3.10 x86_64.

    Thanks.

    ReplyDelete
  5. AnonymousAugust 19, 2013 at 3:15 PM

    Worked for me (3.10.6-100.fc18.x86_64). Thank you!

    ReplyDelete
  6. AnonymousAugust 20, 2013 at 5:46 AM

    Worked for me, thanks a lot!
    3.10.7-200.fc19.x86_64

    ReplyDelete
  7. UnknownAugust 22, 2013 at 2:19 AM

    Worked for me too, thank you
    3.10.7-200.fc19.x86_64

    ReplyDelete
  8. zaycoAugust 24, 2013 at 8:18 AM

    Worked for me too, thank you
    Linux 3.10.9-200.fc19.x86_64 x86_64

    ReplyDelete
  9. AnonymousAugust 26, 2013 at 2:42 AM

    Thanks - worked line for line!!!
    Fedora Kernel: 3.10.9-100.fc18.x86_64

    ReplyDelete
  10. AnonymousAugust 28, 2013 at 8:11 AM

    Holy crap! Thanks. This worked flawlessly for me with a newly installed Fedora 19 (with Fedora Utils for codecs, etc)

    ReplyDelete
    Replies
    1. RichG85August 29, 2013 at 1:43 AM

      what version of VMware are you using? I am having issues installing VMware Workstation 9 I have kernel 3.10.9-200.fc19.x86_64 its driving me crazy :/

      Delete
    2. UnknownSeptember 1, 2013 at 11:43 PM

      Same here I'm also getting errors for the same kernel.

      Delete
  11. AnonymousAugust 30, 2013 at 3:56 PM

    Your steps worked flawlessly for me on Fedora 18 with 3.10.9-200.fc18.x86_64 kernel. Thanks!

    ReplyDelete
  12. ToyhoshiAugust 31, 2013 at 8:16 PM

    Thank you very much. Works perfectly!
    9.0.2 build-1031769 + 3.10.9-100.fc18.x86_64

    ReplyDelete
  13. UnknownSeptember 1, 2013 at 11:39 PM

    Hi,
    Didn't work for me :(

    Kernel: 3.10.9-200.fc19.i686
    Error: Unable to install vmnet

    When tried again :
    patch -p1 < procfs.patch
    patching file bridge.c
    Reversed (or previously applied) patch detected! Assume -R? [n]

    Please help.

    ReplyDelete
  14. UnknownSeptember 20, 2013 at 9:13 PM

    Thanks!!!!

    ReplyDelete
  15. AnonymousOctober 17, 2013 at 8:38 PM

    Worked with VMware-Player-5.0.2 on Debian 7 (Wheezy) with kernel from backports.

    ➜ /tmp uname -a
    Linux ap 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux

    Thanks!

    ReplyDelete
  16. AnonymousOctober 31, 2013 at 3:19 AM

    Failed to setup build environment

    fedora 19 and vmware workstation 10

    ReplyDelete

Post a Comment

Feel free to leave your question or comment here, we will reply you as soon as possible.

Popular posts from this blog

Setup mail server with ldap authentication in docker

-
Getting an email server to run in docker is easy but getting an email server with ldap authentication to run in docker spend me a week to get up and running. Here are the steps that I taken. I will assume you already know how to install docker. Install LDAP. docker run \              --detach \              --restart unless-stopped \              --name openldap \              -e LDAP_ORGANISATION=domain \              -e LDAP_DOMAIN=domain.com \              -e LDAP_ADMIN_PASSWORD=complex-password \              -e LDAP_RFC2307BIS_SCHEMA=true \              -e LDAP_REMOVE_CONFIG_AFTER_SETUP=true \              -e LDAP_TLS=false \              -p 389:389 \              --volume /data/openldap/var_lib_ldap:/var/lib/ldap \              --volume /data/openldap/etc_ldap_slapd.d:/etc/ldap/slapd.d \              osixia/openldap:latest Install postfix-book schema into the ldap. # cd /etc/ldap/schema # apt update # apt install vim wget # wget https://raw.githubusercontent.com/variablenix/ldap-
Read more

How to allow non root user to execute hping command ?

-
If you run hping command without root permission or without sudo and you receive this error : [open_sockraw] socket(): Operation not permitted [main] can't open raw socket This command might be able to help you. sudo setcap cap_net_raw+ep /usr/bin/hping3 (or any location of the hping command) setcap command is to set file capabilities. What are filesystem capabilities?    For the purpose of performing permission checks, traditional Unix implementations distinguish two categories of processes: privileged processes (whose effective user ID is 0, referred to as superuser or root), and unprivileged processes (whose effective UID is non-zero). Privileged processes bypass all kernel permission checks, while unprivileged processes are subject to full permission checking based on the process's credentials (usually: effective UID, effective GID, and supplementary group list).  Starting with kernel 2.2, Linux divides the privileges traditionally associated with super
Read more