Ubuntu, screen resolution and graphic cards, well....it is still kind of complicated

I have spent most of my life in front of computers. 20 years later, Things on Ubuntu still scare me. I can only imagine what it must be like for a complete novice computer user. That would be a sadistic joke, put an Ubuntu machine in front of them.

Anyway, I had some issues with screen resolution again. This time I just wanted to increase my dual monitor resolution from 1280x800 to 1600x1024. Somehow, between nvidia and xorg; it won't let me keep my settings. Not just that, one monitor is fine...the other is not so fine. The only difference between the dual monitors. I am using a Nvidia 5300 on one and a 5200 on another. Same monitors.

EPIC FAIL!!!

Here is my post on Ubuntu. Maybe, in 5-6 years this will get fixed.

hey should have Mensa/GRE/College entrance exams and have a question, "How do you set your screen resolution on Ubuntu"

Anyway, I am having trouble setting my screen resolution and I had it working fine, now I going nuts trying to increase it.

Dual Monitor My setup:
OS: Ubuntu 7.10
Cards: Nvidia 5300 and 5200.
Monitors: Acer 20inches max res at 1680x1050.

What I had orginally (this worked fine for several months)
Resolution in xorg.conf: 1280x800.

This resolution worked fine but then I decided to increase my resolution to the preferred LCD settings, closer to 1680x1050.

I open nvidia-settings.

sudo nvidia-settings.

It has the resolutions:

1600x1024. I click on both of those monitors and set the resolutions. Everything works fine. I say overwrite my xorg.conf. So far, everything looks good.

But, when I logout or reboot, it doesn't keep the setting? It sets one monitor to 1280x800 and the other to 1600x1024? Where would it keep that setting?

A bug?

-----

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce PCX 5300"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5200"
BusID "PCI:5:9:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "1600x1024 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "1600x1024 +0+0"
SubSection "Display"
Depth 24
EndSubSection

-----------------

Edited: Ok, I think I figured out my screen resolution issues. Apparently there are 15,000 ways to configure the resolution: 1. nvidia-settings. 2. xorg.conf. 3. gnome resolution screen settings 4. the graphics and screen settings? wtf?

But I still don't know which one is the default. Also, which one setting has priority.

Comments

Post a Comment

Popular posts from this blog

Is Java the new COBOL? Yes. What does that mean, exactly? (Part 1)

Image
"If you want to know the past, look at your present. If you want to know the future, look at your present." -- Gautama Buddha Java is the new COBOL, whaaaat?     If you are software developer that mainly writes applications for the web; even if you aren't a Java/J2EE developer, you have probably heard the new meme circulating the web and blogosphere. "Java is the new COBOL" . Most blogs and technical writers regurgitate that statement and follow-up by saying that EJBs suck, and some companies are considering Ruby on Rails. I didn't really think much of these posts. I get the impression that a lot of these "managers" don't write any Java or COBOL code. They are really not highlighting the seriousness of the problem. COBOL development has remained stagnant for decades. Java may see the same problem in the future. The Pentagon/DOD has a trillion dollar COBOL problem because it is so difficult to change their ancient infrastructure. Anyon
Read more

On Unit Testing, Java TDD for developers to write

It has been a while, let's kick off 2017 with a blog entry. I have read and I am reading about four or five posts a day about unit testing. It really has been a long time obsession for me. I have moved past the technical and practical considerations on unit testing frameworks and done with the debates with "should you use Junit or Mockito or Karma?" I am more interested in the psychology of unit testing, who does it, likes it, hates it? It really is one of those easy to learn, hard to master concepts. For example, many many may play chess when they are young and can end up being horribly chess players most of their life, I am part of that majority. Unfortunately, I have never played chess and sat down for hours and tried to master it. I never see the common patterns or have a developed end game. I mostly just play with a knowledge of the basic rules. Following good unit testing practices within your software development shop is a lot like playing chess. It is easy to le
Read more

JVM Notebook: Basic Clojure, Java and JVM Language performance

Image
"Measure, don't guess. The primary goal of all performance tuning exercises should be maximize the end user experience given the resource constraints." [1] "It isn't so much a "farewell to the J" as an expansion of the platform opportunities Java provides. Sun's investment to power ongoing development of JRuby and Jython broadens the range and reach of Java, as a whole." -- Rick Ross Overview and JVM Languages    One of the exciting trends to recently emerge from the Java community is the concept of the JVM language. These technologies are all that you would expect them to be. They are implementations of languages that run on the Java Virtual Machine. Some are newly created and some are based on existing, more mature languages. JRuby, Jython are two JVM languages based on CRuby and CPython. Groovy, Scala, Clojure are three completely new JVM languages that were created to add new language features that weren't supported by the core Ja
Read more