Bug 158720 - ipw2200 does not work anymore with 54Mb/s rate
ipw2200 does not work anymore with 54Mb/s rate
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: John W. Linville
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-05-25 03:16 EDT by Ulrich Drepper
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-10 10:06:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ulrich Drepper 2005-05-25 03:16:38 EDT
Description of problem:
With previous kernels (up to 2.6.11-1.1312) I used RATE=54M in my configu file
for the ipw2200 interface.  In the recent kernels (-1.133x and later) this
doesn't work anymore.  If I remove the line and let the kernel/card pick the
rate, the interface works.

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

How reproducible:

Steps to Reproduce:
1.start said kernel on machine with ipw2200 and RATE=54M in iface config
Actual results:
no network connection

Expected results:
working network

Additional info:
Comment 1 Ulrich Drepper 2005-05-26 04:02:30 EDT
Well, without the RATE parameter the card still automatically selects 54M as the
rate.  But I think it is still a regression that it doesn't work anymore if the
rate is explicitly specified.
Comment 2 Dave Jones 2005-05-26 20:11:17 EDT
I dropped back to the rev of the driver that was in FC3 for the final FC4
release as the updated one brought more problems than it fixed. I'll look at
doing an update again sometime after the release.
Comment 3 Ulrich Drepper 2005-05-28 00:55:54 EDT
I think this problem appears since with the old driver, any

iwconfig ethX rate xxx

call will simply fail while with the new one the driver actually does/tries to
do something.  We'll see when the driver gets reenabled.
Comment 4 Dave Jones 2005-10-06 03:21:43 EDT
now that this got merged upstream, we ended up with a different version of the
driver in rawhide. How is this behaving wrt to this bug ?
Comment 5 John W. Linville 2005-11-10 10:06:56 EST
Closed due to lack of response.  Please reopen when the requested information 
becomes available...thanks! 

Note You need to log in before you can comment on or make changes to this bug.