After working around with this error, I found where everything just began. It's because when you building a new module for vmblock, it will do create_proc_entry() removal in favor of proc_create(). So I decide to share with you, how to deal with this new kernel. So you can use your VMWare again. Yay!
1. Open your terminal (you can use terminator, or gnome-terminal, or xterm, or whatever your flavor)
2. Make sure you've installed linux-headers-3.10-3-amd64 and linux-headers-3.10-3-common
If you're not sure, type this on your terminal:
Command :
root@kali:~# apt-get install linux-headers-3.10-3-amd64 linux-headers-3.10-3-common
3. Stop vmware service by typing this command on your terminal
Command :
root@kali:~# service vmware stop
4. Download patches to patch your old vmware source (WARNING: IF YOU PATCH YOUR VMWARE SOURCE, IT MIGHT NOT WORK ANYMORE WITH YOUR OLDER KERNEL. DO WITH YOUR OWN RISK!)
a. Patch for vmnet source
Command :
root@kali:~# cd /tmp/ ; curl -O http://download1504.mediafire.com/1hjabvhjhhmg/p01zil23et23p16/vmnet-9.0.2-5.0.2-3.10.patch
b. Patch for vmblock source
Command :
root@kali:~# cd /tmp/ ; curl -O http://download1338.mediafire.com/cchmnk8dnyog/iqff11seyebt0bd/vmblock-9.0.2-5.0.2-3.10.patch
5. Patch your old vmware source
Command :
root@kali:~# cd /usr/lib/vmware/modules/source
root@kali:~# tar -xvf vmblock.tar
root@kali:~# tar -xvf vmnet.tar
root@kali:~# patch -p0 -i /tmp/vmblock-9.0.2-5.0.2-3.10.patch
root@kali:~# patch -p0 -i /tmp/vmnet-9.0.2-5.0.2-3.10.patch
root@kali:~# tar -cf vmblock.tar vmblock-only
root@kali:~# tar -cf vmnet.tar vmnet-only
root@kali:~# rm -r vmblock-only
root@kali:~# rm -r vmnet-only
6. Reinstall your new vmware modules
Command :
root@kali:~# vmware-modconfig --console --install-all
That's it! Enjoy your VMWare on your new kernel!
0 comment:
Post a Comment