Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-backports-modules-2.6.22 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
linux-backports-modules-2.6.24 (Ubuntu) |
Fix Released
|
High
|
Stefan Bader | ||
Hardy |
Fix Released
|
High
|
Stefan Bader | ||
linux-ubuntu-modules-2.6.22 (Ubuntu) |
Won't Fix
|
Medium
|
Ubuntu Kernel Network Team | ||
Hardy |
Won't Fix
|
Medium
|
Ubuntu Kernel Network Team | ||
linux-ubuntu-modules-2.6.24 (Ubuntu) |
Won't Fix
|
High
|
Stefan Bader | ||
Hardy |
Won't Fix
|
High
|
Stefan Bader |
Bug Description
===
The poll shows that most of the problems with wireless networking are problems with ralink cards in Ubuntu.
POLL: What wireless chipset are you having a problem with in Gutsy?
http://
The bug occurs commonly and it's very important - and will be easy - to fix it.
=======
Cards don't work because of the invalid drivers (extremely slow connection, no connection, connection lost, lack of the wpa support) included in Ubuntu.
Work-around: To install the proper driver from serialmonkey.
SOLUTION:
1. Find out which version of a serialmonkey driver works properly with each ralink card.
2. Implement ralink serialmonkey drivers in Ubuntu.
http://
Most likely the newest CVS version of each ralink driver works correctly.
===
Please write which drivers are known to work and which are invalid.
==
Exemplary posts on ubuntuforums.org:
Linksys WUSB54G V4 (rt2570-based card)
http://
HOWTO: RT73 (RT71) serialmonkey drivers
http://
=======
OLD BUG DESCRIPTION:
=======
I configured my rt2400 card connection in network-admin succesfully but the connection is extremely slow.
Ping works, but I can't get into any website, download packages through Synaptic even if waiting a few minutes.
The card was recognized by Feisty as ra0, but now it's wlan0 in Gutsy.
PING onet.pl (213.180.130.200) 56(84) bytes of data.
64 bytes from 213.180.130.200: icmp_seq=4 ttl=52 time=93.6 ms
64 bytes from 213.180.130.200: icmp_seq=5 ttl=52 time=82.8 ms
64 bytes from 213.180.130.200: icmp_seq=6 ttl=52 time=96.9 ms
The problem does not occur when running Feisty and when running Gutsy with Feisty kernel (2.6.20.x). The newest Gutsy and Hardy kernel still generates problems with ralink card. The transfer rate is extremly low - 678 b/s - 1391 b/s.
Related branches
Changed in linux-source-2.6.22: | |
importance: | Undecided → Medium |
status: | New → Incomplete |
Changed in linux-source-2.6.22: | |
assignee: | leannogasawara → ubuntu-kernel-network |
status: | Incomplete → Confirmed |
description: | updated |
description: | updated |
Changed in linux-ubuntu-modules-2.6.24: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux-ubuntu-modules-2.6.24: | |
importance: | Medium → High |
Changed in linux-ubuntu-modules-2.6.24: | |
milestone: | none → hardy-alpha-4 |
status: | Triaged → Fix Released |
Changed in linux-ubuntu-modules-2.6.24: | |
status: | Fix Released → Confirmed |
Changed in linux-ubuntu-modules-2.6.24: | |
milestone: | hardy-alpha-4 → ubuntu-8.04 |
Changed in linux-ubuntu-modules-2.6.24: | |
assignee: | ubuntu-kernel-team → stefan-bader-canonical |
Changed in linux-ubuntu-modules-2.6.24: | |
milestone: | ubuntu-8.04 → ubuntu-8.04.1 |
milestone: | ubuntu-8.04.1 → ubuntu-8.04 |
Changed in linux-backports-modules-2.6.22: | |
status: | New → Invalid |
Changed in linux-backports-modules-2.6.24: | |
assignee: | nobody → stefan-bader-canonical |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.1 |
Changed in linux-ubuntu-modules-2.6.24: | |
milestone: | ubuntu-8.04 → none |
Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed an updated kernel, 2.6.22-11.32, was recently released. Can you try updating to this newer kernel and verify this bug is still an issue for you? Also, I just want to clarify that you do not see this problem when running Feisty correct? Thanks in advance!