*** This bug is a duplicate of bug 202453 ***
https://bugs.launchpad.net/bugs/202453
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Committed
** This bug has been marked a duplicate of bug 202453
[Hardy] network-manager prevents atheros chip from connecting to the
please test if the bzr branch i just associated with this bug fixes this
ath_pci issue for you.
To build:
1. get the branch
2. build using debuild -b
To test:
1. install libnm-*.deb and network-manager*.deb produced by the build
2. test to connect to wpa ... test to reboot ... and so on.
Yes--your patch fixes the issue--I'm back to the functionality I had in
gutsy where NM can manage my wireless network connections
(successfully). I believe I had seen that mentioned elsewhere--that
madwifi isn't supporting wext very well--so your patch makes sense that
it resolves the issue.
--
On Mon, 2008-03-17 at 10:42 +, Alexander Sack wrote:
please test if the bzr branch i just associated with this bug fixes this
ath_pci issue for you.
I built and installed these and they worked perfectly for me.
:-Dustin
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to
This works great for me on my 3rd gen MacBookPro running with madwifi.
Thanks!
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Built and tested Alexander's branch this morning and after a reboot
everything's back to normal. Network-Manager connects as expected to my
WPA network at home and my open network at school.
Thanks Alexander!
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
The patched network-manager works fine here, too (WPA protected network
at home). I still have to reload ath_pci after resume, but this has
nothing to do with this bug. Thanks!
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
It can't be wpa_supplicant's fault as I see the same issue connecting
to a WEP network.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Agreed, I have the same problem on both WEP and open access points.
Command iwconfig-iness works. Through NetworkManager, no dice.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because
We probably don't need too much more guessing about whether it's network
manager or wpa_supplicant, etc.. for those who are reporting similarity to the
original reporter the following experience is the common bond:
- *can* connect using Atheros h/w to a protected or unprotected network using
I droped off my encryption for a short time, to test wether I could connect
without encryption. It still doesn't work.
I'm using a T41p.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification
I think this bug is a regression caused by the package update described
in Bug #197538.
NetworkManager 0.6.5 works fine with my internal atheros card. With
0.6.6, it won't associate with any access point. Using iwconfig on the
command line, wireless works fine.
I went through the change log
It's still a month or so before Hardy will be released so hopefully this
bug will get the attention it needs. No need to be disappointed just yet
:)
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug
So today I tried it with with our university network. With NM, neither
the Atheros nor the Prism card worked. With iwconfig/dhclient, only the
prism worked, but not the Atheros.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
I'm not sure if it's network-manager or wpa_supplicant's fault, but it
seems that it IS telling ath0 to associate with the network but no
network key is ever set. if you iwconfig while it's trying to associate
you'll see it set to the correct ssid, but enc remains empty.
My guess is that since
I found out that with my built-in Atheros card, I cannot connect to my
university wireless network at all, neither with NM nor with
dhclient/iwconfig. The connection comes up, but breaks down a few
seconds later.
So back at home, I tried my good old 802.11b PCMCIA Wireless card (Prism II
with
Network Manager works fine with two other USB wifi adapters that I have,
neither use madwifi. Using network-admin or manually editing the config
files for wpa etc to configure the Atheros interface works however.
Seems it's a problem with Network Manager talking to the madwifi driver.
--
Confirmed on Hardy Alpha 6 on MacBook Core Duo.
02:00.0 Ethernet controller: Atheros Communications, Inc. AR242x
802.11abg Wireless PCI Express Adapter (rev 01)
NetworkManager just churns with same output as above. Manually setting
the network in /etc/network/interfaces and wpa_supplicant works
Confirmed on Thinkpad T61p
Linux t61p 2.6.24-12-generic #1 SMP Sat Mar 8 02:29:24 UTC 2008 i686
GNU/Linux
network-manager 0.6.6-0ubuntu1
*-network
description: Wireless interface
product: AR5212 802.11abg NIC
vendor: Atheros Communications, Inc.
physical id: 0
It should also be noted that this is a regression from gutsy (at least
on my atheros hardware). In gutsy both NM and wpa_supplicant paths
worked fine for WPA1/2, WEP, open connections to wireless networks.
In Hardy (at least alpha4-6 where I can confirm) *only* wpa_supplicant
(or iwconfig if you
Same here on a Thinkpad T41p using Kubuntu Hardy Alpha 6 and a WPA2
wireless network. Manually invoking wpa_supplicant and dhclient works
fine, wpa_supplicant.conf contains the following:
network = {
proto = WPA2
ssid = MYSSID
key_mgmt = WPA-PSK
pairwise = CCMP
psk = MYKEY
priority =
Same here on a Thinkpad T41p with Atheros AR5212 and current hardy.
Connecting with wpa_supplicant/dhclient works fine.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because you are a
I have exactly the same problem. Have to manually connect but on my case
i'm using wep.
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello,
the same occurs here after dist-upgrading Gutsy to version of yesterday night.
With the old version it more or less worked, but sometimes I needed to click on
the network 2-3 times ... then the connection became ready (100%). I am using a
kernel from vanilla sources + madwifi + whoopie
** Description changed:
Binary package hint: network-manager
Since upgrading to alpha 6 earlier today and rebooting I haven't been
able to connect to my WPA1 network at home using NetworkManager. I've
removed all preexisting wireless settings for the application and
started fresh,
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
26 matches
Mail list logo
