PDA

View Full Version : GeForce FX5200 blank screen problem


mbratch
2008-01-22, 06:16 AM CST
I am using the livna driver for the FX5200 (96.43.01). Occasionally when I logout or reboot Fedora 8, I get a blank screen when it resets X. I have to do a hard reboot and hope it comes back. It doesn't always, though, on the first try.

What I found at the tail end of the Xorg log file is this:

(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(WW) NVIDIA(0): WAIT (2, 3, 0x8000, 0x000006e8, 0x00000d60)
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(II) Loading extension NV-GLX

Everything after the first line is unique to the error case. Anyone else ever get this? I'm not sure what causes it. When I first installed the driver, everything worked fine for awhile. Now it's intermittently giving me this problem.

As a side note: where can I find a log on my system showing a history of what's been updated with yum? Maybe some recent update is giving me grief...

Thanks.

Seve
2008-01-22, 06:37 AM CST
Hello:
Have you tried installing the latest 169.07 driver for your card ?

Seve

mbratch
2008-01-22, 07:10 AM CST
Seve -- the 169.07 is not recommended for FX5200. Version 96.43.01 is cited as the latest version for that NVIDIA configuration.

Seve
2008-01-22, 07:18 AM CST
Hello:
Unless I am misreading something, which may be the case, the 169.07 driver is the one you want.
You can confirm it by having a quick read through here .
Appendix A. Supported NVIDIA GPU Products (http://us.download.nvidia.com/XFree86/Linux-x86/169.07/README/appendix-a.html)

Seve

mbratch
2008-01-22, 07:35 AM CST
OK thanks for that link Seve. Anything I had read before said differently, but that doc does indeed seem to indicate that 169.07 supports the FX5200. I can give that a try. Although I am still puzzled why my driver used to work then recently doesn't.

Anyone know how to look at yum update/install history?

mbratch
2008-01-22, 07:00 PM CST
I yum-erased the 96xx driver and installed 169.07. Then X wouldn't start at all. Re-installed 96xx and X starts but back to my intermittent problem where sometimes it just gives the blank screen.

Seve
2008-01-22, 07:32 PM CST
Hello:
You might want to post your issue here : http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14
The forum is monitored by folks from nVidia and they, if anyone will be able to help you.

Seve

mbratch
2008-01-23, 07:17 AM CST
I will give that forum a try. Thanks.

glennzo
2008-01-23, 07:38 AM CST
Trouble with the FX5200 surprises me. I used that card for a few years with Fedora 6 and 7, maybe even 5 and 4. Never had trouble with it until Fedora 8. Is it a case of needing older drivers because the newer ones don't support it properly? It worked well but now it's broken?

linuxpcmancn
2008-01-23, 08:05 AM CST
OK thanks for that link Seve. Anything I had read before said differently, but that doc does indeed seem to indicate that 169.07 supports the FX5200. I can give that a try. Although I am still puzzled why my driver used to work then recently doesn't.

Anyone know how to look at yum update/install history?
hi,
check this file:/var/log/yum.log

mbratch
2008-01-23, 08:15 AM CST
Trouble with the FX5200 surprises me. I used that card for a few years with Fedora 6 and 7, maybe even 5 and 4. Never had trouble with it until Fedora 8. Is it a case of needing older drivers because the newer ones don't support it properly? It worked well but now it's broken?Actually, this worked fine up until a couple of weeks ago, then I mysteriously started having this intermittent problem. It smells alot like some kind of timing problem or something. I'd say it fails 20 or 30% of the time. For example, if I log out or reboot, some event that causes X to reset/restart, I might get this blank screen. Also, interestingly, Ctrl-Alt-F1 doesn't take me to a command line. The screen stays blank. And pressing Ctrl-Alt-Del blindly after the Ctrl-Alt-F1 doesn't reboot. So the system seems pretty messed up somewhere at that point. I have to resort to a hard reset and hope that X restarts properly (20-30% chance it won't -- back to blank screen).

mbratch
2008-01-23, 08:17 AM CST
hi,
check this file:/var/log/yum.log
Excellent. Thanks!

mbratch
2008-01-23, 08:38 AM CST
The only thing that looks suspicious is two versions of a file:

/usr/lib/xorg/modules/extensions/libglx.so
/usr/lib/xorg/modules/extensions/nvidia/libglx.so

Where the second one symbolically links to: /usr/lib/xorg/modules/extensions/nvidia/libglx.so.96.43.01

They are different sizes. Not sure which libglx.so is being picked up. And not sure which one should be picked up.

mbratch
2008-01-24, 10:45 AM CST
Posted at http://www.nvnews.net/vbulletin and drew a complete blank. :-/

mbratch
2008-01-27, 06:08 AM CST
oompah loompah :(

mpie
2008-01-27, 06:19 AM CST
strange mine works fine.

.
/sbin/lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
02:05.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)


yum list nvidia
nstalled Packages
kmod-nvidia.i686 169.07-2.lvn8 installed
kmod-nvidia-2.6.23.14-107.fc8.i686 169.07-2.lvn8 installed
kmod-nvidia-2.6.23.9-85.fc8.i686 169.07-1.lvn8 installed

cavedweller
2008-01-27, 08:05 AM CST
I am using 5200 FX which worked fine with 7 and Debian etch, but with 8 I can only get 1280x1024 ... :(
I prefer 1024x768 as my eyes aren't what they use to be. When I try to reset the resolution I get a blank screen and have to reset to 1280x1024.

cavedweller
2008-01-27, 09:08 AM CST
I did this to install livna ....... rpm -ihv http://rpm.livna.org/livna-release-8.rpm

Then I went here .............. http://www.firewing1.com/content/view/64/36/

and did this :
su -
yum install kmod-nvidia xorg-x11-drv-nvidia
nvidia-config-display enable
service nvidia restart

I tried first to use the default display manager to reset everything, but could only get a refresh rate of 57Hz, not that 3Hz is going to make that much difference, but Nvidia's would let me get at least 60Hz.

Then went to Nvidia Display Settings and changed resolution and refresh rate 1024x768 60Hz and bingo I could see again. :D

When I clicked on "Save to X Configuration File" it wouldn't let me as a normal user so I logged out and back in as root and reset the resolution and refresh rate and saved it. Now login screen and all users are 1024x768 @ 60Hz.

Me and my wife are the only two that use the computer and we are both over 45 so it works for us. I am just dreading the day I have to set the resolution to 800x600. :eek:

sej7278
2008-01-27, 11:56 AM CST
i have no problem with my 5200 under f7, but just tried to replace it with a 6200 and the latest nvidia drivers (or an older one from 2.6.22 days) didn't start at all, and even the "nv" driver wouldn't start on boot until i ran the xconfig program - although the graphical boot worked, and grub, but not the user chooser screen. anyway back to the 5200 now which still works fine even with the new drivers.....

mbratch
2008-01-27, 12:30 PM CST
strange mine works fine.

.
/sbin/lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
02:05.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)


yum list nvidia
nstalled Packages
kmod-nvidia.i686 169.07-2.lvn8 installed
kmod-nvidia-2.6.23.14-107.fc8.i686 169.07-2.lvn8 installed
kmod-nvidia-2.6.23.9-85.fc8.i686 169.07-1.lvn8 installed

Like I said, mine generally works. It's installed correctly as far as I can tell. I just have this intermittent problem of after a log out or reboot it will sometimes give me a blank screen that I can only fix with a reboot and, possibly, re-encounter the same problem after the reboot.

The error messages I showed in the xorg log file occur when I get the problem. Most of the time (as in maybe 65% or so?) it works fine and the log file appears normal.

Some kind of timing problem or something...

mbratch
2008-01-28, 05:49 AM CST
Just as a comparison, here's the Xorg log after failure:

...(bunch of stuff that is dumped in any case)...

(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(WW) NVIDIA(0): WAIT (2, 3, 0x8000, 0x000006e8, 0x00000d60)
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(EE) NVIDIA(0): Error recovery failed.
(EE) NVIDIA(0): *** Aborting ***
(II) Loading extension NV-GLX

And here it is in a success case:

...(bunch of stuff that is dumped in any case)...

(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us+inet"
(**) Keyboard0: XkbLayout: "us+inet"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: Core Pointer
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(**) <default pointer>: Sensitivity: 1
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
AUDIT: Mon Jan 28 06:34:28 2008: 12772 X: client 1 rejected from local host (uid 500)

mbratch
2008-01-29, 07:53 AM CST
Ain't we got fun?

mbratch
2008-02-04, 07:18 AM CST
Well, finally got in touch with someone at the NVIDIA site. Posted the NVIDIA debug log, etc. They said they don't support the Livna driver at all. :(

They suggested I try the latest 169.09 driver, so I went through and uninstalled the Livna and installed 169.09. As with 169.07, X would not even start up. Sent the log to NVIDIA and they said not enough info to debug the problem. Started down a path of "try this and try that"... no joy yet.

ryptyde
2008-02-04, 05:32 PM CST
I have the GeForce FX 5200 pci 256 MB card and haven't experienced any drastic misbehavior as you have but did have a problem with desktop effects recently. The latest nVidia driver seems to be working ok and here's a shot running it with compiz-fusion-icon.

mbratch
2008-02-04, 09:18 PM CST
I'm glad to hear a couple of people are having no trouble with the NVIDIA driver for FX 5200.

Alas, mine still has issues. :-/