[SOLVED] Kernel 3.1 Required for Virtualbox Update?

jlacroix · 2011-11-09 00:06:25

When trying to update today, I get this:

error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-modules: requires linux>=3.1

I usually don't upgrade the kernel right away. In fact, I normally put kernel and kernel-header on ignore and only update after a few point releases are out. Does this mean that in order to continue using Virtualbox I'll need to update the kernel? I never had to before.

Last edited by jlacroix (2011-11-09 07:28:06)

karol · 2011-11-09 00:11:21

Any reason for your do-not-update-kernel policy?
You don't need to upgrade VirtualBox either.

jlacroix · 2011-11-09 00:18:28

I always seem to have issues with .0 or. 1 kernels on my laptop. Especially problems with suspend to RAM. It seems each .0 kernel release breaks suspend and its fixed later. Among other annoying glitches. With Virtualbox I like to take advantage of the new features, and I've always been able to do this.

karol · 2011-11-09 00:25:39

http://www.archlinux.org/packages/commu … x-modules/
Dependencies:
linux>=3.1
linux<3.2

This package is pretty picky wrt who it is friends with.

There has recently been a change in packaging: http://projects.archlinux.org/svntogit/ … bb4f5c8db5 but you will have to wait for wonder to drop by if you want a definitive answer (he's the maintainer).

wonder · 2011-11-09 00:44:56

jlacroix wrote:

I always seem to have issues with .0 or. 1 kernels on my laptop. Especially problems with suspend to RAM. It seems each .0 kernel release breaks suspend and its fixed later. Among other annoying glitches. With Virtualbox I like to take advantage of the new features, and I've always been able to do this.

unless you want to recompile every single time the modules when a new kernel is released , i mean literally every release, even pkgrel bumps, you can use virtualbox-source and old vboxbuild.

virtualbox-modules was introduced just to avoid this issue because uname -r returns full package version

$ uname -r 
3.1.0-4-ARCH

$ pacman -Q linux
linux 3.1-4

You can work around by doing

# pacman -S virtualbox virtualbox-source

jlacroix · 2011-11-09 01:51:17

Thanks for the replies everyone. But I'm still confused. Has something changed upstream? I never noticed a particular kernel version being required before. After updating the kernel I'd have to recompile the virtualbox module by running "/usr/bin/vboxbuild" but that was the extent of it, and it was no big deal to me.

karol · 2011-11-09 02:25:41

jlacroix wrote:

Has something changed upstream? I never noticed a particular kernel version being required before.

'uname -r' now returns the full version .e.g 3.1.0-4-ARCH instead of 3.1-ARCH - that's the new thing.

Check e.g. https://bugs.archlinux.org/task/25727 how it was before:

Gerhard Brauer (GerBra) wrote:

So: any reason why uname -r reports 3.0-ARCH instead 3.0.2-ARCH ?

karol wrote:

so that the modules don't need to be rebuilt on every minor kernel release

jlacroix · 2011-11-09 07:27:49

Thanks everyone for responding. I get it now but I wish it wasn't the way it was. I'll look for a way around this, but until then, thanks again.

Arch Linux

#1 2011-11-09 00:06:25

[SOLVED] Kernel 3.1 Required for Virtualbox Update?

#2 2011-11-09 00:11:21

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#3 2011-11-09 00:18:28

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#4 2011-11-09 00:25:39

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#5 2011-11-09 00:44:56

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#6 2011-11-09 01:51:17

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#7 2011-11-09 02:25:41

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

#8 2011-11-09 07:27:49

Re: [SOLVED] Kernel 3.1 Required for Virtualbox Update?

Board footer