2.6.27-rc8 and virtualbox

radiodee1 · 10-05-2008, 03:09 PM

I downloaded linux-2.6.27-rc8 last night. I unpacked it and copied the congfig file from 2.6.26-1. Then I executed:

Code:

$ fakeroot make-kpkg --initrd --append-to-version=d1 kernel_image kernel_headers

then I installed the headers and kernel packages as root with dpkg. I went on to build VirtualBox from source. After some messing around I got the whole thing to compile the debian way with 'debian/rules'. Still the kernel module wouldn't compile. As per VirtualBox intructions I typed:

Code:

# /etc/init.d/vboxdrv setup

I got this error in the error log.

Quote:

make[1]: Entering directory `/usr/src/linux-headers-2.6.27-rc8-d1'
/usr/src/linux-headers-2.6.27-rc8-d1/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.27-rc8-d1/arch/x86/Makefile_32.cpu: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.27-rc8-d1/arch/x86/Makefile_32.cpu'. Stop.

Did I make a mistake when I was compiling the kernel in the first place? I looked in the x86 folder. There is no Makefile_32 there. Thanks alot. Any help would be appreciated.

Quakeboy02 · 10-05-2008, 03:22 PM

It's kinda hard to figure out what you're actually wound up with. Did you get the following line (or something very very close to it) to run properly?

Code:

fakeroot make-kpkg --append_to_version -k2 --initrd --revision=rev.01 kernel_image

Once that ran, did you do the following?

Code:

cd ..
dpkg -i linux-image-2.6.27-rc8-k7_0.1_i386.deb

The "k7_0.1" would be something else on your machine. In any case, did you get a successful install with the "dpkg -i"? If so, are you now booted from it? If not, go back to step one and keep trying till you can boot from the new kernel.

Once you're booted, I have to admit that I don't know about doing the "vboxdrv setup". I gave up in frustration about where you are and installed VirtualBox from source using the instructions spat out by configure. I suspect it's just that you're not booted from the new kernel. After playing with this a bit and understanding it some more, I'm tempted to do an uninstall and try the aptitude version, again.

radiodee1 · 10-05-2008, 03:27 PM

Quote:

Originally Posted by Quakeboy02

It's kinda hard to figure out what you're actually wound up with. Did you get the following line (or something very very close to it) to run properly?

Code:

fakeroot make-kpkg --append_to_version -k2 --initrd --revision=rev.01 kernel_image

Once that ran, did you do the following?

Code:

cd ..
dpkg -i linux-image-2.6.27-rc8-k7_0.1_i386.deb

...

I did all of that, except the '-k2' part. What's that?!! I'm typing from the new kernel right now. (??)

Quakeboy02 · 10-05-2008, 03:28 PM

After thinking about this some more, I have another question: where did you get this kernel source from? If it's from kernel.org, that's likely the root of your problem. Debian add their own stuff to kernels so that the installer will work with installable packages. When I was looking into using the Debian VirtualBox package, I got the feeling that I had to use a Debian kernel, not one I downloaded from kernel.org. That kinda stopped it for me, because I needed 2.6,27.

radiodee1 · 10-05-2008, 03:30 PM

it is from kernel.org

Quakeboy02 · 10-05-2008, 03:31 PM

Quote:

Originally Posted by radiodee1

I did all of that, except the '-k2' part. What's that?!! I'm typing from the new kernel right now. (??)

Oh snap! That's a typo in my make script. Should be k7 for an AMD K7 processor. Thanks for finding it for me.

Quakeboy02 · 10-05-2008, 03:34 PM

Quote:

Originally Posted by radiodee1

it is from kernel.org

Yeah, then without major surgery, you'll probably have to install VirtualBox from the source at http://download.virtualbox.org/virtu....2-OSE.tar.bz2. It's near the bottom of this page if you don't trust my link: http://www.virtualbox.org/wiki/Downloads

I'll hang around here to try to get you going, as I have some experience doing it that way.

radiodee1 · 10-05-2008, 03:43 PM

That's exactly the file I downloaded. Then I had to edit the debian/rules file so that the './configure' would happen properly, otherwise it wouldn't start compiling. Did you have that experience? I had to pass the flag '--with-gcc-compat=/usr/bin/gcc-4.3' for it to work.

Quakeboy02 · 10-05-2008, 03:48 PM

Quote:

Originally Posted by radiodee1

That's exactly the file I downloaded. Then I had to edit the debian/rules file so that the './configure' would happen properly, otherwise it wouldn't start compiling. Did you have that experience? I had to pass the flag '--with-gcc-compat=/usr/bin/gcc-4.3' for it to work.

I had no problem with anything other than adding --with-gcc-compat=gcc-4.1. You must not use 4.3 here. Here is a copy of my configure script. (OK, so I'm script-happy)

Code:

#!/bin/sh
./configure --disable-hardening --with-gcc-compat=gcc-4.1 > configit.log

radiodee1 · 10-05-2008, 03:54 PM

I'll try 4.1 and get back to you.

Quakeboy02 · 10-05-2008, 03:56 PM

Quote:

Originally Posted by radiodee1

I'll try 4.1 and get back to you.

I think you'll have to install both gcc-4.1 and g++-4.1. Just keep installing stuff till configure stops complaining.

radiodee1 · 10-05-2008, 04:32 PM

I got past the configure stage but kmk stops on this file. This is a file that was giving me problems before.

Quote:

kmk[2]: *** [/home/dave/deb_i386/VirtualBox-2.0.2/debian/builddir/obj/RuntimeR0Drv/common/alloc/alloc.o] Error 1

The next message after the command line that stopped kmk (which I won't show here) is this:

Quote:

kmk[1]: *** [pass_libraries_before] Error 2
kmk: *** [pass_libraries_before] Error 2
make: *** [debian/build-stamp] Error 2

BTW, what does 'pass_libraries_before' mean?

EDIT: gcc-3.4 and cpp-3.4 seem to work better than gcc-4.1 and cpp-4.1, or at least marginally better.

Quakeboy02 · 10-05-2008, 04:40 PM

Did you run the following first?

Code:

source ./env.sh

Quakeboy02 · 10-05-2008, 04:45 PM

Hmmm. Exactly what are you running and exactly what changes have you made to any scripts? All I needed to do was the following:

Code:

./configure --disable-hardening --with-gcc-compat=gcc-4.1 > configit.log
source ./env.sh
kmk all

That gave me the VirtualBox front end. Then, as the instructions say, you:

Code:

cd ./out/linux.x86/release/bin/src
make
sudo make install

Then it was just a matter of going down the tree to modprobe vboxdrv and then running the program.

radiodee1 · 10-05-2008, 04:48 PM

Yeah, you're describing the kmk way, without the 'debian/rules' file. yep, I sourced 'env.sh'. I tried it both ways, both using 'debian/rules' and with kmk. I either get hung up on 'alloc.o' or on 'crc32.o'. Once I actually got the binaries in debian form, and those are the ones I tried to install. Can I use a version of virtualbox that I've compiled for a different kernel? I've got a couple of those.