Yes install dkms, kernel-devel is for Red Hat based distributions. And when you get the chance install build essentials.
The VBox Manual should say if you would need kernel-devel for a Debian based system. It's been so long since I ran Debian I can't remember.
https://www.virtualbox.org/manual/UserManual.html

Yum is the commandline utility for installing pkg's and software on Red Hat based distributions.
Kali Linux is based on Debian which does not use yum.

-:-Post your sources list for Mr. EDDY1.-:-

If you didn't choose a mirror for your distribution to pull pkg's, security updates and etc. that's probably what is contributing to things not installing.

I had to read the VBox Manual several times to install VBox correctly.-

In post #8 EDDY1 requested that you post your sources.list.

In post #9 and in post #11 evo requested that you post what the konsole/terminal retured.

Kindly post in [code tags] what they have asked of you.

They can't help you or tell you what is going on without seeing the data.

"In post #8 EDDY1 requested that you post your sources.list."
05-25-15, 01:18 PM Contains the source lists.
EDIT (To clarify/simplify):
deb http://http.kali.org/ /kali main contrib non-free
deb http://http.kali.org/ /wheezy main contrib non-free
deb http://http.kali.org/kali kali-dev main contrib non-free
deb http://http.kali.org/kali kali-dev main/debian-installer
deb-src http://http.kali.org/kali kali-dev main contrib non-free
deb http://http.kali.org/kali kali main contrib non-free
deb http://http.kali.org/kali kali main/debian-installer
deb-src http://http.kali.org/kali kali main contrib non-free
deb http://security.kali.org/kali-security kali/updates main contrib non-free
deb-src http://security.kali.org/kali-security kali/updates main contrib non-free

deb http://download.virtualbox.org/virtualbox/debian wheezy contrib

sudo wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -

"In post #9 and in post #11 evo requested that you post what the konsole/terminal retured."
05-25-15, 01:18 PM also contained the output of both the terminal and log, shall i continue to repeat the same error redundantly or what? Admittedly, i missed this second page to this thread until now and for some reason was not informed via email it was even hear, by manually coming here and looking closer did i even find this.
EDIT (To clarify/simplify):
[FAIL] Failed, trying without DKMS ... failed!
[....] Recompiling VirtualBox kernel modules:
[FAIL] Look at /var/log/vbox-install.log to find out what went wrong ... failed!

THE LOG:
Makefile:172: *** Error: unable to find the sources of your current Linux kernel.
Specify KERN_DIR=<directory> and run Make again.

sudo apt-get install dkms don't work in ither terminal or package managment.

"If you didn't choose a mirror for your distribution to pull pkg's, security updates and etc. that's probably what is contributing to things not installing" -Yes, it was an offline install. I had that problem and thought i had fixed it within the source lists as shared. It must not have been, how to be sure?

"Yum is the command line utility for installing pkg's and software on Red Hat based distributions. Kali Linux is based on Debian which does not use yum. " -I said that earlier but it was ignored it seems, when i used a yum command as a sudo command instead it was experimental, as stated in the original post; sometimes that substitution works. But it is a hit and miss thing. One poster tried to say yum would simply work.
Ok Not touching that subject.

If i missed something else feel free to let me know otherwise those who will not read it as it is will not be helpful and can not be expected nor asked to. Throwout this thread, as per error received, one at a time, in the order received it is posted accordingly.

New plan (in the order listed - as wrote) logged in as Root:

sudo apt-get install build essentials
sudo apt-get install linux-headers-$(uname -r)
sudo apt-get install dkms
sudo apt-get install virtualbox-4.
sudo apt-get update

The result:

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package build
E: Unable to locate package essentials

Searched the Add/Remove Software inside Aplications > System Tool's
Found build-essential-11.5 (23-bit)
Question: Am i missing the "-"'s?

Retryed with:
sudo apt-get install build-essentials
Resulted in:

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package build-essentials

I think at this point we, (including myself,) should re-read this thread just to clarify/be on the same line of idea and ensure were all strait with this. Thanks to all who are trying, its appreciated. Apology's about the confusion.

NO
Kali dose NOT!!! use "su" or "sudo"

there is ONLY one user
ROOT!!!
there are NO normal users

you run the OS AS ROOT !!!!
-- so BE WARNED !!!

1 members found this post helpful.

1st: EDDY1- Thank you, i needed to see that and wish more would give references like that. That's the best kind of help there is. Leaves little room for doubt. I will be studying that in a little bit right now its just the day from h3ll for me and i need to chillax for the moment so i don't approach this matter like a bull.

2nd: EDDY1- I would think after "Posts: 14,466" and such a great "Reputation" one would know more than me and that said cap's is shouting and highlighted cap's is emphasizing. I don't know what version of Kali or even BackTrack your using and i'll certainly admit being one of those aforementioned monkeys with a rocket launcher but here we expect people to please keep it civil I am in the worst most rotten mood today and even i am. That said you say: "there is ONLY one user " but that is only if you keep it a live system with or without persistence in the newest version of Kali which i am using. I have both Root and a user name, your half right because i can log out of the auto logged in "user" and log in as Root to do this sort of work without having to mess with the security too much. You also say that "Kali dose NOT!!! use "su" or "sudo"" sudo apt-get is what works, yum did not and i tried many times. That, (at least in some rare instances,) may or may not work with yum but its like using both the package manager and terminal to install software: there is consequences to doing that i am well aware of. I have 0 interest in the hacking tool's in this version of Kali as i use a custom made version with BlackHat repo's and was a Debian and Ubuntu mix 2 years before they did it when everyone said it was impossible i have 0 issue with so i know enough to do most but its these little nagging items were you have something backwards or inside out to find that i have issue with. I use well over 2 and a half thousand more tools in my version than Kali has in it so Kali is a toy to me.

So to be clear again:
This copy of Kali is on a USB of 16GB and a Sandisk that is made for a serious beating and lasts. Its not a live system. All i want to do is use it to boot on a old pile of scrap computer parts i soldered together to repair several TB of HDD's to host a project of mine in the deep web and help the good guys be at there best as is my job to do. Nothing illegal or immoral. Just secured. For all the right reasons. The main mother board of the scrap system is of a Acer Aspire One. Kali is all it will use properly that i know of, i have a collection of Distro's offline stored for such uses, hundreds of them in fact.

So, even "if" some one who has booted something else successfully from a Acer Aspire One and used VirtualBox there can recommend a system ... i will try it and if it works it solves the problem also.

My last forum post is still not solved, no one could. But it was done perfectly none the less by all who tried. There was no flamboyancy and it was informative. Lets keep it that way please. I.E.: The only time i complain about spelling is code improperly made I don't expect anyone to be perfect at all and remember there is a human on the other side of things.

Well, i just formatted the device and did what i set out to do on a separate machine. This post remains unanswered. The advice thus far failed.

JohnVV, Mr. evo2 and Mr. Eddy1 with all due respect are my superiors here at LQ and have earned the rank and have experience above me. Had it not been for their help I would not be running Linux today.

If I have been mistaken in assisting you they would of corrected me. (and still may)

I noticed that the konsole showed the installation of headers for kernel 3.0.0-1.
But you are running kernel 3.18 so the headers for kernel 3.0.0 will not work (unless I'm wrong) for kernel 3.18.
-::-I thought that the kernel and the kernel headers have to match.-::-

Are you sure you didn't modify your sources list?

Where you able to install Virtual Box?

Well that's great, but going off of memory yes i did modify the sources list and had to without choice. When i installed it to USB from a USB it had no mirrors selectable as it said so i went to the Kali site and collected there current lists for the current version. That failed 3 times. Just like me to put a 0 were there should be a 1 sorta as complicated as things are, most would but the lists and Kali site should have been what it should have been. No, Virtualbox failed there miserably and if its gonna be that touchy there then its not worth it to me.

A long while back, i put together a still functioning system with Ubunto, Kali and Debian so why is this an issue? Used BlackHat repo's at that.

I understand but I won't be able to help you.
Anytime that the sources.list is altered you won't get the proper packages and updates from the repository.

The only thing I could suggest is look up the sources.list for Kali Linux and edit yours until it is exactly what Kali recommends.

As I said before, I had to read the installation section of the VBox manual about 3 times before I got VBox installed correctly.
Is this the Virtual Box .deb pkg that you downloaded in the picture attached?
(that is if your pc is 64 bit? or 32 bit?

Maybe try another distribution.
Virtual Box runs great on my CentOS machine and from what I understand it works well on Debian and Slackware.

http://docs.kali.org/general-use/kal...t-repositories
https://www.debian.org/
http://www.centos.org/download/

Attached Thumbnails

 

Yea i tried all that, i think something messed up just enough in the download. Hard to believe several times but o'well. Case was closed 2 posts ago. Thanks any way.

Your Welcome.

I'm surprised that installing the .deb file didn't work for you.

Do you mean your done with this?

I am surprised nothing worked were it should have, no worries i still got the point achieved which was to use it to repair a completely dead hard drive which is now not only online but like new. Funny because it wouldn't even show on a list anywhere when i started. A virtual machine would have taken 3.5 times longer but the idea would be it would be entirely undisturbed. I tested the disk this was for, ( specifically the USB's,) they tested 100% fine so i can rule that out also. This is a mystery, one i won't be solving at this point. No need to and at this time i think its a waste of time. If all those idea's didn't fix the problem, what's left?

I will say that something i been noticing with Kali as well as BackTrack was when you go to install it and it will not connect to the internet, if you don't want these kind of random issues then shut it down and do NOT install it until your online again. If it wouldn't install from the root account logged in as root as per the option contained there in, then don't install it also. I have sen both instances happen and in both instances it ends in disaster one way or another.

Glad to hear that your HDD is working properly. That's good news.

I noticed the same internet connection problem with BackTrack when I helped others.
In fact it didn't make sense to me because installing the driver for the wifi card should of solved the problem.

I'm sorry it's a mystery and I'm out of ideas of what to try.
You'd think that installing the VBox .deb file would of installed properly.

Maybe a Moderator or another member will see this thread and know of another way to fix it.

I'm surprised that other member running Kali Linux or BackTrack haven't chimmed in--

No worrie's. The point was achived by another means. I almost hate to ask but if i should close this post lemmi know and i am not sure how. Again, thanks.