Bug 446933

Summary: NM assigns max wireless speed to ralink card of 1MB/s
Product: [Fedora] Fedora Reporter: Richard Jolly <richard.jolly>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9CC: dcbw, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-20 19:15:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of NM Connection Info + lsmod & lspci outputs none

Description Richard Jolly 2008-05-16 17:23:04 UTC 
Description of problem:NM appears to fix WPA PSK connection speed to 1MB/s on a
RALink Wireless card (03:03.0 Network controller: RaLink RT2500 802.11g
Cardbus/mini-PCI (rev 01). Changes to the connection detail appears to be make
no change to the speed.


Version-Release number of selected component (if applicable):
NM Applet 0.7.0

How reproducible:
Ever boot up occurs

Steps to Reproduce:
1.Log into F9
2.WPA Connection initiated
3.Connection details report 1 MB/s and it does seem to run at this slow speed on
browsing
  
Actual results:
1 MB/s

Expected results:

Auto - 54 MB/s - router approx 6 feet away!
Additional info:

screenshot of NM Connection Information - see attached
output of uname - 2.6.25.3-18.fc9.i686
lsmod - see attachment
lspci - see attachment
Comment 1 Richard Jolly 2008-05-16 17:23:04 UTC 
Created attachment 305714 [details]
Screenshot of NM Connection Info + lsmod & lspci outputs
Comment 2 Dan Williams 2008-05-16 19:18:19 UTC 
Likely an issue with the kernel driver rate adaptation, since right now NM
doesn't do anything with the data rate.
Comment 3 John W. Linville 2008-05-20 19:15:14 UTC 

*** This bug has been marked as a duplicate of 443203 ***