From owner-freebsd-stable Wed Jan 3 20:41:43 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 20:41:42 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 1DF6037B400 for ; Wed, 3 Jan 2001 20:41:40 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA19642; Thu, 4 Jan 2001 15:11:31 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101040444.f044i6e04138@henry.cs.adfa.edu.au> Date: Thu, 04 Jan 2001 15:11:30 +1030 (CST) Sender: doconnor@gsoft.com.au From: "Daniel O'Connor" To: wkt@cs.adfa.edu.au Subject: Re: kldload: Exec format error, is 4.2 problem? Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-01 Warren Toomey wrote: > No, I don't see any kernel messages in /var/log/messages. I downloaded > and used the vmware port for FreeBSD 4.2 after I'd moved to 4.2-STABLE. > > Has there been any changes to kernel modules, magic numbers etc. that > would cause this problem? Hmm.. well generally when you update your kernel source you need to update the kld's as well. This happens automatically when you build a kernel for the 'normal' kld's, but the ones which come in ports (vmware, skip) need to be updated by rebuilding the port. > I'll try reading through imgact_elf.c and compare magic numbers there > with the values in the .ko files. Good luck :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message