HowTo: NViDIA 185.18 Drivers in Ubuntu

my xserver-xorg and xserver-xorg-core are already the newest version.

another question, what is the relation between lib1-mesa-glx and nvidia driver?
before upgrading the kernel and got the problem, i'd once played around with that package (since an OpenGl game asked to install it).

best regards
ajat.

Quote:

---

Originally Posted by Ajat

my xserver-xorg and xserver-xorg-core are already the newest version.

another question, what is the relation between lib1-mesa-glx and nvidia driver?
before upgrading the kernel and got the problem, i'd once played around with that package (since an OpenGl game asked to install it).

best regards
ajat.

---

lib1-mesa-glx is a free implementation of the OpenGL API.

I am pretty certain that the removal of some files, or a bad symlink is the root cause of this.

Post the output of the following:

Code:

---

ls -l /usr/lib/xorg/modules/extensions

---

edit: also, did you implement the "Keep in sync with kernel updates" section in the guide?
That should stop things going wrong when a new kernel is installed/updated.

Regards
Iain

Quote:

---

Originally Posted by tinivole

You mean that the XGA monitor works just fine? or almost? :)

That was my first attempt at doing such a thing, most of it was educated guessworks. Then a quick script to turn the Hex symbols into binary.

---

Well, to be more specific: the final product was off just a bit. My 'main' monitor (the Viewsonic) usually runs a roster of typical refresh rates (65, 70, 75, 85) just fine. My reference above to the 86hz refresh rate being strange is that there might be something off there somewhere...the driver is working, and I can use the GUI thing to set resolutions, but those resolutions aren't all on-target for the monitor.

If you want to run more script, please do. I'm intrigued by the fact you know how to do that in the first place...

I toyed with xrandr a bit some time back, and it is exactly what I'm hoping for in a 'video controller utility'...I do a bit of video work (typically on the hardware side, not anything really cool...), and something like xrandr would come in very handy from time to time. I'll research that a bit more...

Quote:

---

Originally Posted by rayj

If you want to run more script, please do. I'm intrigued by the fact you know how to do that in the first place...

---

It is something that I am learning at the moment out of self interest. :)
I probably jumped the gun a bit there. You can probably remove them now, along with the bin files and lines in xorg.conf file.

Here is the modeline setup, as I probably should have done from the start:
Make a backup of xorg.conf, and replace the 'Section "Monitor"' section with this:

Code:

---

Section "Monitor"
        Identifier "Monitor0"
        VendorName "NEC"
        ModelName  "Unknown"
        Modeline "1024x768@60" 64.56 1024 1056 1296 1328 768 783 791 807
        Option "DPMS"
EndSection

Section "Monitor"
        Identifier "Monitor1"
        VendorName "VSC"
        ModelName  "Unknown"
        Modeline "1600x1200@77" 256.04 1600 1632 2600 2632 1200 1223 1238 1261
        Option "DPMS"
EndSection

---

And we'll see if that puts things right for both monitors.

There are plenty of places where you can find modeline generators, if you are interested in tweaking the default I've given:
For example: http://xtiming.sourceforge.net/cgi-bin/xtiming.pl

Regards
Iain

Quote:

---

Originally Posted by tinivole

lib1-mesa-glx is a free implementation of the OpenGL API.

I am pretty certain that the removal of some files, or a bad symlink is the root cause of this.

Post the output of the following:

Code:

---

ls -l /usr/lib/xorg/modules/extensions

---

edit: also, did you implement the "Keep in sync with kernel updates" section in the guide?
That should stop things going wrong when a new kernel is installed/updated.

Regards
Iain

---

here is the output

Code:

---

ajat@Storophanthus:~$ ls -l /usr/lib/xorg/modules/extensions
total 1440
-rw-r--r-- 1 root root  17860 2009-04-09 09:14 libdbe.so
-rw-r--r-- 1 root root    9628 2009-04-09 09:14 libdri2.so
-rw-r--r-- 1 root root  34428 2009-04-09 09:14 libdri.so
-rw-r--r-- 1 root root  92276 2009-04-09 09:14 libextmod.so
lrwxrwxrwx 1 root root      19 2009-08-23 15:48 libglx.so -> libglx.so.185.18.31
-rwxr-xr-x 1 root root 1272112 2009-08-23 15:48 libglx.so.185.18.31
-rw-r--r-- 1 root root  26096 2009-04-09 09:14 librecord.so

---

i didn't resync, since the driver didn't work at the first time i installed it.

thanks.

Quote:

---

Originally Posted by Ajat

i didn't resync, since the driver didn't work at the first time i installed it.

thanks.

---

Hmm... looks like we are going to need the nvidia-bug-report then.

When you load up your workstation and it goes into Low Resolution mode.
Select Exit to Console, then login and run:

Code:

---

sudo nvidia-bug-report.sh

---

Let it run and complete, then start X as you usually do from here and attach the file produced (should be a gzip file in your home directory) to your next post. And I will have a look at the whole process of what happens just the loading of X.

Regards
Iain

Quote:

---

Originally Posted by tinivole

And we'll see if that puts things right for both monitors.

There are plenty of places where you can find modeline generators, if you are interested in tweaking the default I've given:
For example: http://xtiming.sourceforge.net/cgi-bin/xtiming.pl

Regards
Iain

---

Well, that worked...except that it somehow only allowed 60hz refresh rates on both monitors. I ran nvidia-xconfig again, and that seemed to work. Until I decide to poke around in there again.

Thanks for all the input. I've learned quite a bit...

Quote:

---

Originally Posted by tinivole

Hmm... looks like we are going to need the nvidia-bug-report then.

When you load up your workstation and it goes into Low Resolution mode.
Select Exit to Console, then login and run:

Code:

---

sudo nvidia-bug-report.sh

---

Let it run and complete, then start X as you usually do from here and attach the file produced (should be a gzip file in your home directory) to your next post. And I will have a look at the whole process of what happens just the loading of X.

Regards
Iain

---

Hi again, the problem is: after i choose exit to console, in just a few seconds,the GUI login screen (i assume that the X start) appears, even before i finish typing my login password. So i don't have any chance to type the command in console login.

This is so strange., after then, on this "second login", my KDE or Gnome works very well (glxgears and compiz got no problem, "glxinfo | grep rendering" also give positive answer) .

best regards

ajat

double post

Quote:

---

Originally Posted by Ajat

Hi again, the problem is: after i choose exit to console, in just a few seconds,the GUI login screen (i assume that the X start) appears, even before i finish typing my login password. So i don't have any chance to type the command in console login.

This is so strange., after then, on this "second login", my KDE or Gnome works very well (glxgears and compiz got no problem, "glxinfo | grep rendering" also give positive answer) .

best regards

ajat

---

Hmm...

An alternate way would be to press Ctrl+Alt+F1
That will allow you to log into the console and capture the data alright.

Then press Ctrl+Alt+F7 to switch back to X, and then select "exit to console" to proceed as normal.

I'll see if I can see anything, but I can't say that I have seen anything like this before...
Have you ever made any changes to startup script? Boot speedup tweaks?

Regards
Iain