<html>
<body>
At 04:00 PM 09/10/10, you wrote:<br><br>
<br><br>
<blockquote type=cite class=cite cite="">
<blockquote type=cite class=cite cite=""><b>$ sudo apt-get install
nvidia-settings<br>
[it may already be installed, but if not - install it]<br><br>
$ sudo nvidia-xconfig<br><br>
Now reboot<br><br>
</b>I got through the first 3 steps of this procedure and ended up with a
screen saying "unsupported mode" in a box.<br>
I had to shut the computer down ungracefully, run it up with the
CD, edit the xorg.conf file <br>
</blockquote><br>
Now an update to all this, the main problem I have now once the nvidia
driver is installed and xorg.conf is configured, <br><br>
IF I CAN GET PAST THE PASSWORD SCREEN WITHOUT SEEING WHAT I'M DOING then
the monitor comes to life and works fine.<br>
(I was able to do this once). <br><br>
It still looks like the monitor isn't being identified, and that's the
real problem.<br><br>
I hooked up a brand new out of the box Dell 2007FP monitor with the same
results and it still wasn't showing up in the xorg.conf file. <br>
The graphics card seems to be guessing as to what's connected, and
setting things up incorrectly.<br><br>
It looks like a default mode is stored somewhere, and until the xorg.conf
file is run then that mode is in operation. I would guess that the v sync
is too high.<br>
Without a scope I can't tell for sure.<br><br>
I'm thinking it's now time for a bug report?? <br><br>
Vic<br>
</blockquote><br>
In addition to the above, I found that I had to edit the xorg.conf file
and change the vertical refresh rates <br>
to match the rate that manufacturer says changing the maximum rate for
the maximum display size that the<br>
monitor supports In my case 1600x1200 is a 60Hz rate. I also edited
the Horiz rate to match the monitor I have. <br>
So below is the lines I edited in bold...<br><br>
Section "Monitor"<br>
Identifier
"Monitor0"<br>
VendorName
"Unknown"<br>
ModelName
"CRT-0"<br>
<b> HorizSync 30.0 -
110.0 from this to<br>
HorizSync
30.0 - 81.0<br><br>
VertRefresh 50.0 - 150.0
from this to<br>
VertRefresh 50.0 - 60.0<br>
</b>
Option
"DPMS"<br>
EndSection<br><br>
Section "Device"<br>
Identifier
"Device0"<br>
Driver
"nvidia"<br>
VendorName "NVIDIA
Corporation"<br>
BoardName "GeForce4
MX 440 with AGP8X"<br>
EndSection<br><br>
Section "Screen"<br>
Identifier
"Screen0"<br>
Device
"Device0"<br>
Monitor
"Monitor0"<br>
DefaultDepth 24<br>
Option
"TwinView" "0"<br>
Option
"TwinViewXineramaInfoOrder" "CRT-0"<br>
Option
"metamodes" "1600x1200 +0+0; 1280x1024 +0+0; 1024x768
+0+0; 800x600 +0+0; 640x480 +0+0; 1280x1024_60 +0+0"<br>
SubSection
"Display"<br>
Depth 24<br>
EndSubSection<br>
EndSection<br><br>
<b>In my case, the above <u>had</u> to be done before re-boot, and after
running <br>
$sudo nvidia-xconfig<br><br>
</b>I didn't do that, so I had to run ubuntu from the CD, editing the
xorg.conf file from there<br><br>
So in conclusion, NoOP thanks very much for the vital information to get
me on the right track. The driver has always been o/k and the right one
for the card.<br><br>
I hope this helps others with the same problem, obviously by the various
posts, this is a common problem, <br>
and I agree with Michael Haney that this problem limits the adoption and
use of Ubuntu, at least if did for me. <br><br>
Another issue in this whole thing is that I'm using a usb KVM, and that
might have hindered the recognition of the monitor (I'm not sure about
that)<br><br>
Vic</body>
</html>