From owner-freebsd-emulation@FreeBSD.ORG Sun Jul 5 17:22:55 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B557C1065670 for ; Sun, 5 Jul 2009 17:22:55 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email1.allantgroup.com (email1.emsphone.com [199.67.51.115]) by mx1.freebsd.org (Postfix) with ESMTP id 47F2A8FC15 for ; Sun, 5 Jul 2009 17:22:55 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email1.allantgroup.com (8.14.0/8.14.0) with ESMTP id n65GeRvI009948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 5 Jul 2009 11:40:27 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id n65GeQ3k080114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 5 Jul 2009 11:40:27 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id n65GePi4080112; Sun, 5 Jul 2009 11:40:25 -0500 (CDT) (envelope-from dan) Date: Sun, 5 Jul 2009 11:40:25 -0500 From: Dan Nelson To: Gary Jennejohn Message-ID: <20090705164025.GB5574@dan.emsphone.com> References: <252646496.283281246727198407.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> <1864081109.283641246727373779.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> <20090705101936.3434ea18@ernst.jennejohn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090705101936.3434ea18@ernst.jennejohn.org> X-OS: FreeBSD 7.2-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) X-Virus-Scanned: ClamAV version 0.94.1, clamav-milter version 0.94.1 on email1.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (email1.allantgroup.com [199.67.51.78]); Sun, 05 Jul 2009 11:40:27 -0500 (CDT) X-Scanned-By: MIMEDefang 2.45 Cc: freebsd-emulation@freebsd.org, rondzierwa@comcast.net Subject: Re: vbox driver X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jul 2009 17:22:56 -0000 In the last episode (Jul 05), Gary Jennejohn said: > On Sat, 4 Jul 2009 17:09:33 +0000 (UTC) > rondzierwa@comcast.net wrote: > > I have installed the VirtualBox port my FreeBSD 7.0 system. I had to > > csup ports and download and install the virtualbox port manually, but > > eventually everything built and installed. > > > > kldload has a problem with the vboxdrv module: > > > > phoenix# kldload /boot/modules/vboxdrv.ko > > kldload: can't load /boot/modules/vboxdrv.ko: No such file or directory > > > > the file is there, and kldconfig is set up for the /boot/modules directory: > > > > phoenix# kldconfig -r > > /boot/kernel;/boot/modules > > phoenix# ls -l /boot/modules > > total 182 > > -r-xr-xr-x 1 root wheel 185300 Jul 4 12:57 vboxdrv.ko > > > > could it be that there is no vboxdrv.ko.symbols file? all the other > > modules are in the /boot/kernel directory, and they all have .symbols > > files. > > > > This error message is confusing and doesn't necessarily really have > anything to do with vboxdrv.ko being present. kldload(2) in the kernel > can return a number of errors, but they're all hidden behind the error > message "can't load..." > > kldload(8) should probably use perror(3) so the user can see exactly > what the error returned from the kernel was. kldload did use perror; the kernel returned ENOENT - "No such file or directory". The problem is that the 92 defined errno values are not enough to describe all possible ways a syscall can fail. When loading a module, the most likely cause of ENOENT is a missing symbol preventing the linker from loading the module. The kernel will print a more verbose message to the console, so run dmesg and see what it's complaining about. -- Dan Nelson dnelson@allantgroup.com