Red Hat Bugzilla – Bug 505911
Intel 3945abg wireless bandwidth
Last modified: 2010-01-05 06:42:24 EST
Description of problem:
bandwith limited to around 1mb/s on intel wireless 3945abg card in fedora 11.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot fedora 11 with an intel 3945abc wireless card
tested on dell xps m1530 laptop & inspiron 9400 laptop. problem not present in fedora 10/xp triboot on same laptops.
on intital connection to the wireless network all bandwidth is availble for a few minutes before it gets limited.
issue is present in some versions of other distros maybe something kernel/driver related breaking?
I have experienced this problem on my thinkpad t60 with the intel 3945 wireless card. Initially I'm able to access any wireless AP without any problems, but then the connection slows to a trickle for no apparent reason.
Ubuntu Jaunty users with intel wireless cards are reporting a similar problem under this bug ( https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/348204 )
I know that there were problems with the intel drivers around the time that Fedora 11 / Ubuntu 9.04 were released. Is there anything that can be done to remedy this on a Fedora 11 system?
Does problem still reproducible on current F11 kernel (2.6.30 based)?
What is network configuration: type (a,b,g), encryption ?
Sorry for the late reply, but I had switched to using Xubuntu because of this bug. I'm glad to report now, though, that this bug appears to be fixed for me now, thus enabling me to use Fedora for regular tasks.
The wireless network is a mixed B/G access point using WPA2 Personal encryption with the TKIP algorithm.
I hope this helps, but please let me know if you need more info. Thank you for your work in resolving this bug.
(In reply to comment #3)
> I'm glad to report now, though, that this bug appears to be fixed for me
> now, thus enabling me to use Fedora for regular tasks.
> I hope this helps, but please let me know if you need more info. Thank you for
> your work in resolving this bug.
Sorry, I'm a bit confused. Does this bug needs any additional work ?
I am no longer experiencing this problem. As far as I am concerned, this bug requires no additional work. Thanks very much.
What about you, did you try to upgrade F11 kernel?
According to comment 5 I'm closing this bug.