From owner-freebsd-mobile  Thu Jan  9 22:41:31 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA22541
          for mobile-outgoing; Thu, 9 Jan 1997 22:41:31 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22536
          for <mobile@freebsd.org>; Thu, 9 Jan 1997 22:41:29 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA10422; Thu, 9 Jan 1997 23:41:22 -0700 (MST)
Date: Thu, 9 Jan 1997 23:41:22 -0700 (MST)
Message-Id: <199701100641.XAA10422@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Cc: nate@mt.sri.com (Nate Williams), mobile@freebsd.org
Subject: Re: FreeBSD Laptop Question.
In-Reply-To: <199701100638.RAA03512@genesis.atrad.adelaide.edu.au>
References: <199701100626.XAA10376@rocky.mt.sri.com>
	<199701100638.RAA03512@genesis.atrad.adelaide.edu.au>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > OK, OK, OK.  I just tried it again on my -current system and *NOW* it
> > appears to be working fine.  Honestly, it was causing kernel crashes on
> > my machine just before Christmas.
> 
> I believe you 8) I just meant that whatever might have been the
> problem wasn't a generic 2.2 problem.

According to XInside tech. support they were seeing the problem as well,
though.

> Note that there are lot of
> incrementally-2.2 systems out there with no libgnumalloc in /usr/lib,
> but without updated /etc/rc's that will cause X grief, which _may_
> be part of the problem.  Dunno though.

Naw, I made sure I updated all of the /etc files.  However, they were
updated from 2.0.5 boxes and skipped 2.1* completely, so that might be
something....



Nate