This bug has three duplicates, each of which is for a specific card.
So, those bugs were marked duplicates of this one... and now you've
marked this bug invalid because it is not specific enough. That seems
kind of inconsistent, if you see what I mean.
--
Some drivers do not work with
this bug is far too generic. Please open a new bug for your specific
driver if you still see issues.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Invalid
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://bugs.launchpad.net/bugs/48473
You received
I am getting a possibly related issue with my Advent 7113 laptop, which
has an inbuilt MSI 6877 WLAN. It can see the network just fine, but
cannot connect - this is true for WPA authentication as well as WEP and
open networks, although other users have suggested they have succeeded
by using WPA on
Can you please test if this is still an issue for you with latest gutsy
live cd?
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://bugs.launchpad.net/bugs/48473
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Please disregard my previous comments. It turns out that there was a
miscommunication about the spelling of the WPA password, and I was
trying the wrong one on all of the systems I listed above. The feedback
for this failure was lacking, so I assumed it was a NM bug. I am now
successfully
As commented in bug 53788 (a duplicate of this one), I'm seeing a
related problem with a Sitecom WL-171 (RaLink RT2561/RT61), and
NetworkManager Applet 0.6.4.
I can use the wireless network just fine if I connect using dhclient
ra0. However, I can't get network manager to actually connect, even
I believe that I have observed this bug on several similar systems.
Feisty is unable to connect to a WPA network (appearing to
timeout/blacklist as described) on a variety of thinkpads that I have
encountered on the same wireless network.
These laptops have the following wireless network devices
One little addendum to my previous entry. I'm not sure if it is
relevant, but I believe that all of these systems were upgraded from
Edgy. My own system switched to feisty shortly before the Beta release,
and was in fact able to connect to WPA networks on several occasions in
mid-to-late March.
The rt74 driver, which is required for adequate functioning with my
adapter, also fails to work with NetworkManager due to this issue. (My
problem's history is in bug 104382, which I just found the rt74 driver
as a workaround for.) I am using Ubuntu Feisty.
--
Some drivers do not work with
I had the wpasupplicant from Trevino's repos installed, and after
downgrading to 0.5.4-5, WEP encryption now works. Trevino's repos had
version 0.5.7+3v1ubuntu5
(http://3v1n0.tuxfamily.org/dists/edgy/3v1n0/index.html). Perhaps some
update between those two caused this?
--
Some drivers do not
me too, orinoco_cs. I'll try downgrading wpa_supplicant.
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Scott Robinson: Have you created that wiki page for working
NetworkManager configurations yet? Thanks.
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Bug 42504 and 46136 are the same bug. (but not marked as duplicate for
historical / versioning reasons) Since you keep making casual reads as
opposed to understand the problem, let me describe it here in detail to
resolve your curiousity:
In dapper, the version of ndiswrapper is only partially
Thanks, that explanation greatly clarifies the issue - not knowing
much about wpasupplicant, I assumed that reverting to wireless
extensions meant doing away with wpasupplicant altogether, and spoke
too soon.
--
Some drivers do not work with wpasupplicant, and therefore NM.
** Summary changed:
- [dapper] Some drivers do not work with wpasupplicant, and therefore NM.
+ Some drivers do not work with wpasupplicant, and therefore NM.
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
Does this issue still occur for anyone using Edgy?
Basically, what cards don't quite work with wpasupplicant yet?
Yes, this still happens in Edgy. If I understood it correctly, it is a
driver-related issue. On my particular case, I am using the open source
acx driver shipped in ubuntu and I am
Ndiswrapper doesn't work with wpasupplicant, I think, but I haven't tried in
a couple of months, I just downgraded NM and let it be.
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Correct, ndiswrapper doesn't work but for a reason in NM that is being
fixed bug 46136.
--
Some drivers do not work with wpasupplicant, and therefore NM.
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The fix in NM in that bug is to use wireless extensions instead of
wpasupplicant with ndiswrapper, in effect confirming what I just said.
Bug 42504 seems to be about ndiswrapper not working with wpasupplicant,
at a glance.
--
Some drivers do not work with wpasupplicant, and therefore NM.
19 matches
Mail list logo
