Problem with enabeling vboxdrv

kaifis · 2017-06-27 10:09:41

Hi,
I've been trying to install virtualbox. I followed official wiki - https://wiki.archlinux.org/index.php/VirtualBox.
But when tried:

% sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
% dmesg | tail
[  155.010559] wlp2s0: authenticate with 98:de:d0:ad:bb:cc
[  155.013786] wlp2s0: send auth to 98:de:d0:ad:bb:cc (try 1/3)
[  155.023814] wlp2s0: authenticated
[  155.026912] wlp2s0: associate with 98:de:d0:ad:bb:cc (try 1/3)
[  155.031504] wlp2s0: RX AssocResp from 98:de:d0:ad:bb:cc (capab=0x431 status=0 aid=1)
[  155.037030] wlp2s0: associated
[  155.037068] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  185.955472] vboxdrv: disagrees about version of symbol module_layout
[  412.746279] vboxdrv: disagrees about version of symbol module_layout
[  467.102558] vboxdrv: disagrees about version of symbol module_layout

I've been googling it for several days and somewhere I found that this problem is connected with linux headers so I tried:

% pacman -Q | grep linux headers
%

Thanks in advance.

EDIT:

% pacman -Qi virtualbox-host-modules-arch
Name            : virtualbox-host-modules-arch
Version         : 5.1.22-4
Description     : Virtualbox host kernel modules for Arch Kernel
Architecture    : x86_64
URL             : http://virtualbox.org
Licenses        : GPL
Groups          : None
Provides        : VIRTUALBOX-HOST-MODULES
Depends On      : linux>=4.11  linux<4.12
Optional Deps   : None
Required By     : virtualbox
Optional For    : None
Conflicts With  : virtualbox-modules  virtualbox-host-modules  virtualbox-host-dkms
Replaces        : virtualbox-modules  virtualbox-host-modules
Installed Size  : 181.00 KiB
Packager        : Tobias Powalowski <tpowa@archlinux.org>
Build Date      : Wed 14 Jun 2017 08:33:31 PM CEST
Install Date    : Tue 27 Jun 2017 01:52:28 PM CEST
Install Reason  : Installed as a dependency for another package
Install Script  : Yes
Validated By    : Signature

% uname -a
Linux mibook 4.11.3-1-ARCH #1 SMP PREEMPT Sun May 28 10:40:17 CEST 2017 x86_64 GNU/Linux
%

Last edited by kaifis (2017-06-27 11:29:55)

Trilby · 2017-06-27 11:08:45

Is this still a Manjaro system?

Please edit your post an use code tags - you have been instructed to do so previously. As for the pacman -Q command, post the exact command and complete output - I'm qute sure you didn't get "nothing".

Also post your pacman.conf and the output of the following:

pacman -Qi virtualbox-host-modules-arch
uname -a

kaifis · 2017-06-27 11:32:23

Trilby wrote:

Is this still a Manjaro system?

No, I installed arch linux three weeks ago.

Last edited by kaifis (2017-06-27 11:32:34)

Trilby · 2017-06-27 11:51:43

Thanks for the edits. While I'm not sure if it's related to the actual problem here, something is very wrong with your output from `pacman -Q | grep linux headers` which is why I wanted the exact command and full output. Now that you've provided that, it makes even less sense. Is there a file in the working directory named "headers"? If so, you are not actually grepping the pacman output, you are just grepping that file for the word "linux". If there is no file named "headers" in the working directory, you would get an error message from grep.

loqs · 2017-06-27 12:09:02

https://git.archlinux.org/svntogit/comm … 4d7da55333 Appears to be a partial upgrade.

Trilby · 2017-06-27 12:25:45

Loqs, are you infering that from the running kernel version? If so it *might* be a partial upgrade, but it would more likely be just that the OP hasn't rebooting into the new kernel.

I was suspecting the latter might be the case - and kaifis you should reboot into the new kernel to try this out - but if that was the problem, I'm pretty sure the error from modbrobe would be different (something along the lines of the module not being found, not an exec format error).

Although, I suppose the exec format error might be the expected result from a partial upgrade (I'm not sure).

loqs · 2017-06-27 14:55:08

Trilby yes from the running kernel version. The pacman -Qi output for whatever package if any is providing the kernel or the system's pacman.log would help clarify the issue.

kaifis · 2017-06-28 09:38:25

Hi, don't know how to boot into the new kernel. I haven't installed new kernel. But problem solved by

% sudo pacman -Syu

Thanks for help.

Last edited by kaifis (2017-06-28 09:38:40)

Arch Linux

#1 2017-06-27 10:09:41

Problem with enabeling vboxdrv

#2 2017-06-27 11:08:45

Re: Problem with enabeling vboxdrv

#3 2017-06-27 11:32:23

Re: Problem with enabeling vboxdrv

#4 2017-06-27 11:51:43

Re: Problem with enabeling vboxdrv

#5 2017-06-27 12:09:02

Re: Problem with enabeling vboxdrv

#6 2017-06-27 12:25:45

Re: Problem with enabeling vboxdrv

#7 2017-06-27 14:55:08

Re: Problem with enabeling vboxdrv

#8 2017-06-28 09:38:25

Re: Problem with enabeling vboxdrv

Board footer