Re: X doesn't start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2008-05-26 at 18:18 +0000, Beartooth wrote:
> > On Mon, 2008-05-26 at 16:20 +0000, Beartooth wrote:
> >> On Mon, 26 May 2008 11:05:16 -0430, Patrick O'Callaghan wrote:
> 	[...]
> >> 	Otoh, my hunch says this is progress, or at least gets us off
> >> ground zero. So what next?
> > 
> > pgrep -fl X
> 
> 	pgrep -fl X as user just puts me back to my prompt. As root, it 
> does the same.

That's what it's supposed to do. If it didn't give you any other
feedback, then you aren't running X.

> > will tell you if an X server is running. Rebooting will make sure to get
> > rid of it. Alternatively, do "init 3; init 5" from a console.
> 
> 	Not knowing from console (I can't exactly open a gnome-terminal 
> at the moment), I tried it as root from the one command line I have.

That's a console in Unix-speak.

> It 
> hit a cupsd error, saying it lacked libldap-2.3.so.0, went on, and seemed 
> to hang on starting anacron.
> 
> 	I killed it with ^C, did init 3 alone (which also seemed to hang 
> on anacron) and did init 5.

It only appears to hang because most of the output is coming from
various other processes as they start or finish. If you hit Enter you
should get a Shell prompt.

> 	That did more stuff, of course, still hit the cupsd error, and 
> also set out to start anacron. This time I let it go, and went for a 
> shower (about 1/2 hour). It got past anacron, saying OK; set network 
> parameters, and started the NetworkManager daemon, calling both those OK 
> -- and that's where it still is.

Did any of this happen on a graphical screen, or is it all on the same
white-on-black text console as before? In the normal boot sequence the
startup screen goes graphical (i.e. a few colours and a progress bar)
fairly early in the process.

> 	If I can at least get the machine to connect, I can scp the files 
> I want off it across my LAN; find a way to wipe the whole drive, but not 
> the other drive with XP; install F8 clean; and scp those files back.
> 
>  
> > If it still doesn't work, check for errors (lines marked EE) in
> > /var/log/Xorg.0.log.
> 
> 	That found two. The first says "Unable to locate/open config 
> file." The second gets more specific: "Failed to load module 
> "pcidata"(module does not exist, 0)"

The first one if OK, it's just saying you don't have a config file,
which you know since you moved it. The second one may or may not be a
real problem but I'm afraid my X knowledge doesn't cover it except that
a non-existent module might imply an incomplete installation. My own
Xorg.0.log file has no reference to pcidata (I only have an onboard
Intel 965 chipset).

poc

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux