Thank you! It worked! I didn't realise that "sudo ndiswrapper -m" and "sudo ndiswrapper -ma" differed in that way.
So thank you very much for this information. Strangely enough, though, under Feisty I did manage to get ndiswrapper boot automatically, merely by doing "sudo ndiswrapper -m", while my wlan was attached to the system under "eth0" instead of "wlan0". To my opinion, however, your way should be used at all times. -- ndiswrapper does not launch at boot https://bugs.launchpad.net/bugs/148019 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
