David Baron wrote:
> On Wednesday 06 June 2007, Brian Green wrote:
>> David Baron wrote:
>>> On Wednesday 06 June 2007, Frank Mehnert wrote:
>>>> On Wednesday 06 June 2007, David Baron wrote:
>>>>> Use the init.d script. It first disables NMI. I would suppose that if
>>>>> NMI is active, modprobe alone would fail.
>>>> No, it does not. Please add the kernel parameter 'nmi_watchdog=0' (at
>>>> the kernel command line when booting the kernel. We will try to disable
>>>> the watchdog in from within the module in the next release.
>>> I get the message,
>>> "Trying to permamently stop nmi watchdog ...."
>>> "successful"
>>> From the init script.
>>>
>>> Putting it in the commandline is a good idea. How do I get there from a
>>> simple menu in lilo? options: nmi_watchdog=0 ?
>> Yeah - I can confirm that "/etc/init.d/vboxdrv start" {etc} fails.
> Mine works
>
>> Similarly, how do I insert the "nmi_watchdog=0" in the command line - I
>> use grub.
> For lilo, I am trying append="nmi_watchdog=0"
>
OK. Entered "nmi_watchdog=0" into grub (using YaST).
Apart from (now) getting the old "Could not load the Host USB Proxy
Service" message, starting a session now gives:
"
Unknown error initializing kernel driver (VERR_VM_DRIVER_VERSION_MISMATCH).
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
"
Brian
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
