Michael Graff <explorer@flame.org> writes:

> I plan on cleaning up the driver and committing it later this week,
> along with a program, probably called wimonitor, which will display
> the nearby access points.

With today's sources, which I believe includes this code, the wi
interface on my iBook (dual USB) is crankier than it was before. It's
been rock-solid since the wi at obio support went in. It probes as:

wi0 at obio0 offset 0x30000 irq 57: 802.11 address 00:30:65:01:4a:e0
wi0: using Lucent chip or unknown chip

Today, several times I've gotten the following string of messages, and then
lost my connection until I ifconfig'd down and back up.

I use the connection for NFS, ssh, web surfing.. pretty normal-ish
workstation load.

wi0: device timeout
wi0: init failed
wi0: timeout in wi_seek to 1d14/0; last status 4000
wi0: xmit failed
wi0: device timeout
wi0: init failed
wi0: timeout in wi_seek to fce0/0; last status 8011
wi0: timeout in wi_seek to fc07/0; last status 8011
wi0: timeout in wi_seek to fc81/0; last status 8011
wi0: timeout in wi_seek to fc00/0; last status 8011
wi0: timeout in wi_seek to fc83/0; last status 8011
wi0: timeout in wi_seek to fc84/0; last status 8011
wi0: timeout in wi_seek to fc06/0; last status 8011
wi0: timeout in wi_seek to fc09/0; last status 8011
wi0: timeout in wi_seek to fc0c/0; last status 8011
wi0: timeout in wi_seek to fc2d/0; last status 8011
wi0: timeout in wi_seek to fc04/0; last status 8011
wi0: timeout in wi_seek to fc02/0; last status 8011
wi0: timeout in wi_seek to fc03/0; last status 8011
wi0: timeout in wi_seek to fc0e/0; last status 8011
wi0: timeout in wi_seek to fc01/0; last status 8011
wi0: timeout in wi_seek to fc85/0; last status 8011
wi0: timeout in wi_seek to fc20/0; last status 8011
wi0: timeout in wi_seek to fcb1/0; last status 8011
wi0: timeout in wi_seek to fcb0/0; last status 8011
wi0: timeout in wi_seek to fc80/0; last status 8011
wi0: failed to allocate 1594 bytes on NIC
wi0: tx buffer allocation failed
wi0: interface not running

        - Nathan