| 2007-07-28 14:42:11 |
Chris Rowson |
bug |
|
|
added bug |
| 2007-07-30 13:29:09 |
Chris Rowson |
marked as duplicate |
|
64173 |
|
| 2007-08-06 11:11:01 |
Alexander Sack |
removed duplicate marker |
64173 |
|
|
| 2007-08-06 11:11:15 |
Alexander Sack |
description |
Binary package hint: network-manager
Using network manager and the madwifi drivers (atheros chipset) cause the user to be disconnected from the access point at regular intervals.
This bug seems to be knocking around in lots of incarnations and the problem seems to be this:
1) The madwifi drivers don't support 'background scanning'
2) Network manager instructs the atheros based card to scan for access points in the background whilst it is already associated with an access point.
Because the madwifi drivers don't support background scanning, when the instruction to begin background scanning is given then the network card disassociates with the access point, disconnecting the user.
This bug is a show stopper for any new user, as they are unlikely to dig into the problem to find out what's causing it.
Bugs with similar info:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/37821/
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/105637
Changing network manager so that it only scans for access points, when the card is not connected to an access point seems to fix the problem. |
Maybe dupe of 64173
Binary package hint: network-manager
Using network manager and the madwifi drivers (atheros chipset) cause the user to be disconnected from the access point at regular intervals.
This bug seems to be knocking around in lots of incarnations and the problem seems to be this:
1) The madwifi drivers don't support 'background scanning'
2) Network manager instructs the atheros based card to scan for access points in the background whilst it is already associated with an access point.
Because the madwifi drivers don't support background scanning, when the instruction to begin background scanning is given then the network card disassociates with the access point, disconnecting the user.
This bug is a show stopper for any new user, as they are unlikely to dig into the problem to find out what's causing it.
Bugs with similar info:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/37821/
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/105637
Changing network manager so that it only scans for access points, when the card is not connected to an access point seems to fix the problem. |
|
| 2007-08-06 11:12:19 |
Alexander Sack |
description |
Maybe dupe of 64173
Binary package hint: network-manager
Using network manager and the madwifi drivers (atheros chipset) cause the user to be disconnected from the access point at regular intervals.
This bug seems to be knocking around in lots of incarnations and the problem seems to be this:
1) The madwifi drivers don't support 'background scanning'
2) Network manager instructs the atheros based card to scan for access points in the background whilst it is already associated with an access point.
Because the madwifi drivers don't support background scanning, when the instruction to begin background scanning is given then the network card disassociates with the access point, disconnecting the user.
This bug is a show stopper for any new user, as they are unlikely to dig into the problem to find out what's causing it.
Bugs with similar info:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/37821/
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/105637
Changing network manager so that it only scans for access points, when the card is not connected to an access point seems to fix the problem. |
Maybe dupe of 64173
Binary package hint: network-manager
Using network manager and the madwifi drivers (atheros chipset) cause the user to be disconnected from the access point at regular intervals.
This bug seems to be knocking around in lots of incarnations and the problem seems to be this:
1) The madwifi drivers don't support 'background scanning'
2) Network manager instructs the atheros based card to scan for access points in the background whilst it is already associated with an access point.
Because the madwifi drivers don't support background scanning, when the instruction to begin background scanning is given then the network card disassociates with the access point, disconnecting the user.
This bug is a show stopper for any new user, as they are unlikely to dig into the problem to find out what's causing it.
Bugs with similar info:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/37821/
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/105637
Changing network manager so that it only scans for access points, when the card is not connected to an access point seems to fix the problem. |
|
| 2007-08-06 11:12:19 |
Alexander Sack |
title |
Gutsy: network manager + madwifi drivers = disconnects |
[madwifi] Gutsy: network manager + madwifi drivers = disconnects |
|
| 2007-08-09 08:29:37 |
Alexander Sack |
network-manager: status |
New |
Fix Released |
|
| 2007-08-09 08:29:37 |
Alexander Sack |
network-manager: statusexplanation |
|
for now lets assumed that this is fixed in 0.6.5-0ubuntu9. If you ever see this again, please ping me in given channel.
Thanks,
- Alexander |
|
