From owner-freebsd-stable Fri Jul 14 11:42: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 DE06637B8F9 for ; Fri, 14 Jul 2000 11:42: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 OAA29054; Fri, 14 Jul 2000 14:42: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 OAA05107; Fri, 14 Jul 2000 14:43:15 -0400 (EDT) Message-Id: <200007141843.OAA05107@tangerine.uucom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mike ryan Cc: freebsd-stable@FreeBSD.ORG, larse@ISI.EDU, joseph.scott@owp.csus.edu From: mwhalen@uucom.com Subject: Re: vmware2 and xfree86-4.0.1 In-Reply-To: Message from mike ryan of "Thu, 13 Jul 2000 12:26:35 EDT." <20000713122635.A67937@medianstrip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jul 2000 14:43:15 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I heard mike ryan say: >On Thu, Jul 13, 2000 at 11:44:17AM -0400, Matthew Whalen wrote: >> >> 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? > >i've had the same result. i'm also running 4.0-stable built within >the last few days and xfree86 4.0.1, on a sony vaio z505hs laptop. > >on my system at least, there appears to be a correlation with disk >modes -- virtual machines configured with raw disks abort on boot, >virtual machines with virtual disks work fine. Thank you. This fixed the problem. I wonder why a new release of X would break disk access... I guess I'll wait a while before upgrading at home since I have my virtual machine installed on a raw disk partition so that I could boot NT >ick< if I wanted to outside of VMware. -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message