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.
Is there any place the kernel 4.9.53 packages might still be available? I ask because the Virtualbox kernel driver package from SBo won't build against 4.14.x (yes, caveats of using SBo against Current are known). I reverted back to the 14.2 kernel, 4.4.14, to get Virtualbox working again. At least this Lenovo T410 works well enough with 4.4.14 that I'm not in dire straits.
Is there any place the kernel 4.9.53 packages might still be available? I ask because the Virtualbox kernel driver package from SBo won't build against 4.14.x (yes, caveats of using SBo against Current are known). I reverted back to the 14.2 kernel, 4.4.14, to get Virtualbox working again. At least this Lenovo T410 works well enough with 4.4.14 that I'm not in dire straits.
If you plan on running VirtualBox 5.2.0, this post should be of interest to you.
Basically, you run the VirtualBox .run file; it will err out, but you copy the patch from wherever you downloaded it to the /usr/src/vboxhost-5.2.0 directory, run
I had this. The solution was to switch from Alien's Restricted FFMPEG to Slackware's FFMPEG.
Thanks for the info.
I upgraded to Slackware's FFMPEG. its okay now, no libx265 dependencies.
I have no idea why slackpkg upgrade-all does not show ffmpeg as an upgrade option to slackware64. Maybe, I need to check/reconfigure slackpkgplus, I also had ninja installed from alienbob repo.
As it is, this is just a testing install.
Slackware 14.3 or 15 is getting better.
Keep up the great work people.
unfortunately, I have never blacklisted alien, this is why I found it weird,
slackpkg should have at least shown an upgrade(even if it is a downgrade version).
I think that since slackpkgplus has no registered slackware64 repository, only a repo in mirrors, I think slackpkg does not process the upgrades that well.
I will see into it later.
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264
Rep:
I installed all new updates today including 4.14.1 -- Seems fine so far...
Code:
$ uname -a
Linux slackware.slackware.org 4.14.1 #1 SMP Tue Nov 21 22:50:27 CST 2017 x86_64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GenuineIntel GNU/Linux
Note: I did have one small problem starting x ... it failed trying to load the keyboard, couldn't write or remove something in /tmp (forget now) I just deleted everything in /tmp and all loaded fine. Not sure what happened exactly but it seems more of a 'me problem' then the update.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.