[lug] VC to X in 2 minutes 42 seconds

[McIllece, Matthew W]

> When I do a simple "xinit" from a virtual console, it consistently takes 2
> minutes and 42 seconds for the X desktop to show up.  This seems like an
> unreasonable amount of time just to start the X server, and I remember a
> time months ago when it only took about 5-10 seconds to start X.  I
> imagine I did something that caused this, but don't remember what it was.
> When I installed KRUD last month I configured for an anticipated network
> connection, but my NIC isn't plugged into a network yet.  Could this be
> the problem?  I've looked through numerous HOWTO's, READMEs, and FAQs in
> search of a reason and haven't found one.  Anyone have a clue?
> 
> Running an AMDK6-2-350 (Oc'd to 400), KRUD Red Hat 6.0
> 
> X reports:
> XFree86 Version 3.3.3.1
> Operating System: Linux 2.0.36 i586
> 
> "uname -a" reports:
> Linux (none) 2.2.5-22
> 
> CPU states (BEFORE doing "xinit"): 0.0% user, 0.3% system, 0.0% nice,
> 99.6% idle
> 
> largest CPU process reported by top BEFORE doing "xinit" is:
> top 0.3 %CPU 0.7 %MEM
> 
> largest memory user reported by "ps -aux | sort +5n" BEFORE doing "xinit"
> is:
> xfs 1.5 %MEM
> 
> CPU states (AFTER doing "xinit"): 0.3% user, 0.1% system, 0.0% nice, 99.4%
> idle
> 
> largest CPU process reported by top AFTER "xinit" is:
> top 0.5 %CPU 0.7 %MEM
> 
> largest memory user reported by "ps -aux | sort +5n" AFTER "xinit" is:
> /usr/X11R6/bin/Xw 1.8 %MEM
> 
> Services started at bootup:
> apmd
> atd
> crond
> gnomehack (started, but not running)
> gpm
> inet
> keytable (started, but not running)
> linuxconf (started, but not running)
> lpd
> network (started, but not running)
> pcmcia (started, but not running)
> portmap
> random (started, but not running)
> rinet
> sound (started, but not running)
> sshd
> xfs
> 
> /etc/hosts:
> 127.0.0.1        localhost localhost.localdomain
> ABC.DEF.GHI.JKL
> 
> 
> (where ABC.DEF.GHI.JKL is an actual IP address inside the network I
> anticipated being connected to)