Well this behaviour is quite normal, what's wrong with it ? The device itself does not exist if the ndiswrapper module is not loaded. Loading modules is not the job of the network-manager, in my opinion. Users should do that themselves.
There are many ways of loading the module during boot, one is done by using the ndiswrapper utility itself : sudo ndiswrapper -m or you can add ndiswrapper to your /etc/modules file. I recommend the first option. -- no interfaces available if ndiswrapper module is not loaded https://launchpad.net/bugs/85526 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
