Skip to main content

PAE Support on VirtualBox

This morning, i decided to upgrade one of my virtual machine running Slackware 13.37 into -Current. I started by editing /etc/slackpkg/mirrors and switch to Slackware-Current tree and i start updating by issuing

slackpkg update
slackpkg upgrade-all


I skipped slackpkg install-new since there are no new packages yet at this moment. I also installed the new kernel, 2.6.38.7 on this virtual machine.

Once i make sure everything is properly set up, i restarted the machine (it has been running for about 34 days non stop), and waited until it boots. Since it's a headless system, i have no interaction until the OpenSSH daemon is started and then i can login to that system. On my case, after waiting for 20 seconds or so, i tried to connect to the system, but i have no login prompt. I waited another 10 seconds and still no responds.

At this time, i realize there is a problem with the new kernel, so i fired up KRDC and loggin using VRDE extension on the VirtualBox and i saw that it requires PAE support on VirtualBox. I haven't enabled this when i set up this virtual machine, so i had to enable it in order to make it bootable again since the new kernel configuration in Slackware-Current enables HIGHMEM64G support which also enables PAE automatically.

So i shut down the virtual machine and i issued:
VBoxManage modifyvm SlackVM2 --pae on
This enables PAE support and afterwards, it boots normally again Yahoo

I hope you will take notice when you decided to move on to -Current using VirtualBox Goodluck

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