| 2008-09-08 16:49:56 |
David Hugh-Jones |
bug |
|
|
added bug |
| 2008-09-08 16:49:56 |
David Hugh-Jones |
bug |
|
|
added attachment 'lspci.vvnn' (lspci.vvnn) |
| 2008-09-08 16:53:21 |
David Hugh-Jones |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-09 22:58:39 |
Alexander Sack |
title |
N-M 0.7 caused system to become unresponsive when trying to connect wirelessly |
iwl3945, hardy - N-M 0.7 caused system to become unresponsive when trying to connect wirelessly |
|
| 2008-09-09 23:01:43 |
Alexander Sack |
network-manager: status |
New |
Incomplete |
|
| 2008-09-09 23:01:43 |
Alexander Sack |
network-manager: statusexplanation |
|
This looks like a driver issue. Does running
iwconfig wlan0 essid YOUESSID
while network-manager tries to associate workaround this issue?
Please attach the complete syslog.
what does modinfo iwl3945 dump to the terminal?
In any case, i think that issue should be fixed in intrepid kernel. If you have a chance please test it too.
Thanks!
|
|
| 2008-09-20 10:17:50 |
macavity |
bug |
|
|
added attachment 'syslog.txt' (syslog.txt) |
| 2009-03-16 23:50:34 |
Dimitrios Symeonidis |
network-manager (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2009-03-16 23:50:34 |
Dimitrios Symeonidis |
network-manager (Ubuntu): statusexplanation |
This looks like a driver issue. Does running
iwconfig wlan0 essid YOUESSID
while network-manager tries to associate workaround this issue?
Please attach the complete syslog.
what does modinfo iwl3945 dump to the terminal?
In any case, i think that issue should be fixed in intrepid kernel. If you have a chance please test it too.
Thanks!
|
david, since you haven't reported any new occurrences of the issue, I'm assuming it's fixed for you, so marking accordingly. if this is not the case, feel free to switch back to new... |
|
