Skip to main content

System running in low graphics mode (nVidia)


This problem can be occurred at two instances.
1. Fresh installation:
1. Download the driver from nVidia website
2. Copy the file to the disk. (It looks like "NVIDIA-Linux-x86_64-319.17.run", depends on your version)
3. Now just type the following command from terminal:
    sudo sh ./NVIDIA-Linux-x86_64-319.17.run
4. Follow the on-screen instructions and finally reboot.
2. Problem after upgrade:
1. Login into command prompt
2. Run the following command:
    sudo sh ./NVIDIA-Linux-x86_64-319.17.run
3. It will ask to delete previous installation. Accept all the prompts and also the one to edit xconf file.
4. Finally it will reboot and system boots normally.
After successful boot, you can configure your driver in the System>Preferences section.

Other work-arounds:
1. When prompted the low graphics mode, select the "Restart X" option. This will work in some cases. But every time you boot, perform the same.
2. Also try blacklisting "nouveau" (if you find 'nouveau' by running the command 'lsmod'). To do this, type the following command:
    sudo gedit /etc/modprobe.d/blacklist.conf
This will open a document. Add this line at the bottom:
    blacklist nouveau
3. Reboot to get some relief.

Comments

Popular posts from this blog

Reverse Engineering : Extract contents from .img file

Unyaffs is a program to extract files from a YAFFS2 file system image. Currently it can only extract images created by mkyaffs2image. Download the source from here . Compiling : Extract the contents into a suitable place and run the following command make Usage : unyaffs [options] <image_file_name> [<extract_directory>] Options: -d detection of flash layout, no extraction -b spare contains bad block information -c <chunk size> set chunk size in KByte (default: autodetect, max: 16) -s <spare size> set spare size in Byte (default: autodetect, max: 512) -t list image contents -v verbose output -V print version Source: Official github repository

JavaScript - Singleton Pattern

The singleton design pattern is probably the simplest and most common pattern in JavaScript. So why should you use the singleton pattern? Encapsulation of members & functions Creates its own Namespace A singleton is a single instance object Encourages code reuse Improves readability because you can logically organise your code The point of a singleton is to only have one instance. A shopping cart is a good example of something that you may want only a single instance of at one time. The simplest form of Singleton is an object literal. This loose form of Singleton cannot be instantiated. All of the members are now accessible through the Singleton variable, accessible through dot notation. var myCart = {     self: this ,     totalCost: 0,     totalQty: 0,     cart: {},     getCart: function (){ },     updateCart: function (){ } }; alert( "Total cost: ...

Mac Yosemite : Ugly turned out to be Uglier and Ugliest

You might have read my review on Mac OSX Yosemite , The Good, bad and ugly. Now it turned out to be UGLIEST. No more words. Here's the image. If you are on Yosemite, you might be familiar with it. Most of the times, you get stuck on boot logo. I've seen complaints regarding it saying that fellow members are ignorant of it and they deny such possibility, even though many are still facing it. Workarounds suggested by our online friends: Just reboot your mac as many times it takes to your desktop. Boot into safe mode, by holding SHIFT and then reboot. Comment your workaround below, mine is the first one. If you are still on Mavericks, be there till Apple provides a fix for this.