X problems persist...

gatep5 · 01-28-04, 04:24 AM

Ok, X will come up eventually but it takes about 5 minutes for the login screen to appear. I have tried all the suggestions on other posts to no avail. Here are my specs.

Fedora Core 1
ABIT k7g (via chipset)
AMD 1600+
Kernel 2.4.22-1.2149.ntpl

I get a blank screen for about 5 or 6 minutes when trying to load X and eventually it will come up. My XFree86.0.log file did not yeild any error messages, nor could I find any error messages in any of the other log files. Anyway know what to do? Should I try upgrading to the test 2.6.1 kernel from the fedora website? Thanks in advance!

Keith

whig · 01-28-04, 09:34 PM

Find out what exactly is holding things up. Shut down to the console and type startx. Is it quick? Also try disabling any fancy graphic boot up pictures in favour of watching your services load one by one. Does your distro have a failsafe boot option - that would help. It may just be your PC is looking for a DHCP server to set your network card.

gatep5 · 01-29-04, 09:36 AM

I have been booting into runlevel 3 anyway because I have always had problems trying to get the Nvidia drivers to work under linux. So, in other words, I am running startx from the command-line. By this time it is way past all my services starting up (especially the network initialization). So, I still don't have an answer to what is going on because my log file for X doesn't provide any error messages. I guess I need to try the IgnoreXXXX command that other people have suggested. I think that the drivers might be looking for an DVI monitor or TV. Anyway, once you can get the drivers to work, they work great, but I should not have to wait almost 5 minutes for X to come up. FIX THIS STUFF NVIDIA!!!!!!!!!!!!

Andy Mecham · 01-29-04, 03:14 PM

From the README:

Q: X takes a long time to start (possibly several minutes). What can
I do?

A: Most of the startx delay problems we have found are caused by incorrect
data in video BIOSes about what display devices are possibly connected
or what i2c port should be used for detection. You can work around
these problems with the XF86Config option "IgnoreDisplayDevices"
(please see the description in (app-d) APPENDIX D: XF86CONFIG OPTIONS).

--andy

01-28-04, 04:24 AM	#1
gatep5 Registered User Join Date: Jan 2004 Posts: 2	X problems persist... Ok, X will come up eventually but it takes about 5 minutes for the login screen to appear. I have tried all the suggestions on other posts to no avail. Here are my specs. Fedora Core 1 ABIT k7g (via chipset) AMD 1600+ Kernel 2.4.22-1.2149.ntpl I get a blank screen for about 5 or 6 minutes when trying to load X and eventually it will come up. My XFree86.0.log file did not yeild any error messages, nor could I find any error messages in any of the other log files. Anyway know what to do? Should I try upgrading to the test 2.6.1 kernel from the fedora website? Thanks in advance! Keith

01-29-04, 09:36 AM	#3
gatep5 Registered User Join Date: Jan 2004 Posts: 2	No, I'm sure that that is not it... I have been booting into runlevel 3 anyway because I have always had problems trying to get the Nvidia drivers to work under linux. So, in other words, I am running startx from the command-line. By this time it is way past all my services starting up (especially the network initialization). So, I still don't have an answer to what is going on because my log file for X doesn't provide any error messages. I guess I need to try the IgnoreXXXX command that other people have suggested. I think that the drivers might be looking for an DVI monitor or TV. Anyway, once you can get the drivers to work, they work great, but I should not have to wait almost 5 minutes for X to come up. FIX THIS STUFF NVIDIA!!!!!!!!!!!!

01-29-04, 03:14 PM	#4
Andy Mecham l33t master Join Date: Jul 2002 Location: Santa Clara, CA Posts: 1,163	From the README: Q: X takes a long time to start (possibly several minutes). What can I do? A: Most of the startx delay problems we have found are caused by incorrect data in video BIOSes about what display devices are possibly connected or what i2c port should be used for detection. You can work around these problems with the XF86Config option "IgnoreDisplayDevices" (please see the description in (app-d) APPENDIX D: XF86CONFIG OPTIONS). --andy __________________ Andy Mecham NVIDIA Corporation

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
problems with drivers after 295.40 (OpenSuSE 12.1, GeFroce 7900 GS, Phenom II X4)	alawa	NVIDIA Linux	0	06-09-12 06:37 PM
Problems with drivers	fforw	NVIDIA Linux	7	10-11-02 07:06 PM
Nvidia Problems in Slackware 8.1	xtreme	NVIDIA Linux	3	10-01-02 12:03 PM
F1 2002 problems with driver 40.41	arutten	NVIDIA Windows Graphics Drivers	6	10-01-02 07:07 AM
DirectX 8 problems with GeForce4	Derwin	NVIDIA GeForce 7, 8, And 9 Series	19	08-20-02 01:23 AM

01-28-04, 09:34 PM	#2
whig 550Ti Join Date: Jan 2004 Location: New Zealand Posts: 854	Find out what exactly is holding things up. Shut down to the console and type startx. Is it quick? Also try disabling any fancy graphic boot up pictures in favour of watching your services load one by one. Does your distro have a failsafe boot option - that would help. It may just be your PC is looking for a DHCP server to set your network card.