Skip to main content

Boot Problems on Slackware64-Current on VM

This morning, i had some time to upgrade my VM machines used only for testing running Slackware-Current and Slackware64-Current to the latest batch of update which upgrades the kernel and GCC to the latest version. While the Slackware-Current (32 bit) works flawlessly, i had some problems with the Slackware64-Current. It won't boot and stopped at initializing TTM.

I asked Pat about this whether there are reports from other people and he replied no, but he came up with a simple solution. Use vga=normal. So i tried once more and this time, i press TAB on LILO prompt and use Linux vga=normal and it boots fine. Later, when i have logged in, i just change the vga = 773 into vga = normal in /etc/lilo.conf and ran /sbin/lilo -v to make it permanent.

Strange thing is that it didn't happen on my 32 bit Slackware-Current VM. Both are plain Slackware{64}-Current machine i used for testing, so they are not filled with any other packages from third party repositories.

Thanks to Patrick Volkerding for the tips :)

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 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 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