You are not logged in.
Today I did pacman -Syu and got:
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-modules: requires kernel26<2.6.28
So do I need to wait until virtualbox is updated or I have to force update and recompile virtualbox modules?
Offline
I'm not sure virtualbox modules actually compile with kernel 2.6.28... so you might want to wait. You can add kernel26 (and modules) to your IgnorePkg in makepkg.conf until you are fine to upgrade.
Offline
Thanks a lot!
What I do is just ignore the updates until the problems is solved, because current system is sufficient for my study/work, no updates are needed from my point of view. A system that fulfills my needs is just enough, further updates may give me new features which I do not need, and may even breaks the system. But how comes I cannot preventing me running pacman -Syu several times a day?
Offline
virtualbox-ose should be updated to 2.1.0, as the modules can be compiled
Give what you have. To someone, it may be better than you dare to think.
Offline
hehehe me too... pacman -Syu all day long
though I was smart enough to WAIT until evening to update kernel yesterday
So... ONLY real problem is VIRTUALBOX
anyone know what to do to get it working again...?
Reinstall?
something else?
interested in new version as well!
thakn you ...any tips for getting vbox going again...
ON boot screen says something about vboxsrv I think not loading/found or similar.
Offline
I am using virtualbox-bin 2.1, and works fine.
Try as root:
vbox_build_module
and
modprobe vboxdrv
Excuse my poor English.
Offline
right thanks...!! just got back here after success myself...
I uninstalled what I could after doing
pacman -Ss virtualbox
noting what I might have earlier installed
then did the
yaourt -S virtualbox_bin
WOW just worked... everything...!
Offline
I used to use Ubuntu and faced the same problem, what Ubuntu did is, when it finds the kernel version does not match virtualbox modules, it automatically builds the needed modules. I hope arch has similar features(ie scripts) that does the job.
Offline
Well .... OSS does that .... it did that with this last kernel update, with virtualvox it is clearly stated when you install it that you need to run vbox_build_module as root when you update the kernel. I don't see a problem there .... things that automagically work will go wrong sooner than later and will most probably slow your pc to a crawl as many distros do these days .... thankfully Arch is not like that and you are in control. With control comes the responsibility of fixing things when and if they do break.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Would be nice if they would simply update VirtualBox since 2.0.4 is in the repository and 2.1.0 has been released a while ago... But I think you're not supposed to use 'Bugs' for 'out-of-date' reports, so I guess that's not an option.
Do you want a Bubble Icon? Feel free to submit your requests or personal creations to be included in future releases.
I'm 100% Linux!
Offline
From yaourt search: aur/virtualbox_bin 2.1.0-2. I don't see a version 2.0.4 in the repos or AUR? I have virtualbox_bin and kernel 2.6.28 and after a vbox_build_module and modprobe vboxdrv, it all worked fine.
Scott
Last edited by firecat53 (2009-01-19 14:43:41)
Offline
There is a MAJOR difference between the OSE and PUEL, people. Switching to the PUEL is not a "solution" to this problem.
Being patient, however, is.
M*cr*s*ft: Who needs quality when you have marketing?
Offline
... but it is a nice workaround though
Do you want a Bubble Icon? Feel free to submit your requests or personal creations to be included in future releases.
I'm 100% Linux!
Offline
here's a patch for the virtualbox-modules PKGBUILD from ABS:
--- /var/abs/community/modules/virtualbox-modules/PKGBUILD 2008-11-12 06:47:12.000000000 +0100
+++ PKGBUILD 2009-01-21 13:46:08.000000000 +0100
@@ -6,14 +6,14 @@
# Contributor: Ingmar Steen
pkgname=virtualbox-modules
-_kernver=2.6.27-ARCH
-pkgver=2.0.4
+_kernver=`uname -r`
+pkgver=2.1.0
pkgrel=1
pkgdesc="Kernel modules for VirtualBox (vboxdrv)"
arch=('i686')
url="http://www.virtualbox.org"
license=('GPL')
-depends=('kernel26>=2.6.27' 'kernel26<2.6.28')
+depends=('kernel26>=2.6.27')
makedepends=('bin86' 'dev86' 'iasl' 'libstdc++5' 'qt3' 'sdl_ttf' 'libxt'
'libgl' 'alsa-lib' 'pulseaudio' 'gcc34' 'libxcursor' 'libidl2' 'libxslt'
'xalan-c' 'pth' 'libxml2' 'libidl2' 'libpng')
@@ -41,4 +41,4 @@
install -D -m644 vboxdrv.ko "$pkgdir/lib/modules/${_kernver}/misc/vboxdrv.ko"
sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" "$startdir/virtualbox-modules.install"
}
-md5sums=('89db3f4a227f97c1e080035fbadd10c8')
+md5sums=('4d8f857c9ead892607387656a9e895bb')
and this is for virtualbox-ose:
--- /var/abs/community/emulators/virtualbox-ose/PKGBUILD 2008-11-12 06:30:45.000000000 +0100
+++ PKGBUILD 2009-01-21 14:43:57.000000000 +0100
@@ -4,7 +4,7 @@
# Contributor: Michal Krenek <mikos@sg1.cz>
# Contributor: niQo
pkgname=virtualbox-ose
-pkgver=2.0.4
+pkgver=2.1.0
pkgrel=1
pkgdesc="Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)"
url="http://www.virtualbox.org"
@@ -70,5 +70,5 @@
install -D -m644 "$srcdir/60-virtualbox.rules" \
"$pkgdir/etc/udev/rules.d/60-virtualbox.rules"
}
-md5sums=('89db3f4a227f97c1e080035fbadd10c8'
- '519d32d8c2408e0ed9d643f412117644')
+md5sums=('4d8f857c9ead892607387656a9e895bb'
+ '519d32d8c2408e0ed9d643f412117644')
by the way, there's still a warning at compile time "hardening is disabled, you shouldn't build vbox for distributions without hardening". anybody know the right way to fix this without breaking vbox?
Last edited by schuay (2009-01-21 14:13:14)
Offline