Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm assuming that as part of the upgrade, you upgraded the kernel, in which case you need to recompile ndiswrapper. It is a kernel module, so any time you mess with the kernel, odds are you have to re-install.
I ran make uninstall
then
make
make install
and tried again and still got the error, am I missing something like uninstalling the driver and everything too?
Are you getting any errors from make or make install? And are you root when you run make install? You're going about it the right way so something must be going wrong.
Quote:
am I missing something like uninstalling the driver and everything too?
I don't think the Windows driver has any impact on modprobe. If the module was there it would load.
yes I am root as as far as i can see it's not erroring is there a .tgz or txz package strickly for slackware I should install and give that a shot? I have the newest version 1.56. is there a certain error log to check, I have looked in /var/log/message and didn't see anything in there im going to check the syslog and see if that helps. Im lost on ideas if you have any please shoot them my way
is there a .tgz or txz package strickly for slackware I should install and give that a shot?
Not that I know of. It certainly isn't distributed with Slackware however there is a Slackbuild at Slackbuilds.org. You might give that a try.
To be honest, if there are no errors, it should have worked. Have you looked around in the build tree to see if ndiswrapper.ko was built? How about in the /lib/`uname -r`/ tree? The only other thing I can think of is that for some really odd reason, you're not booting the kernel that ndiswrapper is being built against. Does /usr/src/linux point to the same kernel source code as your running kernel?
Not that I know of. It certainly isn't distributed with Slackware however there is a Slackbuild at Slackbuilds.org. You might give that a try.
To be honest, if there are no errors, it should have worked. Have you looked around in the build tree to see if ndiswrapper.ko was built? How about in the /lib/`uname -r`/ tree? The only other thing I can think of is that for some really odd reason, you're not booting the kernel that ndiswrapper is being built against. Does /usr/src/linux point to the same kernel source code as your running kernel?
From what I have read it's better to configure ndiswrapper from source than installing pre-made packagees of it
Im going to try what suggested and I will give ya the details
I think you might be right about it building against the wrong kernel
I burned a copy of slack-current to dvd is there a way to just upgrade it from the dvd instead of downloading it from the internet and upgrading this way I can just do a fresh install since I just installed slack-13 yesturday anyways and after install the current packages from the dvd install ndiswrapper and see what happens.
I burned a copy of slack-current to dvd is there a way to just upgrade it from the dvd instead of downloading it from the internet and upgrading this way
Oh yeah, just mount the DVD and run your upgrades from there. However, please be sure to read the changelog and README file. Slackware-current can potentially have a lot of gotchas, potentially including the order that some of the upgrades need to happen. And there are almost certainly configuration changes that need to happen after upgrading to current. Just running upgradepkg on all current packages is a sure recipe for disaster.
Yeah, im reading a upgrade guide right now where it shows how to do with using upgradepkg and slackpkg which I think slackpkg will be a better choice and it says to just edit the /etc/slackpkg/mirrors and have it mount the dvd/cdrom and yoddy yoddy. I believe this is the safe choice
Not that I know of. It certainly isn't distributed with Slackware however there is a Slackbuild at Slackbuilds.org. You might give that a try.
To be honest, if there are no errors, it should have worked. Have you looked around in the build tree to see if ndiswrapper.ko was built? How about in the /lib/`uname -r`/ tree? The only other thing I can think of is that for some really odd reason, you're not booting the kernel that ndiswrapper is being built against. Does /usr/src/linux point to the same kernel source code as your running kernel?
Ok I just got done with the 13.0 install with an upgrade to current from dvd then did a freesh install of ndiswrapper and still having the same issue it's compiled against the new kernel which i am booting to
I did a search for ndiswrapper.ko and it shows it in /lib/modules/misc/
when I run /lib/`uname -r`/ it comes back with /lib/2.6.33-smp/: no suck file or directory
I did a search for ndiswrapper.ko and it shows it in /lib/modules/misc/
OK, that simply isn't right and is likely the cause of the problem. All modules must go under their kernel version, so the path should look like /lib/modules/2.6.33-smp/misc. Try moving it by hand and then run depmod -a and see if that does the trick. By the way, I'm suspecting there is some incompatibility between ndiswrapper and the 2.6.33 kernel. I did a little googling and there are a few reports out there of problems. Another approach might be to try to grab the SVN code and see if that works.
Quote:
when I run /lib/`uname -r`/ it comes back with /lib/2.6.33-smp/: no suck file or directory
Oops, that should be /lib/modules/`uname -r`, however that isn't a command. The backticks allow uname -r to be evaluated, so if you did something like this:
Yeah I think it's a compatibility issue, I was so tired last night I fed something up so I had to do a full reinstall LOL now that I have gotten some sleep Im going to re-upgrade and give this another shot, atleast I got wicd working. again thank you for all your help, really appreciate it
Man, you're brillitan issue resolved, this is what kappens with compling ndiwwrapper under the 2.6.33 kernel
it compiles and all just fine but it installes the ndiswrapper.ko to
/lib/modules/misc instead of /lib/modules/2.6.33-spm/misc like you said in your above post so moving/coping /lib/modules/misc/ndiswrapper.ko to
/lib/modules/2.6.33-spm/misc and running depmod -a allowed me to run modprobe ndiswrapper with no issues. *wipes forehead*
after 2days we got it
again thanks a lot for all your help and support, really appreciated.
LOL very true, now the only downside is wicd doesn't seem to work now haha, oh well, well it opens just doesn't find any networks, no biggy though could be the new version I installed, might downgrade it and see what happens.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.