Not really the forum for this thread, which probably ought to go under "networking and wireless".
Originally Posted by kamodan
However, it is possible that the actual ndiswrapper module didn't get installed in the directory structure under /lib/modules/... when the installation routine happened, or, if the module is actually there somewhere, that depmod hasn't run yet after the module was installed to make it known and available for loading by modprobe.
You could check whether the module is present somewhere under /lib/modules/... You could then run depmod yourself from a prompt to make sure the module has been added to the kernel module dependencies and will be findable by modprobe:You could then see if the module can be loaded by hand by
and see whether it has loaded by which will list all loaded modules. It may all then work after a reboot brings up networking upstart scripts and loads drivers.
sudo modprobe ndiswrapper
Or, alternatively, this may be a manifestation of a known error with some workarounds available. See: http://askubuntu.com/questions/13289...pper-not-found
In general, ndiswrapper is a really awful kluge, allowing an adapter without native Linux support use Windows drivers. Even when it works it's never as fast or as stable as native Linux drivers are. In the long term, an adapter with good native Linux driver support might be the best option.