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.
It's a dirty fix regardless. That's a fix better suited for developers only, testers, and such crowds, not end users.
It is nothing more than a kernel license lockout avoidance, not a fix. That feature that is disabled is only a kernel feature used by debugging and developments. You gain no benefit from applying that except extra debugging.
Well, topic starter had this problem (and by the way he tried to build newer version 331.38). I had it too and just posted my solution because didn't seen any other solution in this thread which is working (other then using stock 3.10.17 kernel, which is in fact no solution at all). If you have any other idea how to solve it - just post it please.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.