I think this bug is definitely fixed (or at least half-fixed). I think the fact that you need an additional step in order to make ndiswrapper load automatically is a good thing. This will make users try the windows driver first, because there could be a kernel panic or an oops due to buggy windows drivers or bugs in ndiswrapper itself.
The method suggested above is already implemented nowadays. ndiswrapper -ma writes the module aliases to /etc/modprobe.d/ndiswrapper. Due to the reasons mentioned above I consider marking this bug as fixed a good thing. -- ndiswrapper not loaded automatically at boot https://launchpad.net/bugs/19046 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
