Virtualbox doesn't like kernel 3.2

Post your update and upgrade related errors here
Forum rules
Before you post please read this

Virtualbox doesn't like kernel 3.2

Postby mint123 on Sun Feb 26, 2012 5:29 pm

Anyone else see this problem? Upgraded from 3.0 to 3.2 a few days ago, I had virtualbox 4.1.0 installed. With the new kernel, I got a virtualbox-dkms error. I uninstalled and reinstalled virtualbox-dkms. no change.

So i upgraded Virtualbox wih Oracle's repository for Debian Squeeze to 4.1.8. It actually uninstalled virtualbox-dkms and a few other things. Dkms is only in Synaptic for version 4.1.0 and it wouldn't configure itself to work with 3.2, just kernel 3.0. All works fine though, with virtualbox 4.1.8, virtualbox-dkms 4.1.0 and kernel 3.0.0.1 but I'd like to use the new kernel.

I think it's a Vbox limitation for now though. I'm using all the Mint Lateset repositories. Something from the other day's updates also messed up Cairo Dock. I had to restore all my old settings to it. here's what Synaptic says was in the update,

Code: Select all
Upgraded the following packages:
dpkg-dev (1.16.0.3) to 1.16.1.1~bpo60+2
extlinux (2:4.04+dfsg-3) to 2:4.04+dfsg-9~bpo60+1
libdpkg-perl (1.16.0.3) to 1.16.1.1~bpo60+2
libjs-jquery (1.6.2-1) to 1.6.4-1~bpo60+1
libnss3-1d (3.12.11-1) to 3.13.1.with.ckbi.1.88-1~bpo60+1
libtdb1 (1.2.9-3) to 1.2.9-4~bpo60+1
linux-base (3.3) to 3.4~bpo60+1
linux-headers-amd64 (3.0.0+39) to 3.2+42~bpo60+1
linux-image-amd64 (3.0.0+39) to 3.2+42~bpo60+1
linux-libc-dev (3.0.0-1) to 3.2.4-1~bpo60+1
python-mako (0.4.2-1) to 0.5.0-1~bpo60+1
syslinux (2:4.04+dfsg-3) to 2:4.04+dfsg-9~bpo60+1
syslinux-common (2:4.04+dfsg-3) to 2:4.04+dfsg-9~bpo60+1
ttf-opensymbol (2:2.4.3+LibO3.3.3-4) to 2:2.4.3+LibO3.4.3-3~bpo60+1
uno-libs3 (1.7.0+LibO3.3.3-4+b1) to 3.4.3-3~bpo60+1
ure (1.7.0+LibO3.3.3-4+b1) to 3.4.3-3~bpo60+1
usb-modeswitch (1.1.9-2) to 1.2.0+repack0-1~bpo60+1
usb-modeswitch-data (20110805-1) to 20111023-1~bpo60+1

Installed the following packages:
linux-headers-3.2.0-0.bpo.1-amd64 (3.2.4-1~bpo60+1)
linux-headers-3.2.0-0.bpo.1-common (3.2.4-1~bpo60+1)
linux-image-3.2.0-0.bpo.1-amd64 (3.2.4-1~bpo60+1)
linux-kbuild-3.2 (3.2.1-2~bpo60+1)
mint123
Level 3
Level 3
 
Posts: 133
Joined: Mon Jan 31, 2011 4:44 pm

Linux Mint is funded by ads and donations.
 

Re: Virtualbox doesn't like kernel 3.2

Postby vanDoom on Sun Feb 26, 2012 10:25 pm

Wow I didn't know you could update your kernel from underneath the OS. I just downloaded 3.2.7 from kernel.org, and will see about this myself :D maybe I'll check back later if I try to test out your Virtualbox issues.
User avatar
vanDoom
Level 1
Level 1
 
Posts: 47
Joined: Sun Feb 26, 2012 7:25 pm
Location: USA

Re: Virtualbox doesn't like kernel 3.2

Postby Transitman on Mon Feb 27, 2012 1:51 am

mint123 wrote:Anyone else see this problem? Upgraded from 3.0 to 3.2 a few days ago, I had virtualbox 4.1.0 installed. With the new kernel, I got a virtualbox-dkms error. I uninstalled and reinstalled virtualbox-dkms. no change.

So i upgraded Virtualbox wih Oracle's repository for Debian Squeeze to 4.1.8. It actually uninstalled virtualbox-dkms and a few other things. Dkms is only in Synaptic for version 4.1.0 and it wouldn't configure itself to work with 3.2, just kernel 3.0. All works fine though, with virtualbox 4.1.8, virtualbox-dkms 4.1.0 and kernel 3.0.0.1 but I'd like to use the new kernel.

I think it's a Vbox limitation for now though. I'm using all the Mint Lateset repositories. Something from the other day's updates also messed up Cairo Dock. I had to restore all my old settings to it. here's what Synaptic says was in the update,


I'm running a Liquorix 3.2 kernel and virtualbox balked once on me, but I did a re-install and everything is running smooth.
Transitman
Level 2
Level 2
 
Posts: 98
Joined: Sun Dec 02, 2007 1:48 am

Re: Virtualbox doesn't like kernel 3.2

Postby cooleric1234 on Sat Mar 17, 2012 10:28 pm

I just started tracking SID the other day and had a few VirtualBox problems. I kind of wish I hadn't done this but I ended up removing it then installing the .run version (not the .deb). In the end I was struggling with USB support and all I really had to do was log the user out and in again after adding him to the vboxusers group. I had done that long ago but something with the update made that setting get changed. Anyway, it's working fine now but it's not tracked in the repository. I don't worry too much about that though because that program tends to follow the Windows methodology of checking by itself for updates and prompting you to upgrade.
cooleric1234
Level 1
Level 1
 
Posts: 36
Joined: Sat Sep 10, 2011 9:48 pm


Return to Update/Upgrade Issues

Who is online

Users browsing this forum: No registered users and 4 guests