Brian Green wrote:
> 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.
>>
> 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
>
D'oh! dmesg gives:
"
ioctl32(VirtualBox:5175): Unknown cmd fd(3) cmd(c0102201){00}
arg(fff4d408) on / dev/vboxdrv
ioctl32(VirtualBox:5391): Unknown cmd fd(3) cmd(c0102201){00}
arg(ffeddb08) on / dev/vboxdrv
ioctl32(VirtualBox:5406): Unknown cmd fd(29) cmd(c0102201){00}
arg(f40d8058) on /dev/vboxdrv
"
Brian
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
