Wireless Driver Required Changes: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
[http://dev.laptop.org/ticket/6706|Firmware 5.110.22.p6] allows probe response retries to be set from driver, from 0 (no probe response) to 15.
[http://dev.laptop.org/ticket/6706|Firmware 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 [http://dev.laptop.org/attachment/ticket/6706/0002-Probe_Res_Retry_Limit.patch|can be found here].
But a driver patch is required and [http://dev.laptop.org/attachment/ticket/6706/0002-Probe_Res_Retry_Limit.patch can be found here].


==== Not responding to RREQs ====
==== Not responding to RREQs ====


In [http://dev.laptop.org/ticket/6589| 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.
In [http://dev.laptop.org/ticket/6589 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 [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 ====
==== ethtool -S msh0 returning noise ====
Line 19: Line 19:
The command ethtool -S eth0 should return useful NIC statistics, but it is dumping senseless numbers instead.
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.
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 17:11, 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

Probe Request/Response exchange between XOs is maintained for the sole reason 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 can 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 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 this ticket and is believed to be related to the driver. A patch/fix is still needed.