Summary: | app-emulation/virtualbox-1.5.2: no module available for the current kernel | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | FieldySnuts <sgtphou> |
Component: | Current packages | Assignee: | Markus Ullmann (RETIRED) <jokey> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | swapon |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
FieldySnuts
2007-10-27 19:41:15 UTC
I forgot to mention that it's not the NMI watchdog issue. I have that disabled at boot time. I just did a large number of updates, did a reboot, same issue. Really trivial: current is mis-spelt as "currente" in the error output ;p Cheers. I've found the issue. I run virtualbox as a normal user. The wrapper script checks to see if the vboxdrv kernel driver exists. On my system only root has any access to the kernel modules. Giving my user read access to the diretory tree and that module solved the issue. This might cause problems for other users who are paranoid like myself, and don't let normal users read modules. I'm not sure what to resolve this as so I'll let you gentlemen decide that. Hi, (In reply to comment #1) > I forgot to mention that it's not the NMI watchdog issue. I have that disabled > at boot time. I just did a large number of updates, did a reboot, same issue. the NMI watchdog workaround is no more needed for virtualbox-modules, and was intended only for amd64 systems. > Really trivial: current is mis-spelt as "currente" in the error output ;p > fixed on jokey's overlay[1] for both virtualbox and virtualbox-bin (In reply to comment #2) > I've found the issue. I run virtualbox as a normal user. The wrapper script > checks to see if the vboxdrv kernel driver exists. On my system only root has > any access to the kernel modules. Giving my user read access to the diretory > tree and that module solved the issue. > > This might cause problems for other users who are paranoid like myself, and > don't let normal users read modules. imho that check in the wrapper is fine, because 0644 is the standard permission mask for all the other modules in: /lib/modules/`uname -r`/ Unluckily as normal user is not easy to find another "effective 100% bomb proof" method to test the existence of the vboxdrv for the current kernel :) Thanks for reporting this issues. [1] http://overlays.gentoo.org/dev/jokey/browser/trunk/app-emulation Fixes applied to CVS, thanks :) |