Comment 8 for bug 315467

Will this huge pb for such a common wireless hardware be considered one day?

In 2.6.24-24 it's still there:

****
May 8 08:46:12 marsupilami kernel: [ 8384.134659] wlan0: No ProbeResp from current AP 00:14:bf:XX:XX:XX - assume out of range
May 8 08:46:12 marsupilami kernel: [ 8384.767249] iwl3945: Error sending REPLY_RXON: time out after 500ms.
May 8 08:46:12 marsupilami kernel: [ 8384.767260] iwl3945: Error clearing ASSOC_MSK on current configuration (-110).
May 8 08:46:13 marsupilami kernel: [ 8385.321903] iwl3945: Error sending REPLY_RXON: time out after 500ms.
(...)
May 8 08:46:30 marsupilami kernel: [ 8402.786914] iwl3945: Error clearing ASSOC_MSK on current configuration (-110).
May 8 08:46:31 marsupilami kernel: [ 8403.514440] iwl3945: Error sending REPLY_RXON: time out after 500ms.
May 8 08:46:31 marsupilami kernel: [ 8403.514451] iwl3945: Error clearing ASSOC_MSK on current configuration (-110).
May 8 08:46:31 marsupilami kernel: [ 8403.746298] iwl3945: No space for Tx
May 8 08:46:31 marsupilami kernel: [ 8403.746309] iwl3945: Error sending REPLY_RXON: iwl_enqueue_hcmd failed: -28
May 8 08:46:31 marsupilami kernel: [ 8403.746314] iwl3945: Error clearing ASSOC_MSK on current configuration (-28).
****

Note my AP neither laptop came "out of range", some poor TX/RX level management by this iwl driver may be considered... Also note under windows XP double-boot everithing is perfect... as it was under Dapper with ipw driver that should really have stayed unchanged.

Regards