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.
Until this is patched by other projects, this addition to kernel 4.1 and later may need to be reversed by a patch to allow extra kernel modules to build correctly.
Already this causes ZFSOnLinux some issues, but I have no idea if other modules like Broadcom(wl), nvidia, and other kernel drivers are affected, but do be mindful of Kernels 4.1 or later if you use external modules not normally included with the kernel.
You may need to recreate the patch to reverse out these additions to the code. I ran into a problem with this on a custom build project, so I figured I'd share in case anyone else may have had a problem, or was considering 4.1 or later to use or test.
I've read yours post about the zfs issue. I think the problem is that this file doesn't have a #ifndef macro at the begin of code, which leads to include it more than one time. The patch is not trivial, but you must follow the include tree starting from fs/zfs/zfs/trace.c and check for include guards.
I contacted the project and they said that currently it is being worked on, but patching is the best solution until it is fixed. They directed me to that commit so for now I'm going to work on creating a simple patch for testing purposes.
I've been tempted to upgrade to a 4.1 kernel, but so far have been chugging a long with 3.18.x without issue. Dell Inspiron N4010. Every time I try to get a newer kernel than a LTS, I always have hardware problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.