[hardy] nv crashes after a while

Ok, so you didn't perform a fresh install? Just run 'dpkg-reconfigure -phigh xserver-xorg' to regenerate the xorg.conf.

Timo, I have been comfortable at the command line since I got my first PC --- an Osborne 1a --- back in 1982. I would have been happy to manually edit the xorg.conf. However, if Ubuntu aims to serve newcomers to Linux, such a problem should be addressed.

A further problem has arisen: xorg is complaining that it cannot find the glx extension in order to run the proprietary nvidia driver. I have not yet found documentation how to change the driver back to the "non-tainting" nv driver. I have rebooted into Gutsy in order to access Launchpad. When I am next in Hardy, I shall check the xorg manpage.

This is another example why one should not use alpha releases in production environments. Fortunately, there is a Gutsy installation on the same computer.

I am attaching an Xorg.0.log from the Hardy session.

Returning to the original point of this bug report, would appreciate your verifying with Dell Ubuntu support team how to identify and configure correctly this monitor which does not return an EDID value.

That log was with the nv driver, if you wish to use the binary one please use the new "driver manager" which should configure things correctly.

Looking at the log, it shows correct values for the monitor:

(II) NV(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 170 MHz
...
(II) NV(0): Configured Monitor: Using hsync range of 30.00-81.00 kHz
(II) NV(0): Configured Monitor: Using vrefresh range of 56.00-76.00 Hz
(II) NV(0): Configured Monitor: Using maximum pixel clock of 170.00 MHz
(II) NV(0): Estimated virtual size for aspect ratio 1.5758 is 1920x1200

and it should be using the right resolution as well, so I'm not sure where the bug is?

As I mentioned in comments to the report on the related Bug 190378, several weeks ago I had used nvidia-xconfig in an attempt to enable the proprietary driver. That might be the source of the bad settings for my monitor.

However, until I can figure out why X is crashing using the "non-tainted" nv driver, I do not have access to X in Hardy.

Please see the attachments to Bug 190381.

Following up on your first comment about "not doing a fresh install" and the possibility that the use of nvidia-xconfig might have added to the problems, I did a reinstall of hardy using the latest (Alpha 4) CD.

I continue to have a problem with X loading but then crashing after about 20-30 secs.

An Xorg.0.log is attached.

Ok, now we are talking ;)

Does the nv-driver work fine with gutsy?

I have always used the "nvidia" driver with Gutsy, but will switch to "nv" and report back to you. If there are no instant problems, I will use the "nv" driver for several hours and then report.

Thanks for the reply.

nv did not work with gutsy. xorg.conf and logs attached.

Hardy wont recognize 01:01.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)
on boot, I need to dpkg-reconfigure xserver-xorg to fix issue...

Bruce, remove the UseFbDev option, it should work then.

Bruce, any luck dropping the UseFbDev option?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!