commands to rt2860sta fails

Bug #437804 reported by Michael Rasmussen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

distro: ubuntu 9.04
hardware: asus eee 901
driver: rt2860sta
wicd: 1.5.9

When connection to an AP wicd sends this command sequence:
2009/09/27 20:56:16 :: Putting interface up...
2009/09/27 20:56:16 :: ifconfig ra0 up
2009/09/27 20:56:16 :: iwconfig ra0 mode Managed
2009/09/27 20:56:16 :: ['iwconfig', 'ra0', 'essid', 'kastrupBG', 'channel', '7', 'ap', '00:20:A6:56:58:5F']
2009/09/27 20:56:16 :: Running DHCP
2009/09/27 20:56:16 :: /sbin/dhclient ra0

Apparently the command iwconfig ra0 mode Managed fails making all subsequent commands to the driver fail. This means the connection cannot be made. On the other hand skipping iwconfig ra0 mode Managed and going directly to ['iwconfig', 'ra0', 'essid', 'kastrupBG', 'channel', '7', 'ap', '00:20:A6:56:58:5F'] has the expected result, a connection is established.

Revision history for this message
Dan O'Reilly (oreilldf) wrote :

I think this is probably fixed in 1.6.2, because we issue the "iwconfig mode" command with the interface down. Running it with the interface up like we did in 1.5.9 is most likely the reason for the failure.

Changed in wicd:
status: New → Incomplete
Revision history for this message
Michael Rasmussen (mir) wrote :

Hi Dan,

I tried your suggestion of sending the command iwconfig ra0 mode Managed before issuing ifconfig ra0 up but this is not possible because you get this error message: "Error in wireless request "Set Mode" (8806) : SET failed on device ra0 ; Network is down". And did not change a thing. Next I tried to upgrade to latest version - 1.6.2.2, and still seeing the same behavior. Do you think it might be a bug in the rt2860sta driver?

To me it seems issuing the command "set mode" to the driver means the driver stops being responsive.

Revision history for this message
Michael Rasmussen (mir) wrote :

I totally forgot an important information: I only see this behavior when a turn the wifi off and the on again using Fn+F2.

Revision history for this message
Michael Rasmussen (mir) wrote :

A break through:-) Sending this command "iwconfig ra0 mode Managed key off" enables wicd to make a working connection. Whether this is an anomaly for rt2860sta I don't know . E.g. instead of doing:
ifconfig ra0 up
iwconfig ra0 mode Managed
['iwconfig', 'ra0', 'essid', 'kastrupBG', 'channel', '7', 'ap', '00:20:A6:56:58:5F']

wicd should do it this way:
ifconfig ra0 up
iwconfig ra0 mode Managed key [off|WEP] *)
['iwconfig', 'ra0', 'essid', 'kastrupBG', 'channel', '7', 'ap', '00:20:A6:56:58:5F']

*) if using WPA or WPA2 key off should be fired too.

Revision history for this message
Michael Rasmussen (mir) wrote :

Attached is a small path which solves the issue.

affects: wicd → linux
Revision history for this message
penalvch (penalvch) wrote :

Michael Rasmussen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

affects: linux → linux (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.