[97763] in RedHat Linux List
Re: Window manager not starting
daemon@ATHENA.MIT.EDU (Dorian)
Wed Nov 4 23:09:14 1998
Date: Sun, 1 Nov 1998 21:58:39 -0500
From: Dorian <nazark@idt.net>
To: redhat-list@redhat.com
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
I had a similar problem. sues-xf86config did something wrong in creating /dev/X11/XFree86Cnofig so X wouldnt
+start up andymore.
Fortunatley I has saved my previous XFree86Config so I restored it. Hope you saved it too or at least backt up
+xfree86config if not reinstall X. Anyway appraently how you get X to use a different X server is by making
+the /etc/X11/X and /usr/X11R6/bin/X
links point to it so you wuld give a command like
ln -s /usr/X11R6/bin/X /usr/X11R6/bin/XFCom_Matrox (replace with your server of course)
ln -s /etc/X11/X /usr/X11R6/bin/XFCom_Matrox (again replacve with yours)
Hope this helps
On Sat, 31 Oct 1998 03:33:53 Braden N. McDaniel wrote:
> Okay... I installed RH 5.1. I have a Permedia2-based video card, so I
> installed the SuSE X-server for that chip, along with their modified
> xf86config. After running xf86config, I typed "startx", and things seemed to
> work just fine.
>
> After a bit, I exited FVWM/X and went back to the console. But then, when I
> tried "startx" again, I just got the black and white crosshatched background
> and the "X" cursor--the window manager wouldn't start. I didn't knowningly
> do *anything* that might have affected this. The *only* thing I did was
> modify the XF86Config file to include a "DefaultColorDepth" line. But even
> commenting out that addition didn't help. Even running xf86config again to
> generate a new XF86Config file didn't help.
>
> How can I fix this?
>
> Braden
>
> <http://www.endoframe.com>
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
