Wireless Driver Required Changes: Difference between revisions
m (Wireless Driver Required Patches moved to Wireless Driver Required Changes: More meaningful name) |
No edit summary |
||
Line 14: | Line 14: | ||
A suggested fix [http://dev.laptop.org/ticket/6589#comment:13||can be found here]. |
A suggested fix [http://dev.laptop.org/ticket/6589#comment:13||can be found here]. |
||
==== ethtool -S msh0 returning noise ==== |
|||
The command ethtool -S eth0 should return useful NIC statistics, but it is dumping senseless numbers instead. |
|||
This is described in [http://dev.laptop.org/ticket/6589|this ticket] and is believed to be related to the driver. A patch/fix is still needed. |
Revision as of 16:52, 3 April 2008
This page lists known issues related to the Wireless Driver, pointing to track numbers and suggested driver patches (where applicable) to fix the issues.
Probe Retry Limit
Probes Request/Response for/from XOs are maintained for the sole goal of not breaking ad-hoc mode (which can be implemented passively and, in the end, brings no obvious advantages over the mesh mode). As it is a very bursty and demanding control traffic, particularly in dense networks, the number of retries, currently set to 2, should be reduced, if not removed altogether.
5.110.22.p6 allows probe response retries to be set from driver, from 0 (no probe response) to 15.
But a driver patch is required and be found here.
Not responding to RREQs
In this bug, the XO stops responding to mesh path requests frames (RREQs). The main cause seems to be that the driver is not waiting long enough for the firmware to download.
A suggested fix be found here.
ethtool -S msh0 returning noise
The command ethtool -S eth0 should return useful NIC statistics, but it is dumping senseless numbers instead.
This is described in ticket and is believed to be related to the driver. A patch/fix is still needed.