Skip to main content

Linux Kernel 3.0.1 and VMWare Patch

Last night, i attempted to build my first Linux Kernel 3.0.1 on my desktop at home. This is my third attempt on Linux Kernel 3.0 build after the previous two attempts on my workstation ended with a kernel panic message even though i follows the standard procedure i used to do in the past. Probably a misconfiguration problem. This time, i tried a different method. I build the kernel as much the same with the one i used in Linux Kernel 2.6.39, so i minimized the changes. In most questions answered, i pick N(o) as the answer, except for the RTC (Real Time Clock) which happened to be needed for Linux Kernel 3.0.x to build.

Since i have work to do last night, i didn't have time to reboot the computer, so i went to bed afterwards. This morning, i woke up and tried to reboot the machine and it boots back normally when i picked Linux-3.0.1. I was so happy and after logged in, i reinstalled my VirtualBox (stayed with 4.0.12 since having issues with 4.1 for now) and NVidia drivers (upgraded to 280.13). All went well and the last thing to do is to find VMWare patch for Linux Kernel 3.0.x branch.

So far, the only patch i could found is located on this blog. There are several versions of the patch, but the one working on my machine is patch version 3. Since this patch is a well-refined patch for Linux Kernel 2.6.39, you will have some FAILED message while patching if you have previously patched your VMWare source against Linux Kernel 2.6.39, but that's fine.

After patching it, you can try to run this command to recompile VMWare on your terminal
vmware-modconfig --icon="vmware-workstation" --appname="vmware"
This is on my machine
willysr@desktop:~$ uname -a

Linux desktop 3.0.1-smp #2 SMP Mon Aug 8 21:26:31 WIT 2011 i686 Pentium(R)
Dual-Core CPU E5300 @ 2.60GHz GenuineIntel GNU/Linux

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