modules

Nvidia Driver on Linux – Easy, and Quick

Image representing NVidia as depicted in Crunc...
Image via CrunchBase

There is a buzz that installing the Linux based Nvidia accelerated graphics driver is complicated. I consider it rather straight forward. First install build-essential, and the headers for your kernel. Those may appear to be some bigs words in the previous sentence, but it is really one line in a terminal window. Build essential installs GCC and its dependencies:

sudo apt-get install build-essential linux-headers-$(uname -r)

Now download the latest and greatest Nvidia driver. Choose the correct build type for your architecture. Conveniently save the file to your desktop and rename it to nvidia.run. The change your tty to another. To change to tty2 press control-alt f2.

Shut down gdm, which will stop X11:

sudo /etc/init.d/gdm stop

Or if you are using the new process manager in Ubuntu 9.10 you can use also:

sudo service gdm stop

Then execute the Nvidia installation script. Login to the command prompt and navigate to the desktop:

cd Desktop
sudo sh nvidia.run

Basically answer yes to everything, let the driver compile, and then when it asks you to configure the xorg.conf file, let it. Nowadays the Nvidia driver basically works out of the box. In the past, with Ubuntu in particular, you had to comment out the included driver in Ubuntu’s modules package, otherwise the custom compiled driver would not load on startup. The open source driver used to be commented out in /etc/default/linux-restricted-modules-common (comment NV); note that this is not needed any more except in Hardy (8.04).

Then start your gdm session, which will take you back to the login window, or your desktop depending on your startup settings:

sudo /etc/init.d/gdm start

Reblog this post [with Zemanta]

VirtualBox 2.6.26 Kernel Support

With Debian Lenny you can update to the 2.6.26 kernel, but in VirtualBox support for this version is not ready. A kernel panic will not allow the system to boot into a stable state, therefore for the time being users must retain use of 2.6.24. One major drawback is that there are no headers for the 2.6.24 kernel in Lenny. This forces VirtualBox users to wait to install guest additions, thus slightly decreasing stability because of the timing benifits associated with the VirtualBox kernel modules. Overall because of this it is most likely best to still use Etch until Lenny progresses a bit further, specifically including some needed kernel headers or VirtualBox provides an update for better support of the 2.6.26 kernel.

Ndiswrapper – Ubuntu WiFi in 4 Easy Steps

First download Ndiswrapper:

1) http://ndiswrapper.sourceforge.net/joomla/

Then install your kernel headers and compilation packages:

2) sudo apt-get install build-essential

Unzip the ndiswrapper package. Navigate to the folder and issue:

3) make

Then issue:

4) sudo make install

Your done. Add Ndiswrapper to autostart on boot:

sudo nano /etc/modules

Add ndiswrapper to the bottom of the list. And blacklist any conflicting drivers (my conflict was bcm43xx) to prevent conflict:

sudo nano /etc/modprobe.d/blacklist

Add “blacklist bcm43xx” in my case, to the bottom of the list.

Now add your windows module to ndiswrapper. Windows drivers are .inf files. A typical Windows driver is bcmwl5.inf:

sudo ndiswrapper -i bcmwl5.inf

You can extract drivers from exe files using “cabextract”. Install cabextract using apt-get then issue:

cabextract drivers.exe

This will unzip the exe to the current directory of the terminal window. You may want to place the exe file in a new folder to prevent making a mess.

Just type ndiswrapper at a terminal prompt to see other options the binary allows. Also for a graphical frontend use ndisgtk.

Instantly load the ndiswrapper module to get your WiFi working without rebooting:

sudo rmmod ndiswrapper && sudo modprobe ndiswrapper

Now, could this be any easier :) Send a comment if your having trouble :(

Reblog this post [with Zemanta]