nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   1.0.9629 reverting to legacy pci mode (?); no glxgears (http://www.nvnews.net/vbulletin/showthread.php?t=80451)

parish_d 11-15-06 12:11 PM

1.0.9629 reverting to legacy pci mode (?); no glxgears
 
1 Attachment(s)
I appeared to have installed 1.0.9629 successfully into Fedora Core 6 (2.6.18.2) using the nvidia installer. The card is a GeForce FX 5700LE installed on a DFI Lanparty NFII Ultra B motherboard with an Athlon 2500+ processor. I've read about similar issues here and experimented with the various suggestions to no avail.

Starting X initially causes a black screen, but switching to a virtual terminal and back (CTRL-ALT-F1, CTRL-ALT-F7) results in the X session becoming visible. Looking at the x log at this point indicates that the driver has encountered errors and reverted to legacy PCI mode. When attempting to run glxgears, it aborts without ever drawing anything.

Other observations:
- Same behaviour observed with version 1.0.8776
- Disabling selinux does not resolve the problem.
- Cannot switch between modes with CTRL-ALT-+

I have started x with the command startx -- -logverbose 6 and then generated an nvidia-bug-report.log, which is attached here.

Suggestions appreciated.

Daniel

netllama 11-15-06 12:43 PM

Re: 1.0.9629 reverting to legacy pci mode (?); no glxgears
 
It looks like you're hitting two different problems. Here is the first:
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0

That may be why nothing is initially displayed, although its not clear. Further on, you're hitting the 2nd problem:
(II) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to
(II) NVIDIA(0): recover...
(II) NVIDIA(0): CRT-0 assigned CRTC 0
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
(II) NVIDIA(0): allocating video overlay
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to
(II) NVIDIA(0): recover...
(WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors. Falling
(WW) NVIDIA(0): back to legacy PCI mode.

I have a few questions:
0) Were these problems not present with older NVIDIA drivers, or FC5 ?
1) Does the 2nd problem also exist with an official FC6 kernel?
2) Have you verified that you're using the latest BIOS for the motherboard?
3) If you set NvAGP to 0 in xorg.conf, does that have any impact?

Thanks,
Lonni

parish_d 11-15-06 01:39 PM

Re: 1.0.9629 reverting to legacy pci mode (?); no glxgears
 
Lonni,

Setting NvAGP to 0 in xorg.conf solved the problem with the initial blank screen and glxgears. I read some earlier posts where you suggested that option and thought I tried it, but apparently not. I am still unable to cycle through the resolutions using CTRL-ALT-+, but this is not critical and I'll look into it a bit myself before asking you for more help.

Thank you very much for your quick response!

Daniel

parish_d 11-16-06 01:55 PM

Re: 1.0.9629 reverting to legacy pci mode (?); no glxgears
 
As I mentioned above, I'm up and running now, but I looked into a few of your questions in case it can be of use to someone:

>It looks like you're hitting two different problems. Here is the first:
>(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
>0) Were these problems not present with older NVIDIA drivers, or FC5 ?

This error is present on this exact system using 8776 in FC5 as well as on my other FC5 system (Asus M2N32-SLI/Athlon64 X2, Asus 7600GT graphics) using 8776, but has never seemed to be a problem. I noticed in another thread that you asked if someone's monitor was connected directly to the graphics card; in my case it is not, it is routed through an Iogear 2-port KVM switch; I'll try a direct connection later and see what happens.

>(II) NVIDIA(0): Unable to get display device enabled on this X screen; not
>(II) NVIDIA(0): allocating video overlay
>0) Were these problems not present with older NVIDIA drivers, or FC5 ?

This error is present on this exact system using 8776 in FC5 where it was also corrected by your suggestion to set the NvAGP option. The error is not present on the other FC5 system (Asus M2N32-SLI/Athlon64 X2, Asus 7600GT graphics) where it works without the NvAGP setting.

>1) Does the 2nd problem also exist with an official FC6 kernel?

I had installed an official FC6 kernel with the appropriate version-matched nvidia module from livna. X came up, so I think the error is not there, but the session was otherwise poorly behaved, primarily an unresponsive mouse, so I went back to my home-grown kernel and your installer script. I neglected to check if glx was working.

>2) Have you verified that you're using the latest BIOS for the motherboard?

The BIOS is not the latest.

>3) If you set NvAGP to 0 in xorg.conf, does that have any impact?

This fixed the problem in FC5 for both the current and a previous version of the driver.

Thanks again.

Daniel


All times are GMT -5. The time now is 05:26 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.