SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I currently run a Windows 10 system and run Slackware64 14.2 inside of VirtualBox.
I upgraded my kernel for Slackware 14.2 to 4.4.172 which has broken inside of VirtualBox and will not allow the installation of the guest additions kernel modules.
I've seen some solutions, but these look to be running Slackware and then running VirtualBox inside Slackware. I am running Windows 10 and running Slackware64 14.2 inside Virtualbox as the guest system.
Is there a solution for fixing this inside VirtualBox? Is there a way to roll back the kernel to 4.4.157 for the timing being?
If you ran slackpkg upgrade-all, that process would have removed 4.4.157, all files for the kernel upgrade. If you look at any mirror, 4.4.157 is gone, and only 4.4.172 packages are there now.
So, unless you have a backup of those files, they are gone.
Your best bet, what I would do, is get and install the kernel packages from current. I did see one post where that worked fine for the user. I have not tried that myself.
The other choice is to go to kernel.org and fine the source files for a release before 4.4.168; that is where the devs changed the kernel and caused this mess. You would have to compile the kernel and install it that way.
What version of v-box are you running on Win 10? Is it from Oracle?
If you ran slackpkg upgrade-all, that process would have removed 4.4.157, all files for the kernel upgrade. If you look at any mirror, 4.4.157 is gone, and only 4.4.172 packages are there now.
So, unless you have a backup of those files, they are gone.
Yep...I noticed. I checked a bunch of mirrors hoping to find a slow one, but they were all updated already.
Quote:
Originally Posted by camorri
Your best bet, what I would do, is get and install the kernel packages from current. I did see one post where that worked fine for the user. I have not tried that myself.
The other choice is to go to kernel.org and fine the source files for a release before 4.4.168; that is where the devs changed the kernel and caused this mess. You would have to compile the kernel and install it that way.
I might try that as a last resort.
Quote:
Originally Posted by camorri
What version of v-box are you running on Win 10? Is it from Oracle?
It is from Oracle. I was using 5.12. When this problem started I upgraded to 5.26...then I upgraded to 6.0.4...then I downgraded back to 5.26.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
