Skip to main content

Stay Away From VMWare Workstation 9 For Now

You heard the news that VMWare Workstation 9 has been release with it's all new features mentioned on the release notes. It has Windows 8 support, Graphics improvements, OpenGL support for the guest OS, USB 3.0 support, Nested virtualizations, Restricted virtual machines, and many other goodies that might seduce you to upgrade to this version.

Unfortunately, it also came with some known issues that most people didn't read at the bottom of the page. One of the primary issues is that it doesn't work well with Linux Kernel 3.5 because of the changes in the kernel main tree that affects how VMWare works. Some of the comments i received regarding VMWare Workstations 9 stated that it caused their system to crash.

On my system, i tried to upgrade to VMWare Workstation 9 by performing the same steps i have done previously like removing the old configuration and executables files, install it with --ignore-errors parameters, and patching it. It turns out that VMWare Workstation 9 only need 1 patch to be able to work with Linux Kernel 3.5 and that patch is now uploaded to my SlackHacks repository.

Note: The patch is believed to solve the problems by many people according to the original discussion here, but not in my case. I still can't start my Virtual Machine due to stack trace flooding my system whenever i tried to start it.

Looks like i would wait for the next build release that hopefully have a permanent fix over this problems. For now, it's better to stay away from VMWare Workstation 9 until VMWare release another release to fix this problem

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue