From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:16:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE1E116A4CF; Wed, 21 Jul 2004 17:16:00 +0000 (GMT) Received: from mta08-svc.ntlworld.com (mta08-svc.ntlworld.com [62.253.162.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B00A43D64; Wed, 21 Jul 2004 17:16:00 +0000 (GMT) (envelope-from ben@spooty.net) Received: from m157-mp1.cvx3-b.pop.dial.ntli.net ([80.1.84.157]) by mta08-svc.ntlworld.comESMTP <20040721171555.WEYO548.mta08-svc.ntlworld.com@m157-mp1.cvx3-b.pop.dial.ntli.net>; Wed, 21 Jul 2004 18:15:55 +0100 From: Ben Paley To: Robert Watson Date: Wed, 21 Jul 2004 18:12:29 +0100 User-Agent: KMail/1.6.1 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407211812.29934.ben@spooty.net> cc: "freebsd -current@" cc: Scott Long Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:16:01 -0000 On Wednesday 21 July 2004 17:01, Robert Watson wrote: > On Wed, 21 Jul 2004, Scott Long wrote: > > > Additional ABI support: linux. > > > Starting cron. > > > Local package initialization:link_elf: symbol > > > linux_ioctl_register_handler undefined > > > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such > > > file or directory > > > > Is your linux.ko module out of date? You have a mis-match somewhere > > here. > > Or, alternatively, the symbols exported by the Linux emulation module have > changed, and the VMware port hasn't caught up (or the local copy needs > updating). Something is definitely out of sync, needless to say, but it > could be that the VMware module needs updating in the pseudo-vendor. So it looks like I need to update everything (world, kernel, vmware and linux base) before trying any harder on this... bummer. One of the reasons I haven't done that since mid June is that my system was all in sync then (so I thought) and I wanted to get this sorted before I started messing it all around again... Oh well, thanks a lot for your help. I'll get back in touch after I've found the time to do that and it _still_ doesn't work! Thanks a lot, Ben