[arch-general] Virtual Box Update Fails
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2 Total Installed Size: 66.86 MiB Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.* Can I move those files? Regards, Victor
Op 16/06/12 18:36, Victor Silva schreef:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor https://bbs.archlinux.org/viewtopic.php?id=56373
Op zaterdag 16 juni 2012 13:36:17 schreef Victor Silva:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor
did you build the modules manually before ? you could fix your problem by issuing: pacman -Sf virtualbox-modules --Ike
2012/6/16 Ike Devolder <ike.devolder@gmail.com>
Op zaterdag 16 juni 2012 13:36:17 schreef Victor Silva:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor
did you build the modules manually before ?
you could fix your problem by issuing: pacman -Sf virtualbox-modules
--Ike
Guys thanks a lot for the insigths your tips did the trick. I could not look on the forums befor as my system got mangled by the last kernel update and just now I was able to get an X server and internet running again. Regards, Victor
2012/6/16 Victor Silva <vfbsilva@gmail.com>
2012/6/16 Ike Devolder <ike.devolder@gmail.com>
Op zaterdag 16 juni 2012 13:36:17 schreef Victor Silva:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor
did you build the modules manually before ?
you could fix your problem by issuing: pacman -Sf virtualbox-modules
--Ike
Guys thanks a lot for the insigths your tips did the trick. I could not look on the forums befor as my system got mangled by the last kernel update and just now I was able to get an X server and internet running again.
Regards, Victor
I'm back to the issues: VirtualBox is not currently allowed to access USB devices. You can change this by allowing your user to access the 'usbfs' folder and files. Please see the user manual for a more detailed explanation. Still looking on the manual. Anyone got a quick fix?
On 06/16/2012 11:10 PM, Victor Silva wrote:
2012/6/16 Victor Silva <vfbsilva@gmail.com>
2012/6/16 Ike Devolder <ike.devolder@gmail.com>
Op zaterdag 16 juni 2012 13:36:17 schreef Victor Silva:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor
did you build the modules manually before ?
you could fix your problem by issuing: pacman -Sf virtualbox-modules
--Ike
Guys thanks a lot for the insigths your tips did the trick. I could not look on the forums befor as my system got mangled by the last kernel update and just now I was able to get an X server and internet running again.
Regards, Victor
I'm back to the issues:
VirtualBox is not currently allowed to access USB devices. You can change this by allowing your user to access the 'usbfs' folder and files. Please see the user manual for a more detailed explanation.
Still looking on the manual. Anyone got a quick fix?
add your user to vboxusers group, relogin and that's it. -- Ionuț
2012/6/16 Ionut Biru <ibiru@archlinux.org>
On 06/16/2012 11:10 PM, Victor Silva wrote:
2012/6/16 Victor Silva <vfbsilva@gmail.com>
2012/6/16 Ike Devolder <ike.devolder@gmail.com>
Op zaterdag 16 juni 2012 13:36:17 schreef Victor Silva:
Folks with the last kernel I can no longer build virtualbox, here is the error log: *Targets (2): virtualbox-4.1.16-1 virtualbox-modules-4.1.16-2
Total Installed Size: 66.86 MiB
Proceed with installation? [Y/n] y (0/2) checking package integrity (1/2) checking package integrity (2/2) checking package integrity (0/2) loading package files (1/2) loading package files (2/2) loading package files (0/2) checking for file conflicts (1/2) checking for file conflicts (2/2) checking for file conflicts error: failed to commit transaction (conflicting files) virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxdrv.ko.gz exists in filesystem virtualbox-modules:
/lib/modules/extramodules-3.4-ARCH/vboxnetadp.ko.gz
exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxnetflt.ko.gz exists in filesystem virtualbox-modules: /lib/modules/extramodules-3.4-ARCH/vboxpci.ko.gz exists in filesystem Errors occurred, no packages were upgraded.*
Can I move those files?
Regards, Victor
did you build the modules manually before ?
you could fix your problem by issuing: pacman -Sf virtualbox-modules
--Ike
Guys thanks a lot for the insigths your tips did the trick. I could not look on the forums befor as my system got mangled by the last kernel update and just now I was able to get an X server and internet running again.
Regards, Victor
I'm back to the issues:
VirtualBox is not currently allowed to access USB devices. You can change this by allowing your user to access the 'usbfs' folder and files. Please see the user manual for a more detailed explanation.
Still looking on the manual. Anyone got a quick fix?
add your user to vboxusers group, relogin and that's it.
-- Ionuț
That did the trick thanks a lot!
participants (4)
-
Ike Devolder
-
Ionut Biru
-
Jochen Maes (Gcool)
-
Victor Silva