Page 1 of 1

Problem with 2.6.27 kernel

Posted: 12. Aug 2008, 02:54
by scottro
I'm running Fedora rawhide on one machine. (Fedora 10 alpha, more or less.)

It's using kernel 2.6.27-0.244.rc2.git1.fc10.x86_64.

(As you can see, a Fedora kernel.)

Whether I install trying to use the Fedora 9 rpm or the 1.6.4 amd64.run script, I get the following errors in /var/log/ vbox-install.log after running /etc/init.d/vboxdrv setup

Code: Select all

v_linux)"  -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.6/linux/SUPDrv
-linux.o /tmp/vbox.6/linux/SUPDrv-linux.c
In file included from include/linux/smp.h:28,
                 from include/linux/topology.h:33,
                 from include/linux/mmzone.h:683,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from /tmp/vbox.6/SUPDRV.h:98,
                 from /tmp/vbox.6/linux/SUPDrv-linux.c:35:
include/asm/smp.h:187:28: error: mach_apicdef.h: No such file or directory
In file included from include/linux/smp.h:28,
                 from include/linux/topology.h:33,
                 from include/linux/mmzone.h:683,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from /tmp/vbox.6/SUPDRV.h:98,
                 from /tmp/vbox.6/linux/SUPDrv-linux.c:35:

:
include/asm/smp.h: In function ‘hard_smp_processor_id’:
include/asm/smp.h:191: error: implicit declaration of function ‘GET_APIC_ID’
In file included from /tmp/vbox.6/linux/SUPDrv-linux.c:35:
/tmp/vbox.6/SUPDRV.h:104:30: error: asm/semaphore.h: No such file or directory
/tmp/vbox.6/linux/SUPDrv-linux.c: In function ‘supdrvOSGipResume’:
/tmp/vbox.6/linux/SUPDrv-linux.c:1331: error: too many arguments to function ‘sm
p_call_function’
make[2]: *** [/tmp/vbox.6/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.6] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.27-0.244.rc2.git1.fc10.x86_64'
make: *** [vboxdrv] Error 2
 
(I can paste the complete log if you feel it would be helpful)

It seems to be similar to a problem mentioned on ArchLinux forums

http://bbs.archlinux.org/viewtopic.php?pid=402575

It starts around post number 8.

I haven't seen any thing else about it while googling, so it's quite possible it's simply a problem with this Fedora kernel or the kernel the poster on the ArchLinux forums was using. (The suggested solutions there didn't work for me, I can post relevant errors if you feel it would be helpful)

However, as I haven't seen anything else about it while googling, I strongly suspect it's simply some sort of Fedora kernel issue. However, I would be curious to know if others are having trouble with 2.6.27 kernels. (So few distributions are using it yet that I think that could also be a reason.)

I haven't tried with a vanilla 2.6.27 kernel, my time is a bit limited and this isn't a high priority for me. (It's a test install, and for my really necessary use of VBox, I have it on a CentOS install, where it gives no trouble.)

However, I thought I'd throw the question out here to see if it's one of those Just Me(TM) problems. I'm not sure what other information would be helpful. It's a 64 bit installation on a laptop that also has a CentOS install and Fedora 9 install--all 64 bit and all running Vbox 1.6.4 from their respective rpms without problem.


EDIT: One more thing possibly worth mentioning--the Fedora 9 rpm worked without problem on rawhide until rawhide updated to the 2.6.27 kernel.

Posted: 13. Aug 2008, 14:50
by Sasquatch
That kernel is not yet final, so not supported. Locking this one, as it's asked before and alpha versions (and even beta) are not supported unless mentioned in the release notes.