LinuxQuestions.org - Virtualbox driver missing on ose using Mandriva 8

- Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)

- - Virtualbox driver missing on ose using Mandriva 8 (https://www.linuxquestions.org/questions/mandriva-30/virtualbox-driver-missing-on-ose-using-mandriva-8-a-685358/)

Virtualbox driver missing on ose using Mandriva 8

I realise I've posted a similar thread so apologies in advance. I have had vbox working on Mandriva in the past but this seems to be some new problem, so two main questions:

Will having two or more vbox kernels on one machine confuse the issue

and,why does a shell search report 'no such directory' for Vboxdrv - surly it should report something like 'permission denied' or is there just not compilable because of the above conflicts?

Ignorance is not bliss.

fred.

Quote:

Originally Posted by Fred Caro (Post 3350838)

Will having two or more vbox kernels on one machine confuse the issue

Assuming that you mean the kernel module packages, no.

Quote:

and,why does a shell search report 'no such directory' for Vboxdrv - surly it should report something like 'permission denied' or is there just not compilable because of the above conflicts?

Presumably because the module is vboxdrv.

Jim

vbox driver missing

Dear jkerr,
thanks for your reply and you are right on both counts so if you, or others, could give an answer it would make a newbie very happy.

Fred.

An answer to what question? What problem exactly do you have?

Jim

Vboxdrrv missing

Sorry I'll try again. The error message is somthing like 'error 1908 Vboxdrv missing or not compiled, type in /etc/init.d/vboxdrv setup'.This is useless as are many of the solutions available, leading me to conclude that this drver is not there and appears to be nowhere to readily download it. All the codecs are present (Vbox version 1.6) but it still gives the above error- the likely next errror will be 1909 then 102.
I wonder if the presence of differnt kernel modules on the disk is causing problems. If so how do you remove them effectivly? I ask this becuase the useual methords leave vbox lurking in the backgruond so that when you reinstall it preserves disks you have previously created.

Thoughts greatfully recieved.

Fred.

What does

Code:

rpm -qa | grep virtual

run as root, return? Please copy and paste the output - "something like" the result would not be helpful. :)

Also post the result of

Code:

uname -r

Jim

In reply, and thanks for your time and efforts, here are the results from running the suggested code:
sorry cannot copy and paste this information, although the relevant kernels do match. Sorry, will get back.

fred.

If you run the above suggested commands in a terminal window you can highlight the output with your mouse, then ALT+CLICK the highlighted information and select COPY in the resulting pop-up menu. Following this, you can paste the information to your browser window (in the post submission editor).

HTH,

Quote:

Originally Posted by Fred Caro (Post 3352635)

Sorry I'll try again. The error message is somthing like 'error 1908 Vboxdrv missing or not compiled, type in /etc/init.d/vboxdrv setup'.This is useless as are many of the solutions available

Exactly how is it "useless"? It's the standard way of generating /dev/vboxdrv. What errors are you getting? You do know that you must run it as root, right?

Yes I did run it as root but if it is not there then it will not run.
Regarding high-lighting and copying there must be something I'm doing wrong as it will not high-light or copy.

Fred.

Quote:

Originally Posted by Fred Caro (Post 3355831)

Yes I did run it as root but if it is not there then it will not run.

It would have been helpful if you had said "/etc/init.d/vboxdrv" does not exist, rather than simply it's useless. Or are you talking about something else not existing?

Quote:

Originally Posted by Fred Caro (Post 3355831)

Regarding high-lighting and copying there must be something I'm doing wrong as it will not high-light or copy.

To highlight, left-click at the beginning of the text that you want to copy, hold down the left mouse button and drag the cursor over the text you want to copy and then release the button, leaving the text highlighted. Left click at the spot in your browser where you want to paste the text and then middle-click. (On a wheel mouse the wheel is also the middle button. Just click it like the other buttons.) Sorry, if you already knew all this. :)

Jim

missing vbox driver

Sorry I'm making hard work of this:

virtualbox-kernel-desktop-latest-1.5.0-1.20080506.6mdv2008.0
virtualbox-kernel-2.6.22.9-laptop-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-desktop-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.19-desktop-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.19-server-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-server-latest-1.5.0-1.20080506.6mdv2008.0
virtualbox-kernel-desktop586-latest-1.5.0-1.20080506.6mdv2008.0
dkms-virtualbox-1.6.0-4mdv2008.0
virtualbox-1.6.0-4mdv2008.0
virtualbox-kernel-2.6.22.9-desktop586-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.12-desktop586-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-server-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.12-laptop-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.12-server-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.12-desktop-1mdv-1.5.0-6mdv2008.0
virtualbox-guest-additions-1.6.0-4mdv2008.0
virtualbox-kernel-laptop-latest-1.5.0-1.20080506.6mdv2008.0
virtualbox-kernel-2.6.22.19-laptop-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-desktop-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-server-1mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-desktop586-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.19-desktop586-2mdv-1.5.0-6mdv2008.0
virtualbox-kernel-2.6.22.9-laptop-2mdv-1.5.0-6mdv2008.0
[root@localhost patti]#

I would only highlight just after the beginning of the text. The above is the grep readout and the uname one records a kernel of 2.6.22.9-desktop.

Yes the vbox driver is missing, any ideas where I can find said driver?
Call me cynical but the VirtualBox website seems to be mainly concerned with its commercial version- that or I've missed somthing.

Thanks Fred.

The kernel module packages that you have are for a different version (1.5) of vbox than you have installed. You have vbox 1.6, which I assume you got from the backports repo. There are no binary kernel modules for backports packages.

Uninstall everything in that list, except:

dkms-virtualbox-1.6.0-4mdv2008.0
virtualbox-1.6.0-4mdv2008.0
virtualbox-guest-additions-1.6.0-4mdv2008.0

Then install kernel-desktop-devel-2.6.22.9

dkms should build the kernel module the next time you re-boot.

Jim

<edit> sorry for not reading your post Jim, I agree with you whole heartedly. Glenn</edit>

Hi, if you run a business or a corporation you may use the OSE (open source edition).

If you just want to use it at home and are more interested in using rather than developing vBox,

you can use the non-open source edition.

The benefits of the non-ose version is that usb and file sharing are configurable.

They are both "free software", but for the extras business or corporations may pay, but may also

modify the source, hence, open source edition.

Your question...

Looks to me as if you have vBox 1.6 installed and the kernel module (via DKMS) for 1.5,

These version numbers must match, then you may still have problems launching the the program.

Decide if you want the sever, desktop, or laptop kernel and remove the others.

It is a good idea to keep one old (previous) version as a backup of the kernel if you

like to configure things your self.

See how you go.

Cheers, Glenn