From owner-freebsd-stable Thu Jul 13 8:43:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bman.uucom.com (bman.uucom.com [198.202.217.19]) by hub.freebsd.org (Postfix) with ESMTP id 5CA8337C43B for ; Thu, 13 Jul 2000 08:43:35 -0700 (PDT) (envelope-from dakota@tangerine.uucom.com) Received: from tangerine.uucom.com (tangerine.uucom.com [198.202.217.38]) by bman.uucom.com (8.9.3/8.9.3/990218bjb) with ESMTP id LAA14143 for ; Thu, 13 Jul 2000 11:43:30 -0400 (EDT) Received: from tangerine (localhost [127.0.0.1]) by tangerine.uucom.com (8.9.3+Sun/8.9.3) with ESMTP id LAA21770 for ; Thu, 13 Jul 2000 11:44:17 -0400 (EDT) Message-Id: <200007131544.LAA21770@tangerine.uucom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@freebsd.org From: Matthew Whalen X-image-url: http://www.mediumgreen.com/dakota.gif Subject: vmware2 and xfree86-4.0.1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jul 2000 11:44:17 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a new machine that I'm trying to configure. It's very similar to my regular home machine (PIII 700 vs K7 700). They both run 4.0-stable (home was build last about 1 month ago, new machine yesterday). I have xf86 4 on this new machine, and 3 at home. My vmware on the new machine dies cathing with a SIGSEGV and "Abort trap" being printed to the screen. I know that vmware doesn't officially support XF86 4, but this doesn't really sound a lot like an Xserver problem to me. There isn't much in the vmware log to note. Has anyone tried vmware2 with XF86 4 yet? If so, did you get the same result? Is there something else going on? thank you for any pointers -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message