From owner-freebsd-current Sat Dec 25 14:19:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id 30FBF14C9C for ; Sat, 25 Dec 1999 14:19:38 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00513; Sat, 25 Dec 1999 14:24:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912252224.OAA00513@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: can't get vmware to run ( on -current ) In-reply-to: Your message of "Sat, 25 Dec 1999 23:13:19 +0100." <19991225231318.A44105@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Dec 1999 14:24:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Dec 25, 1999 at 01:11:06PM -0800, Mike Smith wrote: > > Check the console; you have a mismatch somewhere inbetween the vmmon > > module and the Linux module, or between the vmmon module and your kernel. > > Well, I think I had an outdated vmware port. > I grabbed it new from the mindspring webserver. > Then I had to manually load the vmmon.ko module > from /usr/local/lib/vmware/lib/modules It does that automatically when you boot. It'll load the vmnet module then too, which you will probably want. > I created a new configuration and the only problem seems > to be the following error messages: > a) about missing /dev/rtc and > b) could not open /usr/local/lib/vmware/lib/vmm (no such file or directory). No idea about that one. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message