Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey all, I was running OpenSUSE Tumbleweed and decided to go to Leap 42.2. The upgrade went fine in every way except one -- Virtualbox quit working. At Virtualbox's request I tried doing the vbox command but no joy; VB still won't run. I tried removing VB but I got an error about kernel headers not being found. I thought I might be able to install the new VB but no joy there either -- kernel headers can't be found.
I found a post that said to add the following in Yast to add the kernel headers:
Code:
Development
[X] Base Development
[X] Linux Kernel Development
[X] C/C++ Development
Nope, kernel headers still can't be found. Out of desperation I tried to do a --force reinstall of VB but even still no joy.
I'm out of ideas and I haven't found anything new to help my dilemma. Do any of you have any ideas, suggestions, or recommendations that might help? I've backed up my files in case my only option is to Nuke and Repopulate this beast but I'm hoping it won't come to that.
I ran this command, rpm -qa | grep -i virtualbox, then when I had the package name I ran this command, rpm -e <package name> and done! I just removed VirtualBox from my computer. I hope this helps someone out there.
My celebration was premature. I downloaded and tried to install the newest VirtuaBox and met once again with failure:
Code:
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
zypper install kernel-default-devel-4.8.11-1.1.x86_64
(The last command may fail if your system is not fully updated.)
zypper install kernel-default-devel
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
I tried to install the kernel-default-devel-4.8.11-1.1.x86_64 but no joy:
linux-cgcw:/home/jobee/Downloads # zypper install kernel-default-devel
Loading repository data...
Reading installed packages...
'kernel-default-devel' is already installed.
No update candidate for 'kernel-default-devel-4.4.36-8.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
linux-cgcw:/home/jobee/Downloads #
I checked /var/log/vbox-install.log and found this recommendation:
Code:
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
WARNING: Symbol version dump ./Module.symvers
is missing; modules will have no dependencies and modversions.
I'm hesitant to mess with tweaking the kernel because of everything I have installed and working on this workstation.
I've installed all available updates. If I re-run /sbin/vboxconfig (I'm running all of this as root) these error messages start over again. Any ideas on what the problem is and how to fix it???
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,952
Rep:
Quote:
Originally Posted by jbruyet
My celebration was premature. I downloaded and tried to install the newest VirtuaBox and met once again with failure:
Code:
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
zypper install kernel-default-devel-4.8.11-1.1.x86_64
(The last command may fail if your system is not fully updated.)
zypper install kernel-default-devel
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
I tried to install the kernel-default-devel-4.8.11-1.1.x86_64 but no joy:
linux-cgcw:/home/jobee/Downloads # zypper install kernel-default-devel
Loading repository data...
Reading installed packages...
'kernel-default-devel' is already installed.
No update candidate for 'kernel-default-devel-4.4.36-8.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
linux-cgcw:/home/jobee/Downloads #
I checked /var/log/vbox-install.log and found this recommendation:
Code:
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
WARNING: Symbol version dump ./Module.symvers
is missing; modules will have no dependencies and modversions.
I'm hesitant to mess with tweaking the kernel because of everything I have installed and working on this workstation.
I've installed all available updates. If I re-run /sbin/vboxconfig (I'm running all of this as root) these error messages start over again. Any ideas on what the problem is and how to fix it???
Thanks,
Joe B
it looks like you need to install/update to a current autoconf
and get your header files installed for your current kernel.
as well as if you have not gotten rid of your old VBOX getting the kernel headers for what kernel it was last using needs to be installed to.
I think if you got your old VBox kernel headers installed you should be able to just update/upgrade it from there.
I'd if not just reinstalling system, find where the old directories and config files and all of that are kept and strip them out manually. last ditch resort .
trying to or installing over an old VBox may cause you more damage then you want to deal with.
(personally I'd be backing up my needed config files and reinstalling my Linux system and getting on with life, but that is me I just use mine to play on. Nothing that serious. you might not be that fortunate)
LOL, I have a 500 gig external hard drive connected right now and I'm copying my Home folder to it. Yeah, it was time to upgrade to a new SSD anyway. Thanks for the nudge to keep me going that direction.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.