Closing, as this wasn't a real bug.
** Changed in: ndiswrapper (Ubuntu)
Status: New => Invalid
** Changed in: ndiswrapper
Status: New => Invalid
--
ndiswrapper does not launch at boot
https://bugs.launchpad.net/bugs/148019
You received this bug notification because you are a membe
> 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".
Maybe this is the cause of your problem. What is your interface called
now, wlan0 or eth0
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
ndiswrapper -m creates an alias i.e. the module is being loaded when wlan0 is
used. That means that you have to use wlan0. If you haven't configured your
wlan card to connect at boot (i.e. auto wlan0 in /etc/network/interfaces) it
won't load at boot, but when doing a sudo ifup wlan0
I'm not sure
** Changed in: ndiswrapper (Ubuntu)
Sourcepackagename: None => ndiswrapper
** Also affects: ndiswrapper
Importance: Undecided
Status: New
--
ndiswrapper does not launch at boot
https://bugs.launchpad.net/bugs/148019
You received this bug notification because you are a member of Ubuntu
