[Fixed] : Virtualbox 4.2.0 ebuild - module version conflict

lyallp · Last edited by lyallp on Fri Sep 14, 2012 10:41 am; edited 2 times in total

It installed, I re-loaded the kernel modules, but there is something wrong.

VM's won't start because it seems to think the kernel is running modules 4.1, not 4.2

In desperation, I even tried rebooting.

I ended up masking 4.2.0 (it's already ~amd64)
_________________
...Lyall

DawgG · Guru Joined: 17 Sep 2003 Posts: 551

maybe you have forgotten to emerge app-emulation/virtualbox-modules?
i use virtualbox-bin and the corresponding modules always have to emerged separately. also you mgiht have to check the kernel-version and the /usr/src/linux-symlink
GOOD LUCK!
_________________
DUMM KLICKT GUT.

Polynomial-C · Posted: Fri Sep 14, 2012 8:27 am Post subject:

This is bug 434958 which has already been fixed.
_________________
The manual said "Requires Windows7 or better" so I installed GNU/Linux...

my portage overlay

Need a stage1 tarball? (Unofficial builds)

lyallp · Posted: Fri Sep 14, 2012 10:40 am Post subject:

Thanks, I notice the 4.2.0-r1, quick work.

When I get back to the affected computer, I will have to change my mask, as I masked virtualbox, not virtualbox-modules.

_________________
...Lyall