Date: Mon, 4 Aug 2014 13:19:30 +0200 From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= <decke@FreeBSD.org> To: Matthias Apitz <guru@unixarea.de> Cc: "freebsd-emulation@freebsd.org" <emulation@freebsd.org> Subject: Re: [Call for Testers] VirtualBox 4.3.0 Message-ID: <CAE-m3X3wE_hRtT41jd7vH4zXfE6iAsnGJr1_qdhn0FWHbZM84g@mail.gmail.com> In-Reply-To: <20140804085140.GA1669@La-Habana> References: <CAE-m3X2AEvxdAb4y2ACYsZkKBddSEPkffq3j3WUaPZQS0mtbDA@mail.gmail.com> <20140804085140.GA1669@La-Habana>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 4, 2014 at 10:51 AM, Matthias Apitz <guru@unixarea.de> wrote: > El d=C3=ADa Friday, January 03, 2014 a las 04:15:30PM +0100, Bernhard Fr= =C3=B6hlich escribi=C3=B3: > >> VirtualBox 4.3.6 Ports: >> http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.6-2014010= 3.tar.gz >> >> ... > > > Hello, > > Based on the call for testers file virtualbox-cft-4.3.0-20131020.tar.gz > I compiled ports/emulators/virtualbox-ose-additions; > > the background of using this version from end of October is, that > it is the last one which fits in my ports tree and the 10-CURRENT > (r255948, ports: r328930, October 1st 2013) I have to run > in this VM which runs fine in vbox of Ubuntu 14.04; > > after this 4.3.0 there was a fundamental change in the ports tree and it > would mean that I have to compile all my ports from scratch; > > I had a few errors and removed > > -fformat-extensions > -fno-format-extensions > -mno-align-long-strings > > from work/VirtualBox-4.3.0/Config.kmk and after this it > compiled and installed fine with: > > # make install USE_GCC=3Dany > > but the system can not load the module: > > # /usr/local/etc/rc.d/vboxguest start > /usr/local/etc/rc.d/vboxguest: WARNING: Can't load vboxguest module. > # ls -ltr /boot/modules/vb* > -r-xr-xr-x 1 root wheel 5433 Aug 4 10:24 /boot/modules/vboxvideo.ko > -r-xr-xr-x 1 root wheel 184387 Aug 4 10:24 /boot/modules/vboxguest.ko > # kldload /boot/modules/vboxguest.ko > kldload: can't load /boot/modules/vboxguest.ko: No such file or directory > > Why is this? Please have a look at /var/log/messages when loading the kernel module because the real cause is posted there when loading fails. --=20 Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X3wE_hRtT41jd7vH4zXfE6iAsnGJr1_qdhn0FWHbZM84g>