From owner-freebsd-questions  Mon Sep 27 12:47: 9 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from vega.brown.edu (vega.cis-176.brown.edu [128.148.176.47])
	by hub.freebsd.org (Postfix) with ESMTP id 491BB15389
	for <freebsd-questions@freebsd.org>; Mon, 27 Sep 1999 12:47:01 -0700 (PDT)
	(envelope-from Pillsy@Brown.edu)
Received: from Brown.edu ([128.148.212.245])
	by vega.brown.edu (8.9.3/8.9.3) with ESMTP id PAA21901
	for <freebsd-questions@freebsd.org>; Mon, 27 Sep 1999 15:47:00 -0400 (EDT)
Message-ID: <37EFC9B0.4DA8AC4B@Brown.edu>
Date: Mon, 27 Sep 1999 15:46:56 -0400
From: Matt Pillsbury <Pillsy@Brown.edu>
Organization: Procrastinators for a Better Tomorrow
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: XFree86 / GNOME problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

I am running 3.2-RELEASE on a PPro 200 w/ 96 megs of RAM. I am also
using 
XFree86 3.3.1 (for the RIVA TNT) and GNOME 1.0.5 (the one in ports).
When
I log out, the X server will lock up the console very hard--nothing
(CTRL-
ALT-DEL, CTRL-ALT-BACKSPACE) seems to get through. I can still got to my
roomates computer and telnet in and everything works fine. When I do
"top" 
or "ps -a" there's no sign of an X server process running, and I can
"kill
-9" just about everything in sight without getting my console back. I
end
up having to reboot the machine remotely to use it from the console.

So,

  a) what can I do to prevent the X crashes?

  b) if I'm stuck with the crashes, how do I get my console back w/o 
  rebooting.

Thanks muchly,
Matt

-- 
Matt Pillsbury                  "If you can't hear the signal,
pillsy [at] brown [dot] edu     just enjoy the noise."


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message