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.
4.12 running ok here, though for now I just used a 'make olddefconfig' against my 4.11 config and haven't investigated any of the fancy new features such as the new schedulers.
For anybody using 'dusk', I'm not going to be building any more 4.9 series kernels because Slackware's official kernels in -current are available and regularly updated. So from now on it's 4.4 and 4.12
For anybody using 'dusk', I'm not going to be building any more 4.9 series kernels because Slackware's official kernels in -current are available and regularly updated.
True, although it was so convenient always see the current version of the kernel in slackpkg. Thank you!
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,125
Original Poster
Rep:
Quote:
Originally Posted by 55020
For anybody using 'dusk', I'm not going to be building any more 4.9 series kernels because Slackware's official kernels in -current are available and regularly updated. So from now on it's 4.4 and 4.12
Thanks for the 4.12.1 kernel!
It works with everything except VirtualBox. When trying to build the VB module it returns this error,
Quote:
Testing system setup...
Installing VirtualBox to /opt/VirtualBox
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/
4.12.1/build -j2 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)....
Thanks for the 4.12.1 kernel!
It works with everything except VirtualBox. When trying to build the VB module it returns this error,
Just FYI.
Thanks, again.
I haven't used the dusk kernel builds, so forgive the ignorant question, but is the kernel source included? If so, it sounds like you can just follow those instructions to fix it.
For anybody using 'dusk', I'm not going to be building any more 4.9 series kernels because Slackware's official kernels in -current are available and regularly updated. So from now on it's 4.4 and 4.12
Thanks. Sorry if this post is OT.
I'm building a new Ryzen system, and slackware-current is using 4.9.37 as of today. I hear that Ryzen should use 4.10+. Is there a way to modify my local mirror to insert one of these 4.12 kernels into the directories and rebuild the ISO? Will it just work? Or do I need to do more work?
I'm building a new Ryzen system, and slackware-current is using 4.9.37 as of today. I hear that Ryzen should use 4.10+. Is there a way to modify my local mirror to insert one of these 4.12 kernels into the directories and rebuild the ISO? Will it just work? Or do I need to do more work?
It depends on the detail of "Ryzen should use 4.10+" (and possibly also on any other new/shiny/expensive stuff). If that means 'works well enough with 4.9 to do an install but needs to be upgraded to 4.10+ later to get fancy video and max performance', then there's your answer. If that means 'totally broken on 4.9', then you would need to replace not just the kernel packages under slackware64/, but also the installer's own kernel inside initrd.img. I'm not sure how much work that is. If NVMe is also in the mix, god knows. This stuff is outside my budgetary parameters, which leads to downward pressure on my attention span.
If it was me, I might do the install on another box, including a 4.12 kernel, then move the finished hd to the Ryzen box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.