[madwifi] Gutsy: network manager + madwifi drivers = disconnects

Bug #128911 reported by Chris Rowson
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Edgy by Chris Rowson
Nominated for Feisty by Chris Rowson
Nominated for Gutsy by Chris Rowson

Bug 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.

Revision history for this message
Chris Rowson (christopherrowson) wrote :

linux-restricted-modules-2.6.20 ships with madwifi 0.9.1 - Current WEXT compliance should have been added to this release as requested here http://madwifi.org/ticket/462

Is it worth just applying the patch which has already been submitted for this? It looks like the problem could possibly lie with network manager after all. http://launchpadlibrarian.net/6824480/reconnect-timeout.diff.gz

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 128911] Re: Gutsy: network manager + madwifi drivers = disconnects

On Mon, Jul 30, 2007 at 10:20:44AM -0000, Chris Rowson wrote:
> linux-restricted-modules-2.6.20 ships with madwifi 0.9.1 - Current WEXT
> compliance should have been added to this release as requested here
> http://madwifi.org/ticket/462

So maybe start using generic wext driver when we see ath_pci kernel
driver would cure us?

 - Alexander

description: updated
Revision history for this message
Alexander Sack (asac) wrote : Re: Gutsy: network manager + madwifi drivers = disconnects

i would really like to investigate if using other wpa_supplicant driver helps. Can you ping me on irc.freenode.net (asac) ... channels: e.g. #ubuntu-devel #ubuntu-mozillateam

description: updated
Revision history for this message
Chris Rowson (christopherrowson) wrote :

Hi Alex,

I just noticed that the latest upgrade from network-manager 0.6.5-0ubuntu7 to 0.6.5-0ubuntu9 in Gutsy applys a patch to increase the timeout. Crossed fingers, so far it seems to be OK (although I haven't had much time to test for long). Do you still want to investigate wpa_supplicant?

Chris

Revision history for this message
Alexander Sack (asac) wrote :

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

Changed in network-manager:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.