You are not logged in.
I just did an upgrade, with new kernel 2.6.23 and my virtualbox install is now giving me an error for the vboxdrv module.
when i try to modprobe vboxdrv it can't find it. This was working fine before the upgrade.
Do I need to build VirtualBox from source?
Offline
virtualbox is built against kernel26 from current.. you can either build your own module, wait for 2.6.23 to go to current, or downgrade your kernel
Offline
Try:
sudo /usr/bin/vbox_build_module
or as root if you don't use sudo.
Offline
That's strange. I thought I was running current. pacman upgraded me to the new kernel, I didn't ask for it.
Doesn't "pacman -Syu" upgrade your system from current if you only have the core, extra, and community servers added in pacman.conf?
man_man22: some suggested that on IRC, but i do not have that script. I'm running the standard OSE.
PS: A lot of these suggestions make me wonder if I really understand how Arch works.
Last edited by efleming969 (2007-10-22 12:13:35)
Offline
Doesn't "pacman -Syu" upgrade your system from current if you only have the core, extra, and community servers added in pacman.conf?
man_man22: some suggested that on IRC, but i do not have that script. I'm running the standard OSE.
The new kernel 2.6.23.1-3 is in core (look here: http://www.archlinux.org/packages/13318/). So everything was alright with your update.
The package "virtualbox-ose-additions-modules" must be rebuild in the community repo. It is built against kernel-2.6.22, that's wrong. Rebuild it on your own or flag the package out-of-date.
Offline
ok, that make me feel better. the package is already marked out of date.
i suppose, for an app as mission critical as virtualbox is to me (need for work), i need to pay more attention to upgrading my kernel at least with archlinux (there is not a way to simply revert back to a different kernel, like in debian).
thanks for the input.
Offline
... (there is not a way to simply revert back to a different kernel, like in debian)
That depends on the meaning of "simple". If you don't erase cached pacman packages you can always simply rollback to a previously installed kernel; you find cached packages at "var/cache/pacman/pkg".
If you cd to that directory you could simply "ls kernel*", to see what previous kernel package you have. After that you could rollback by "pacman -U kernel[...correct version number here...]".
Complicated or simple?
Offline
KimTjik,
Simple! once you know how to do it. I love learning new things in Linux :-)
Thanks alot!
BTW, I think debian's way is more simple since you can choose at grub boot, but then you have to manually clean the mess left over time.
Offline