The problem is not in Ubuntu, but rather in the main kernel. Details
here:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1507
Currently the developers are working on it. I guess that when the patch
will be ready, it will be included in the linux or linux-backports
packages...I hope.
I'm receiving a similar problem as above, attempts to connect to some
unsecured networks work fine, but others do not. I've attached the
appropriate syslog entries of a failed attempt - the lights do not light
up, although connecting through a wired connection works fine.
** Attachment added:
On Mon, Mar 31, 2008 at 1:06 PM, Jefferson Martins de Oliveira
[EMAIL PROTECTED] wrote:
mode Ad-Hoc don't work. Look:
Please file a new bug for that.
--
Martin http://launchpad.net/~mbp/
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
mode Ad-Hoc don't work. Look:
[EMAIL PROTECTED]:~$ sudo iwconfig wlan0 mode Ad-Hoc
Error for wireless request Set Mode (8B06) :
SET failed on device wlan0 ; Device or resource busy.
[EMAIL PROTECTED]:~$ dmesg | grep iwl
[ 31.810134] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network
This bug was fixed in the package network-manager - 0.6.6-0ubuntu4
---
network-manager (0.6.6-0ubuntu4) hardy; urgency=low
* fix hidden networks for chipsets that do not have scan_capa enabled
driver. (LP: #50214, #200950, #203793, #199679). The following
behaviour is now
I'm confirming that with 0.6.6-0ubuntu4, and system restart, my WPA
Network is working again
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ok, reopening. martin, you said that my .ap_scan fixes this for you?
** Changed in: network-manager (Ubuntu)
Status: Fix Released = Confirmed
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is
i assume that this non-hidden ssid bug was fixed by hal. if you see
issues with hidden ssid, please see the branch in bug 200950
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
Still not fixed for me.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The new version of NetworkManager solved my problem. Great work!
(The (latest) Hal version listed below did not solve the problem, Steve.)
version listing:
network-manager 0.6.6-0ubuntu3
hal 0.5.11~rc2-1ubuntu2
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
Fixed here too, I'm back online.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Martin, Trip, does installing the current hal package fix this problem
for you as well?
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
May I suggest that the bug is related with
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/205355 ?
I have the latest hal and NetworkManager installed. But the problem
still presents.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
It may be that this bug is related to bug #205355, but the first
question is whether it's really a manifestation of bug #204768.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a
Here's an extra data point: I'm seeing the same problem on my machine.
The data:
- Hardy, up to date until March 22, 2008.
- It worked yesterday, now nm tries to connect but I get no bulbs. I have to
kill -9 NetworkManager, and then manually restart it, if it starts to try to
use the wireless
Oh, and I forgot to mention: it's a public WPA2 PSK network for me as
well.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the exact issue on my notebook computer running a PRISM54 wireless card.
After yesterday's updates (as mentioned by Bart) networkmanager does not
connect to my wireless network (WPA/WPA2 with PSK). After killing the nm-applet
and plugging in a LAN cable I can configure the wired
edit: I retryed to get the wired connection to work instead of the
wireless as I described above by killing nm-applet and NetworkManager
but it did not work again. I fideld around a long time and then gave up
(NetworkManager does not work, the gui is slow/hangs, ifconfig does not
work either...).
Confirmed here, too (Dell Inspiron e1505). It broke last night after a
small update (wish I remembered what the packages were). When it's
trying to connect to a WPA-Personal network, it just sits there and
spins around with two empty dots in the tray, and uses up as much CPU as
it can. I have
NetworkManager also displays these symptoms on my macbook with madwifi-
ng trunk drivers too associating to a public WPA2-PSK network
It worked until that major version update of NetworkManager, now I see
NetworkManager CPU spinning in top, and no association.
--
[hardy][iwl3945] 3945ABG
I should mention that I was wrong to say only WPA networks fail.
Unsecured networks give me the same symptoms (I don't have a WEP network
handy to check that).
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug
It worked until that major version update of NetworkManager, now I see
NetworkManager CPU spinning in top,
and no association.
What version of hal do you have installed? This symptom (CPU spinning
in top) points to bug #204768, fixed in hal 0.5.11~rc2-1ubuntu2.
--
[hardy][iwl3945] 3945ABG
After upgrading to the latest hal via a wired connection, this problem
is fixed for me (CPU spinning). Thanks, Steve for the pointer.
I can now associate with madwifi-ng to my network.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
The hal downgrade earlier tonight fixed the problem for me too.
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
When I brought my laptop back from suspend, nm showed the network in
the menu. I selected it and syslog showed stage 2 complete.
iwconfig at that point shows it *not* associated with an AP.
I disabled NM, unloaded and reloaded the iwl3945 module, and restarted
NM through /etc/dbus/event.d etc.
the log makes me think that you don't get any association event to user
space. can you confirm that while waiting at stage 2 your interface
associates properly?
Anyway, I received several confirms that iwl3945 works in general. This
makes me wonder if this has something to do with your chipset
The home of the driver is here: http://intellinuxwireless.org/?p=iwlwifi
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Wed, Mar 19, 2008 at 5:49 PM, Alexander Sack [EMAIL PROTECTED] wrote:
can you confirm that while waiting at stage 2 your interface
associates properly?
What do you mean?
--
Martin http://launchpad.net/~mbp/
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
check while it sits in stage 2 that iwconfig shows your interface as
associated
--
[hardy][iwl3945] 3945ABG cannot associate to public WPA2 PSK network
https://bugs.launchpad.net/bugs/203793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
30 matches
Mail list logo
