Black Screen with GeForce FX 5600

bogusiano · 01-02-04, 03:26 AM

Hi:

I installed the drivers: NVIDIA-Linux-x86-1.0-5328 succesfully. Then I changed the configuration file /etc/X11/XF86Config so it will use the "nvidia" driver, I activated the glx module and I added the Option "NvAGP" "1".

The problem is when I start running X, the log does not give any error, but the screen at tty7 goes black and thats it, if I swap screen to ttyX where I gave the command startx it gives me the following error:

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.

Plz help!

Thanx!

whig · 01-03-04, 10:58 PM

There's got to be some telling errors somewhere in the logs.

startx > x-error.log 2>&1

bogusiano · 01-05-04, 01:32 PM

The command printed this file:

X: warning; process set to priority -11 instead of requested priority -10

This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org. Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.0.1 (Debian 4.3.0-0pre1v4 20031024231956 aigarius@namatevs.lv)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.22 i686 [ELF]
Build Date: 25 October 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002 T
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 5 07:25:49 2004
(==) Using config file: "/etc/X11/XF86Config"
Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"

after 0 requests (0 known processed) with 0 events remaining.

It is the same error that I find when I change to the screen where I executed the startx.

Any ideas?

bogusiano · 01-05-04, 01:37 PM

I don`t know why the log of X, was not posted on my first message, here it goes.

whig · 01-05-04, 06:38 PM

The logs just end, without telling much - darn. I have only one guess and it is a long shot: like me, you have a VIA chipset which just doesn't work with version 5328. So go back a release.

One more thing: try using <"Driver" "vesa"> and <"Driver" "nv"> to see if X even works again.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[9800gt] Xorg black screen after installing nvidia driver	HacKurx	NVIDIA Linux	1	06-07-12 01:29 PM
Nvidia GeForce 301.42 WHQL drivers	DSC	NVIDIA Windows Graphics Drivers	5	05-29-12 10:12 PM
Black screen after switching between graphical virtual consoles five times	rrr-wtf	NVIDIA Linux	1	05-21-12 04:40 PM
New GPU from Nvidia Announced Today, the GeForce GTX 670	News	Latest Tech And Game Headlines	0	05-10-12 01:50 PM
Gainward Unleashes the Sexy GeForce GTX 670 Phantom Graphics Card, Also launches the	News	Latest Tech And Game Headlines	0	05-10-12 09:28 AM

01-02-04, 03:26 AM	#1
bogusiano Registered User Join Date: Jan 2004 Posts: 3	Black Screen with GeForce FX 5600 Hi: I installed the drivers: NVIDIA-Linux-x86-1.0-5328 succesfully. Then I changed the configuration file /etc/X11/XF86Config so it will use the "nvidia" driver, I activated the glx module and I added the Option "NvAGP" "1". The problem is when I start running X, the log does not give any error, but the screen at tty7 goes black and thats it, if I swap screen to ttyX where I gave the command startx it gives me the following error: XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. Plz help! Thanx!

01-03-04, 10:58 PM	#2
whig 550Ti Join Date: Jan 2004 Location: New Zealand Posts: 854	There's got to be some telling errors somewhere in the logs. startx > x-error.log 2>&1

01-05-04, 01:32 PM	#3
bogusiano Registered User Join Date: Jan 2004 Posts: 3	The command printed this file: X: warning; process set to priority -11 instead of requested priority -10 This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to fixes@XFree86.Org. Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.0.1 (Debian 4.3.0-0pre1v4 20031024231956 aigarius@namatevs.lv) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.22 i686 [ELF] Build Date: 25 October 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002 T Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 5 07:25:49 2004 (==) Using config file: "/etc/X11/XF86Config" Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. It is the same error that I find when I change to the screen where I executed the startx. Any ideas?

01-05-04, 06:38 PM	#5
whig 550Ti Join Date: Jan 2004 Location: New Zealand Posts: 854	The logs just end, without telling much - darn. I have only one guess and it is a long shot: like me, you have a VIA chipset which just doesn't work with version 5328. So go back a release. One more thing: try using <"Driver" "vesa"> and <"Driver" "nv"> to see if X even works again.