SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How did you install ndiswrapper? ndiswrapper is both an application and a kernel module. The module needs to be rebuilt for a new kernel. So if you changed from one kernel to another you will need to rebuild and reinstall ndiswrapper.
/usr/sbin/ndiswrapper is the application part. /etc/ndiswrapper is the configuration part. The module will be installed in /lib/modules/your_kernel. To see whether the module exists for the kernel you are running you can "modprobe -l | grep ndiswrapper". If it's not there (which it won't be, because you couldn't modprobe it), you can see where the package you made put it by doing "grep ndiswrapper.ko /var/log/packages/ndiswrapper_version_number".
Actually, looking at your post, I want to be clear about one thing. When you used the SlackBuild, you used it while running the smp kernel, and installed it using installpkg/upgradepkg, correct?
If you used the SlackBuild from SlackBuilds.org and your package doesn't have smp in its name, then it is obvious it was built for a non-smp kernel. $(uname -r | tr '-' '_') goes into the package name, so it would be named something like:
but there are of course two entries in /lib/modules
Presumably the solution lies in getting grep etc to point to the 22.214.171.124-smp entry?
Perhaps you could try the SlackBuild again. The installed package was not built for the smp kernel, which means it was not compiled on the smp kernel. You can look at the SlackBuild yourself to see that it determines the running kernel with uname, and will name the package accordingly (as well as installing in the correct /lib/modules tree). You can check yourself after you rebuild the package that the kernel names (both in the package name and in the module path) match uname.
[QUOTE=Bazzaah;3149381]Something is definitely amiss and I know that in Slackware that almost certainly equates to my error (you know where you stand with Slackware, even if you don't know how you got there, lol).[/QUOTED]