From owner-freebsd-ports  Tue Mar 27 14:30: 7 2001
Delivered-To: freebsd-ports@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 1F88137B71A
	for <freebsd-ports@hub.freebsd.org>; Tue, 27 Mar 2001 14:30:04 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f2RMU4v49636;
	Tue, 27 Mar 2001 14:30:04 -0800 (PST)
	(envelope-from gnats)
Date: Tue, 27 Mar 2001 14:30:04 -0800 (PST)
Message-Id: <200103272230.f2RMU4v49636@freefall.freebsd.org>
To: freebsd-ports@FreeBSD.org
Cc: 
From: Nate Dannenberg <natedac@kscable.com>
Subject: Re: ports/25958: Xfree86's savage and vesa drivers%2
Reply-To: Nate Dannenberg <natedac@kscable.com>
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR ports/25958; it has been noted by GNATS.

From: Nate Dannenberg <natedac@kscable.com>
To: <freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: ports/25958: Xfree86's savage and vesa drivers%2
Date: Tue, 27 Mar 2001 16:14:57 -0600 (CST)

 On Tue, 27 Mar 2001 natedac@kscable.com wrote:
 
 > Athlon, or the kernel is somehow detecting it wrong.  XFree86
 > 4.4.x obviously is trying to use this feature somehow, and that was
 > causing a kernel panic.
 
 Erm... make that 4.0.x (i.e. 4.0.2, 4.0.3)
 
 -- 
  /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~___~~~~~\
 |  natedac@kscable.com              //Z@|___  |
 |  http://home.kscable.com/natedac |'(__ [_<  |
  \_C64/C128_-_What's_*YOUR*_hobby?__\___|____/
 

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