Kernel 25 but no virtualbox-modules

dear all,
since there is 2.6.25 the virtualbox-modules compile but cannot be loaded
any help appreciated:
sudo modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-ARCH/misc/vboxdrv.ko): Unknown symbol in module, or unknown parameter (see dmesg)
dmesg | tail
vboxdrv: Unknown symbol change_page_attr

zyghom wrote:
dear all,
since there is 2.6.25 the virtualbox-modules compile but cannot be loaded
any help appreciated:
sudo modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-ARCH/misc/vboxdrv.ko): Unknown symbol in module, or unknown parameter (see dmesg)
dmesg | tail
vboxdrv: Unknown symbol change_page_attr
Already answered you in the announcement thread, but here it is again:
http://users.archlinux.de/~pierre/packa … x/vboxdrv/

Similar Messages

Kernel upgrade broke VirtualBox modules

Hi guys,
after upgrading the kernel from linux-3.4.4-3 to linux-3.4.5-1 the VirtualBox modules for the new kernel aren't generated automatically.
Downgrading the kernel helps, but that's just an interim solution. Does anyone know how to build the modules manually? 'vboxbuild' and '/etc/rc.d/vboxdrv setup' is obviously deprecated. Even on virtualbox.org I couldn't find clear instructions.
I really don't know whether it's a kernel or VirtualBox issue.
Any ideas?
Thx & Rgds
hcjl
Last edited by hcjl (2012-07-18 09:13:15)

kernel 3.4.5-1 has just moved to core. The matching precompiled virtualbox-modules are still in community-testing. Just wait a bit longer.
Last edited by progandy (2012-07-18 09:40:23)

Virtualbox-ose, virtualbox-modules 2.2.0 on kernel 2.6.29

Anyone managed to get virtualbox-ose and virtualbox-modules 2.2.0 working on kernel 2.6.29?
I tried editing the virtualbox-modules PKGBUILD like so:
9,10c10,11
< _kernver=2.6.28-ARCH
< pkgver=2.1.2
> _kernver=2.6.29-ARCH
> pkgver=2.2.0
16,17c17,18
< depends=('kernel26>=2.6.28' 'kernel26<2.6.29')
< makedepends=('bin86' 'dev86' 'iasl' 'libstdc++5' 'qt3' 'sdl_ttf' 'libxt'
> depends=('kernel26>=2.6.28' 'kernel26<2.6.30')
> makedepends=('bin86' 'dev86' 'iasl' 'libstdc++5' 'qt3' 'qt4' 'sdl_ttf' 'libxt'
44c45
< md5sums=('ce1360945d65a79dbea1bec997c25c00')
> md5sums=('37bd7d58cf7b6c46998cfd82c1b70573')
to get the makedeps in place I did
pacman -Sy --asdeps dev86 iasl qt3 qt4 sdl_ttf pulseaudio gcc34 xalan-c
But when I run makepkg it can't find Qt4

schuay wrote:isn't qt4 just called qt?
actually qt provides qt4. so If you call pacman -S qt4 it will install qt (which is at version 4.something)
I have qt and qt3 installed.
schuay wrote:
and you'll also probably need this:
#get virtualbox working with 2.6.29
in /opt/virtualbox/src/vboxdrv/Makefile, uncomment VBOX_USE_INSERT_PAGE and recompile module - should be fixed by 2.6.29.1
for -ose i'm not sure where the Makefile is, but i guess you can find it with grep
I don't think so. I'm running 2.6.29.1

Cannot update: virtualbox modules need a lower kernel

Today I did pacman -Syu and got:
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-modules: requires kernel26<2.6.28
So do I need to wait until virtualbox is updated or I have to force update and recompile virtualbox modules?

here's a patch for the virtualbox-modules PKGBUILD from ABS:
--- /var/abs/community/modules/virtualbox-modules/PKGBUILD 2008-11-12 06:47:12.000000000 +0100
+++ PKGBUILD 2009-01-21 13:46:08.000000000 +0100
@@ -6,14 +6,14 @@
# Contributor: Ingmar Steen
pkgname=virtualbox-modules
-_kernver=2.6.27-ARCH
-pkgver=2.0.4
+_kernver=`uname -r`
+pkgver=2.1.0
pkgrel=1
pkgdesc="Kernel modules for VirtualBox (vboxdrv)"
arch=('i686')
url="http://www.virtualbox.org"
license=('GPL')
-depends=('kernel26>=2.6.27' 'kernel26<2.6.28')
+depends=('kernel26>=2.6.27')
makedepends=('bin86' 'dev86' 'iasl' 'libstdc++5' 'qt3' 'sdl_ttf' 'libxt'
'libgl' 'alsa-lib' 'pulseaudio' 'gcc34' 'libxcursor' 'libidl2' 'libxslt'
'xalan-c' 'pth' 'libxml2' 'libidl2' 'libpng')
@@ -41,4 +41,4 @@
install -D -m644 vboxdrv.ko "$pkgdir/lib/modules/${_kernver}/misc/vboxdrv.ko"
sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" "$startdir/virtualbox-modules.install"
-md5sums=('89db3f4a227f97c1e080035fbadd10c8')
+md5sums=('4d8f857c9ead892607387656a9e895bb')
and this is for virtualbox-ose:
--- /var/abs/community/emulators/virtualbox-ose/PKGBUILD 2008-11-12 06:30:45.000000000 +0100
+++ PKGBUILD 2009-01-21 14:43:57.000000000 +0100
@@ -4,7 +4,7 @@
# Contributor: Michal Krenek <[email protected]>
# Contributor: niQo
pkgname=virtualbox-ose
-pkgver=2.0.4
+pkgver=2.1.0
pkgrel=1
pkgdesc="Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)"
url="http://www.virtualbox.org"
@@ -70,5 +70,5 @@
install -D -m644 "$srcdir/60-virtualbox.rules" \
"$pkgdir/etc/udev/rules.d/60-virtualbox.rules"
-md5sums=('89db3f4a227f97c1e080035fbadd10c8'
- '519d32d8c2408e0ed9d643f412117644')
+md5sums=('4d8f857c9ead892607387656a9e895bb'
+ '519d32d8c2408e0ed9d643f412117644')
by the way, there's still a warning at compile time "hardening is disabled, you shouldn't build vbox for distributions without hardening". anybody know the right way to fix this without breaking vbox?
Last edited by schuay (2009-01-21 14:13:14)

Virtualbox modules compilation from virtualbox-source no longer works

Since virtualbox-source dropped /usr/bin/vboxbuild and started depending on dkms, I can no longer compile VirtualBox modules for my kernel.
I use:
thar@myhost ~> uname -a
Linux myhost 3.4.6-1-ck #1 SMP PREEMPT Sun Jul 22 09:37:50 EDT 2012 x86_64 GNU/Linux
virtualbox, virtualbox-source and dkms in newest versions. Module compilation and instalation with dkms is seemingly fine:
thar@myhost ~> sudo dkms install vboxhost/4.1.18
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.4.6-1-ck -C /usr/lib/modules/3.4.6-1-ck/build M=/var/lib/dkms/vboxhost/4.1.18/build..............
cleaning build area....
DKMS: build completed.
vboxdrv.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/3.4.6-1-ck/kernel/misc/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/3.4.6-1-ck/kernel/misc/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/3.4.6-1-ck/kernel/misc/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/3.4.6-1-ck/kernel/misc/
depmod......
DKMS: install completed.
But then:
thar@myhost ~> sudo modprobe vboxdrv
ERROR: could not insert 'vboxdrv': Exec format error
I have seen similar topic on Chakra support forums. The advice was not to use dkms. Because in Arch virtualbox-source package has a dependency on it, it is not applicable (and anyways, virtualbox-source doesn't have vboxbuild anymore).

None of the previous mentioned methods worked for me:
I'm still using the stock kernel 3.3.4 because of the high load problems since 3.3.5.
$ uname -a
Linux zeus 3.3.4-2-ARCH #1 SMP PREEMPT Wed May 2 18:28:42 CEST 2012 x86_64 GNU/Linux
linux-headers are installed:
$ yaourt -Qs linux-headers
core/linux-headers 3.3.4-2
Header files and scripts for building modules for linux kernel
vboxbuild doesn't work...
$ sudo /usr/lib/vboxbuild
sudo: /usr/lib/vboxbuild: command not found
dkms also...
$ sudo rc.d start dkms
:: Starting Dynamic Kernel Module System [BUSY]
Error! echo
Your kernel headers for kernel 3.3.4-2-ARCH cannot be found at
/usr/lib/modules/3.3.4-2-ARCH/build or /usr/lib/modules/3.3.4-2-ARCH/source. [DONE]
$ sudo dkms install vboxhost/4.1.18 -k 3.3.4-2-ARCH/x86_64
Error! echo
Your kernel headers for kernel 3.3.4-2-ARCH cannot be found at
/usr/lib/modules/3.3.4-2-ARCH/build or /usr/lib/modules/3.3.4-2-ARCH/source.
BUT:
/usr/lib/modules/3.3.4-2-ARCH/build exists and contains a symlink to the correct headers under /usr/src/linux-3.3.4-2-ARCH:
ls -l /lib/modules/3.3.4-2-ARCH/build
lrwxrwxrwx 1 root root 35 Mai 2 18:39 /lib/modules/3.3.4-2-ARCH/build -> ../../../usr/src/linux-3.3.4-2-ARCH
What can I still do to get virtualbox working?
Thanks!

Virtualbox-modules cannot resolve dependecies

resolving dependencies...
error: cannot resolve "kernel26<2.6.26", a dependency of "virtualbox-modules"
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-modules: requires kernel26<2.6.26

this is because the vm* pkg theoretically has o support for the newer kernel yet
o either rebuild it and see if it works against the new one
find a patch for the new kernel and rebuild
or if you don't use it currently you could force the upgrade
pacman -Syud (d to ignore the dependency)
this way you can continue to test the new pkgs
you may wanna check the bug tracker a more permanent fix(patch) may have been submitted there
if there exists a bug report

Problem upgrading and installing virtualbox-modules

Have some problems upgrading and installing virtualbox-modules
[elgringo@compjotr Desktop]$ sudo pacman -S community/virtualbox-modules
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: lirc: requires kernel26>=2.6.26-1
:: nvidia: requires kernel26>=2.6.26-1
Had to uninstall lirc nvidia and virtualbox-modules before I could upgrade the kernel and now I can't install the virtualbox-modules.
Anyone else who experienced the same problems?

virtualbox-modules depends on the kernel in core. If you want to use the kernel in testing, you'll need to rebuild the virtualbox-modules against it.
Virtualbox-modules will be fixed when kernel 2.6.26 will be moved in core. So you can wait if you prefer.

[SOLVED] virtualbox-modules: dkms: command not found

$ makepkg -s
==> Making package: virtualbox-modules 4.2.6-4 (Tue Jan 29 15:42:01 EET 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
-> Host modules
/home/yuri/builds/virtualbox-modules/PKGBUILD: line 26: dkms: command not found
==> ERROR: A failure occurred in build().
Aborting...
$ which dkms
which: no dkms in (~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/vendor_perl:/usr/bin/core_perl)
$ su - -c 'which dkms'
/usr/sbin/dkms
Since makepkg uses fakeroot (and should never be run as root), ...
https://wiki.archlinux.org/index.php/AUR
What is the proper way to make it work? Thank you.
Last edited by x-yuri (2013-01-29 19:33:44)

It's not my PKGBUILD. It's PKGBUILD, downloaded by abs (community/virtualbox-modules):
# $Id: PKGBUILD 82593 2013-01-21 11:10:44Z tpowa $
# Maintainer: Ionut Biru <[email protected]>
# Maintainer: Sébastien Luttringer <[email protected]>
pkgbase=virtualbox-modules
pkgname=('virtualbox-host-modules' 'virtualbox-guest-modules')
pkgver=4.2.6
pkgrel=4
arch=('i686' 'x86_64')
url='http://virtualbox.org'
license=('GPL')
makedepends=('linux-headers'
"virtualbox-host-dkms>=$pkgver"
"virtualbox-guest-dkms>=$pkgver"
'expac'
'bc')
build() {
_kernver=$(expac -Q '%v' linux-headers)-ARCH
# dkms need modification to be run as user
cp -r /var/lib/dkms .
echo "dkms_tree='$srcdir/dkms'" > dkms.conf
# build host modules
msg2 'Host modules'
dkms --dkmsframework dkms.conf build "vboxhost/$pkgver" -k "$_kernver"
# build guest modules
msg2 'Guest modules'
dkms --dkmsframework dkms.conf build "vboxguest/$pkgver" -k "$_kernver"
package_virtualbox-host-modules(){
_kernver=$(expac -Q '%v' linux-headers)-ARCH
_extraver=extramodules-${_kernver%.*}-ARCH
pkgdesc='Host kernel modules for VirtualBox'
depends=("linux>=${_kernver%.*}" "linux<$(echo "${_kernver%.*}+0.1"|bc)")
replaces=('virtualbox-modules')
conflicts=('virtualbox-modules')
install=virtualbox-host-modules.install
install -dm755 "$pkgdir/usr/lib/modules/$_extraver"
cd "dkms/vboxhost/$pkgver/$_kernver/$CARCH/module"
install -m644 * "$pkgdir/usr/lib/modules/$_extraver"
find "$pkgdir" -name '*.ko' -exec gzip -9 {} +
sed -ie "s/EXTRAMODULES='.*'/EXTRAMODULES='$_extraver'/" "$startdir/virtualbox-host-modules.install"
package_virtualbox-guest-modules(){
_kernver=$(expac -Q '%v' linux-headers)-ARCH
_extraver=extramodules-${_kernver%.*}-ARCH
pkgdesc='Guest kernel modules for VirtualBox'
license=('GPL')
depends=("linux>=${_kernver%.*}" "linux<$(echo "${_kernver%.*}+0.1"|bc)")
replaces=('virtualbox-archlinux-modules')
conflicts=('virtualbox-archlinux-modules')
install=virtualbox-guest-modules.install
install -dm755 "$pkgdir/usr/lib/modules/$_extraver"
cd "dkms/vboxguest/$pkgver/$_kernver/$CARCH/module"
install -m644 * "$pkgdir/usr/lib/modules/$_extraver"
find "$pkgdir" -name '*.ko' -exec gzip -9 {} +
sed -ie "s/EXTRAMODULES='.*'/EXTRAMODULES='$_extraver'/" "$startdir/virtualbox-guest-modules.install"
# vim:set ts=2 sw=2 et:
Could it possibly be that this time makepkg must be run as root?

[J2EE:160167] uses ejb-links but no EJB modules

Dear All
Seeking support/assistance to resolve the below problem. I'm using laster Jdeveloper 11g software publish in 2011.
weblogic.deployment.EnvironmentException: [J2EE:160167]The module abc-ViewController-context-root in application abc_Project1_abc uses ejb-links but no EJB modules were found for this application
Please provide guidelines why this appears and how to resolve it.
Best Regards
Shahebaz Shaikh

The module abc-ViewController-context-root in application abc_Project1_abc uses ejb-links but no EJB modules were found for this application
Is the application deployed as an EAR application with web and ejb modules? If not, deploy as an EAR application.

How to inform the kernel about newly installed STREAMS MODULE?

I made a copy of timod and installed the copy to /kernel/strmod
as a new module (newmod). I modified the t_open.c to make
it to use the "newmod" instead of the timod. The result of the
test is "Invalid Argument". It looks like the kernel doesn't
recognize the module "newmod". I looked throught Sun
Docs, I'm not able to find any instruction for how to
make kernel to recognize my new STREAMS module name
as the add_drv does for device drivers. Can anyone point
me to the right docs and give me some instructions for informing
the kernel about the newly installed STREAMS module?
Thanks
Yuen

Forget my precedent post, here is what's on the configuration page of this module :
("[_]" are checkboxe)
1/ [_] Check this option if your users' DNs look like cn=jdoe,ou=Group1,cn=example,cn=com and Group1 turns out to be the group you want.)
Attribute of the DN which contains the group name:
[Single line text field to enter attribute]
(The name of the attribute which contains the group name. In the example above, it would be ou, as the DN contains the string ou=Group1 and Group1 happens to be the desired group name.
2/ [_] Groups are specified by LDAP attributes
Attribute names (one per line):
[Multi-lines text field]
(If the groups are stored in the user entries, along with the rest of their data, then enter here a list of attributes which may contain them.)
3/ [_] Groups exist as LDAP entries where a multivalued attribute contains the members' CNs
Nodes containing groups (one per line):
[Multi-lines text field]
(Enter here a list of nodes from where groups should be searched for. The module will look them up recursively from the given nodes.)
Attribute holding group members:
[Single line text field]
(Name of the multivalued attribute which holds the CNs of group members, for example: memberUid)
If someone could tell me which checkboxe I should select and what to put into fields it would be king as I really have no idea of what to enter and what to select.

Multiboot kernel must be loaded before modules

Hello,
Does anybody knows what is the problem here.
kernel /I86PC.Solaris_10-1/multiboot kernel/unix - install dhcp -B console=ttya
,install_config=10.203.68.40:/opt/SUN/InstallServer/jumpstart,sysid_config=10.2
03.68.40:/opt/SUN/InstallServer/config/svr101,install_media=10.203.68.40:/opt/S
UN/InstallServer/sol10_8_07_x86,install_boot=::1:/opt/SUN/InstallServer/sol10_8
_07_x86/boot
module /I86PC.Solaris_10-1/x86.miniroot
Error 20: Multiboot kernel must be loaded before modules
It's jumpstart installation.
Thanks
Mario

I am getting similar error after upgrading my jumpserver form solaris 10 u2 to solaris 10 u6.
kernel /I86PC.Solaris_10-3/multiboot kernel/unix -B console=ttya,install_config
=10.2.11.240:/jumpserver/jumpstart,sysid_config=10.2.11.240:/jumpserver/Sysidcf
g/5.10u6/x86,install_media=10.2.11.240:/jumpserver/install/5.10u6/x86,install_b
oot=10.2.11.240:/jumpserver/boot/5.10u6/x86/Solaris_10/Tools/Boot
module /I86PC.Solaris_10-3/x86.miniroot
Error 20: Multiboot kernel must be loaded before modules
Press any key to continue..
ANY Suggestsion ?
Thanks,
W

Kernel panics but no panic log

Hi all,
Have been getting what appear to be random kernel panics, but am having trouble diagnosing because my Beige is generating no panic logs at all.
Panics occur sometimes at startup, very early in boot process (grey screen with spinning wheel, before the blue Mac screen), sometimes in the middle of a work session, sometimes not at all for a day or two. Do not seem to be related to connection of external FW drives.
Have done most of the diagnostic stuff -- checking cables, dust bunnies, restting CUDA, reset NVRAM, disconnecting SCSI scanners, serial modem, USB hub, starting with a fresh user account, etc.
Mostly, would like to know why I'm not getting panic logs, because maybe this indicates the root of the problem?
Thanks,
Tina

Thanks, Tom,
I hadn't thought about that. Just assumed that XPostFacto, by enabling Panther, would enable all of Panther. All the other logs are generated just fine. I'll check back at my usual place on the Beige forums and see if others get panic logs or not.
That particular Beige Mac of mine is at its busiest work period of the year, so removing/testing RAM will have to wait until after the holidays. But running DIM First Aid shows no problem. Guess I'll go ahead and run TTP4's RAM tests.
I'm also wondering if perhaps a failing PRAM battery might be causing these hiccups, but the symptoms aren't usually kernel panics.
Thanks for the suggestions,
Tina

[solved] kernel 3.2.8 fails with loading nvidia and virtualbox modules

Topic says it. I just updated from kernel 3.2.7 to 3.2.8 and X won't start. The kernel fails to load the nvidia module with the follwing error: 'Exec format error'. Same for the virtualbox kernel modules. This is on x86_64, multilib and all testing repos enabled.
Downgrade to 3.2.7 by
pacman -S core/linux
solves the issue.
Last edited by Harey (2012-02-28 18:55:36)

Allan wrote:Bug tracker...
https://bugs.archlinux.org/task/28695

Virtualbox module won't compile?

I upgraded Virtualbox from 4.0.10 to 4.0.12 and I am receiving an error when trying to compile the module by /etc/rc.d/vboxdrv setup.
The contents of /var/log/vbox-install.log are :
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.39-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/include -I/usr/src/linux-2.6.39-ARCH/arch/x86/include -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=1024 -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/2.6.39-ARCH/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
In file included from /tmp/vbox.0/include/VBox/types.h:34:0,
from /tmp/vbox.0/linux/../SUPDrvInternal.h:39,
from /tmp/vbox.0/linux/SUPDrv-linux.c:37:
/tmp/vbox.0/include/iprt/types.h:87:30: fatal error: linux/autoconf.h: No such file or directory
compilation terminated.
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2
Where do I start to repair this?
Thank You
Last edited by glenn69 (2011-07-18 17:57:37)

I had a breakthrough, although I'm not sure what it means...other than Virtualbox now runs again.
Here's what I did:
downgraded glibc to 2.12.1-2 ( and any other files with dependencies. gcc, gcc-libs, binutils )
still had no luck compiling module
then I downgraded back to Virtualbox 4.0.10 again with the downgraded glibc
..and it worked. Hopefully someone can make some sense of it for the rest of us.
Summation: Virtualbox 4.0.12 did not compile with glibc at 2.12.1-2 or at its most current version
Virtualbox 4.0.10 would not compile with a current version of glibc ( >2.12.1-2)
..but VB 4.0.10 did compile fine with glibc downgraded to 2.12.1-2
Last edited by glenn69 (2011-07-18 20:13:00)

[kernel] kernel update and third party modules management

Hi all,
I turned to Archlinux with my new thinkpad X220 just for a few days, while I have used Ubuntu for 4 years. I had never controlled my system in such a degree, and feel happy about it.
However, I have a question about kernel update, for I had install some modules from AUR with yaourt( e.g. tp_smapi, acpi_call). For my poor knowledge about pacman, I don't know how to handle those modules while I upgrade my kernel. I cannot remember to re-install all of them!
I think there must be a solution that I didn't found, so I write this thread to ask for help.
Any help would be appreciate.

Mr.Elendig wrote:You can use some silly wrapper around pacman that rebuilds them when there is a kernel update. I'm sure someone has written one already.
Thank you, Mr.Elendig. Do you mean some kind of frontend such as yaourt?
Or some kind of hooks like this:
aur/mkinitcpio-vbox 2.0-3 (Out of Date) (29)
VirtualBox hook for mkinitcpio that rebuilds kernel modules on next reboot
Using the key words you provided, I searched " kernel upgrade module rebuild " and found that gentoo offically provide a tool called "module-rebuild" to reinstall external modules. Maybe it's because gentoo always compile source code? But no other results.
However, now I found what I need to do is just to build the modules listed in the /etc/rc.conf, and that is acceptable. Maybe after a few weeks of study, I can find out my way to solve this problem.
And thanks for your reply.
Last edited by ywarlock (2012-03-09 16:20:36)

Kernel 25 but no virtualbox-modules

Similar Messages

Maybe you are looking for