MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.
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).
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.
Last edited by jkerr82508; 11-27-2008 at 04:45 AM.
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 220.127.116.11-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.
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.