From owner-freebsd-questions Fri Nov 16 3:51:44 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id E214A37B418 for ; Fri, 16 Nov 2001 03:51:41 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Fri, 16 Nov 2001 11:51:34 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 164hVB-0001CJ-00; Fri, 16 Nov 2001 11:49:45 +0000 Date: Fri, 16 Nov 2001 11:49:45 +0000 (GMT) From: Jan Grant X-X-Sender: To: Manuel Hendel Cc: FreeBSD Questions Subject: Re: vmware - could not get address for /dev/vmnet1: In-Reply-To: <20011116074848.GA37900@he0.easygolucky.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Fri, 16 Nov 2001, Manuel Hendel wrote: > Yesterday I did a complete upgrade. Afterwards vmware didn't work > anymore. The following error message appeared: > > Could not get address for /dev/vmnet1: Invalid argument > Failed to configure ethernet0. > > Does anyone know, where this comes from? What can I do against it? The > point is, that I didn't change anything after my upgrade, I just > rebooted. This seems to be coming from the linux compatability layer upgrade. It's been discussed a bit on -stable, no solutions as yet. You could try going back to a -STABLE with a release date prior to the changes (November 5th, I think, is ok). You'll probably find that the port's maintainer is already aware of this; have you checked for/filed a PR? -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk "I like oranges more than apples!?" - that's like comparing apples and oranges! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message