- This is definitely a regression. In Gutsy (even Feisty!) there was a reliable version of the driver. In Hardy there is a crappier version related to the code that was merged into the main linux tree. I quote from the front page rtx00 upstream web site:
rt2x00 enters mainline kernel - January 2008
Hi All,
two days ago, January 24th, Linux Kernel 2.6.24 was released. This is the first mainline kernel that includes (sadly a somewhat buggy) rt2x00 release.
- It is more than just the rate issue. The code seems to have other problems. I have very variable success with associating under the same setup that worked perfectly under the hardy rt2500pci module.
- I have linux-backports-modules-2.6.24-16-generic installed. doesn't help. Sometimes I get good performance, other times I can't even associate.
What can be done to fix this? It kills/blocks/subverts networking on this popular network hardware (rt2500) in Hardy.
Some short comments:
- This is definitely a regression. In Gutsy (even Feisty!) there was a reliable version of the driver. In Hardy there is a crappier version related to the code that was merged into the main linux tree. I quote from the front page rtx00 upstream web site:
rt2x00 enters mainline kernel - January 2008
Hi All,
two days ago, January 24th, Linux Kernel 2.6.24 was released. This is the first mainline kernel that includes (sadly a somewhat buggy) rt2x00 release.
- It is more than just the rate issue. The code seems to have other problems. I have very variable success with associating under the same setup that worked perfectly under the hardy rt2500pci module.
- I have linux-backports -modules- 2.6.24- 16-generic installed. doesn't help. Sometimes I get good performance, other times I can't even associate.
What can be done to fix this? It kills/blocks/ subverts networking on this popular network hardware (rt2500) in Hardy.