'network interface is down' when trying to connect to network using rt73
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rutilt (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Gutsy |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: rutilt
Using rt73 ( on advent laptop)
This was previously working fine until the last upgrade.
It will scan and find wireless networks, and how can it do that if the interface is down?(it might be possible it just seems counter intuitive)
tried ifconfig no wlan0, oh great how did that happen?
does appear if I check iwconfig
tried ifdown & ifup yeah that does little of import...
downloaded compiled and installed latest serialmonkey driver (I thought it could be a problem so best to be as up to date as possible)
no joy exactly same symptoms and behaviour
current solution:-
if you downgrade to the previous version of rutilt it works perfectly again (currently using the latest serialmonkey driver)
TEST CASE:
note: you need a wireless card with the ralink r73 (aka RT2501USB) chipset to test this.
1) Start rutilt, check that the version is 0.15-0ubuntu5.1 (Options tab -> About).
2) In rutilt, select a profile (Profiles tab) and hit apply (you should be prompted for the admin password).
3) A window with 'network interface is down' will appear immediately; no wireless connection will be established.
4) Quit rutilt.
5) Add the gutsy-proposed repository by adding this line to your /etc/apt/
deb http://
6) Update and upgrade with your preferred package manager.
7) Start rutilt, check that the version is 0.15-0ubuntu5.2 (Options tab -> About).
8) In rutilt, select a profile (Profiles tab) and hit apply (you should be prompted for the admin password).
9) The wireless connection should be established immediately without any error prompt.
Changed in rutilt: | |
importance: | Undecided → Low |
status: | Incomplete → Triaged |
Changed in rutilt: | |
assignee: | nobody → norsetto |
status: | Triaged → In Progress |
importance: | Undecided → Medium |
status: | New → Confirmed |
description: | updated |
First of all, thank you for contacting us.
I'm trying to understand your report, especially what problem you are reporting.
In the last update we added a patch to improve the behavior with legacy drivers, and I'm wondering if what you are seeing are some side effects of it.
Can you perhaps describe more in details what is the problem you are experiencing?