There do seem to be multiple issues here, each one affecting different
drivers.

Regarding the issue affecting ndiswrapper:  I think anonym was onto
something when he noticed that AP_SCAN 1 is being used rather than
AP_SCAN 2.  Can someone come up with a patch so we can see if that is
the problem?  (I don't know where to make the changes to do it
myself...)  Did someone make a deliberate change to NetworkManager so
that it issues AP_SCAN 1 when it used to issue AP_SCAN 2?  What are the
differences between/reasons for using AP_SCAN 1 instead of AP_SCAN 2?
Would a change back to AP_SCAN 2 affect other drivers, possibly breaking
them?

I appreciate everyone's continued effort on this.  I'd really like to
see all of these issues sorted out before Hardy is released with LTS.
In my mind, problematic wireless networking support is one of the
biggest show-stoppers for using Linux out-of-the-box with no prior
experience.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
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

Reply via email to