From owner-freebsd-questions Tue Apr 23 15: 1:48 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fac13.ds.psu.edu (fac13.ds.psu.edu [146.186.61.98]) by hub.freebsd.org (Postfix) with ESMTP id A6DFF37B41A for ; Tue, 23 Apr 2002 15:01:34 -0700 (PDT) Received: from fac13.ds.psu.edu (localhost [127.0.0.1]) by fac13.ds.psu.edu (8.12.2/8.12.2) with ESMTP id g3NM1Oer014294; Tue, 23 Apr 2002 18:01:24 -0400 (EDT) (envelope-from hawk@fac13.ds.psu.edu) Message-Id: <200204232201.g3NM1Oer014294@fac13.ds.psu.edu> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Manuel Hendel Cc: dochawk@psu.edu, FreeBSD Questions Subject: Re: vmwware2 - could not get interface address for vmnet1: ... In-Reply-To: Your message of "Tue, 23 Apr 2002 23:06:05 +0200." <20020423210605.GA73177@habana.easygolucky.de> From: dochawk@psu.edu Date: Tue, 23 Apr 2002 18:01:24 -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Manuel mentioned,m > On Tue, Apr 23, 2002 at 04:44:58PM -0400, dochawk@psu.edu wrote: > > This seems to be related to an instance of vmware that just won't go > > away. > > THe extreme solution: top vmware, deinstall the module, kill the > > devices, reboot, and reinstall. > > Not all of these steps are necessary all the time, but thw whole > > sequence should get you there. > There was no instance after I closed the vmware window the normal way. yes, but something may still be locked. vmware has done this to me a couple of time s . . hawk -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message