Prev: restart fbi
Next: Type ahead change in Slack 13
From: barnabyh on 28 Nov 2009 14:16
Hi all,

I previously had VB 3.0.8 working well with the stock kernel in 13.
When updating the kernel to 2.6.30.5 from /testing I also decided to
upgrade VB to 3.0.12.
Now the kernel driver is not loading any more despite

> # Start vboxdrv
> # If you do not wish this to be executed here then comment it out,
> # and the installer will skip it next time.
> if [ -x /etc/rc.d/rc.vboxdrv ]; then
> /etc/rc.d/rc.vboxdrv start
> fi

in rc.local.

Getting plenty of error messages on startup when probing for / updating
new kernel modules, all seemingly I/O related (UMDA 133). Has anyone
else encountered this?
By now I have attempted this several times, also with VB 3.0.10, with
the same results. Using the binary for all distributions, AMD64, from VB
website, not the OSE Slackbuild as it is supposed not to build on 64 bit.

These days a virtualisation tool is quite essential so I'm trying to get
this solved on my main machine.

Thanks in advance.

Barnabyh
From: goarilla on 28 Nov 2009 18:13
On Sat, 28 Nov 2009 19:16:07 +0000, barnabyh wrote:

> Hi all,
>
> I previously had VB 3.0.8 working well with the stock kernel in 13.
> When updating the kernel to 2.6.30.5 from /testing I also decided to
> upgrade VB to 3.0.12.
> Now the kernel driver is not loading any more despite
>
>> # Start vboxdrv
>> # If you do not wish this to be executed here then comment it out, #
>> and the installer will skip it next time. if [ -x /etc/rc.d/rc.vboxdrv
>> ]; then
>> /etc/rc.d/rc.vboxdrv start
>> fi
>
> in rc.local.
>
> Getting plenty of error messages on startup when probing for / updating
> new kernel modules, all seemingly I/O related (UMDA 133). Has anyone
> else encountered this?
> By now I have attempted this several times, also with VB 3.0.10, with
> the same results. Using the binary for all distributions, AMD64, from VB
> website, not the OSE Slackbuild as it is supposed not to build on 64
> bit.
>
> These days a virtualisation tool is quite essential so I'm trying to get
> this solved on my main machine.
>
> Thanks in advance.
>
> Barnabyh

you need to recompile the kernel modules
From: barnabyh on 29 Nov 2009 05:23
goarilla wrote:

>
> you need to recompile the kernel modules

Ahaa, thanks.
From: barnabyh on 29 Nov 2009 17:27
goarilla wrote:

>
> you need to recompile the kernel modules

Thanks again for that pointer, I'm happy to report success.

Barnaby
 | 
Pages: 1
Prev: restart fbi
Next: Type ahead change in Slack 13