registry team mailing list archive
-
registry team
-
Mailing list archive
-
Message #03968
[Bug 190515] Re: [Hardy][Intrepid] Low bandwidth with rt2400 / rt2500 drivers
OK, this appears to be an effective workaround: disable power management
for the wireless chipset. As follows:
Applications - Accessories - Terminal
type (use copy/paste):
gksudo gedit /etc/rc.local
Press Enter.
Add this line, just above exit 0 (use copy/paste):
iwconfig wlan0 power off
So it should become something like this (example):
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
iwconfig wlan0 power off
exit 0
Save, close and reboot. The problem should be fixed permanently.
Please report your findings.
** Tags added: lucid
** Description changed:
+ Added description:
+
+ This bug is still present in 10.04 Lucid Lynx. In comment #161 I've
+ described a workaround that should be effective, at least in Lucid.
+
+ ----------------
Binary package hint: linux-ubuntu-modules-2.6.24-8-generic
I'm using hardy alpha 4 (on Linux nand-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux ) and I was testing a PCMCIA rt2500 card :
- 03:00.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
+ 03:00.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
with WEP encryption, near the AP :
- wlan0 IEEE 802.11g ESSID:"DartyBox_005c"
- Mode:Managed Frequency:2.462 GHz Access Point: 00:09:5B:EB:32:20
- Bit Rate=1 Mb/s Tx-Power=27 dBm
- Retry min limit:7 RTS thr:off Fragment thr=2346 B
- Link Quality=43/100 Signal level=-54 dBm
- Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
- Tx excessive retries:0 Invalid misc:0 Missed beacon:0
+ wlan0 IEEE 802.11g ESSID:"DartyBox_005c"
+ Mode:Managed Frequency:2.462 GHz Access Point: 00:09:5B:EB:32:20
+ Bit Rate=1 Mb/s Tx-Power=27 dBm
+ Retry min limit:7 RTS thr:off Fragment thr=2346 B
+ Link Quality=43/100 Signal level=-54 dBm
+ Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
+ Tx excessive retries:0 Invalid misc:0 Missed beacon:0
-
- The connection is working, but slowly (40 kb/s). It's due to the bit rate being set to 1Mb/s. If I manually set the rate to 54Mb/s, then I got the 900 kb/s I expect from my AP.
+ The connection is working, but slowly (40 kb/s). It's due to the bit
+ rate being set to 1Mb/s. If I manually set the rate to 54Mb/s, then I
+ got the 900 kb/s I expect from my AP.
I have also tested with one other RT based I have, a RT73 one, and the
bit rate goes automatically to 54Mb/s...
** Description changed:
- Added description:
+ Added description on June, 4th 2010:
This bug is still present in 10.04 Lucid Lynx. In comment #161 I've
described a workaround that should be effective, at least in Lucid.
+
+ --Pjotr12345
----------------
Binary package hint: linux-ubuntu-modules-2.6.24-8-generic
I'm using hardy alpha 4 (on Linux nand-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux ) and I was testing a PCMCIA rt2500 card :
03:00.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)
with WEP encryption, near the AP :
wlan0 IEEE 802.11g ESSID:"DartyBox_005c"
Mode:Managed Frequency:2.462 GHz Access Point: 00:09:5B:EB:32:20
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality=43/100 Signal level=-54 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
The connection is working, but slowly (40 kb/s). It's due to the bit
rate being set to 1Mb/s. If I manually set the rate to 54Mb/s, then I
got the 900 kb/s I expect from my AP.
I have also tested with one other RT based I have, a RT73 one, and the
bit rate goes automatically to 54Mb/s...
--
[Hardy][Intrepid] Low bandwidth with rt2400 / rt2500 drivers
https://bugs.launchpad.net/bugs/190515
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for rt2x00 Project.