Re: Wifi troubles: device timeout, init failed

["N.J. Reuvers" <n.j.reuvers@home.nl>]

List,

I have solved my problem with the following error messages:
 /bsd: wi0: device timeout
 /bsd: wi0: init failed

The solution for me was to change the tx rate in wicontrol:

Previous hostname.wi0 (malfunctioned)
inet 10.0.1.1 255.255.255.0 10.0.1.255 media DS11 mediaopt ibss
!wicontrol wi0 -A 2 -p 6 -t 11 -f 7 -k boguspassword -v 1 -e 1 -n
welhaak

Current Hostname.wi0
inet 10.0.1.1 255.255.255.0 10.0.1.255 media DS11 mediaopt ibss
!wicontrol wi0 -A 2 -p 6 -t 3 -f 7 -k boguspassword -v 1 -e 1 -n welhaak

The difference lies in the -t option. This sets the transfer rate. The
setting in the current hostname.wi0 is "Auto Rate Select (High)". In the
previous hostname.wi0 -t was set to 11. This means "Fixed Turbo
(11Mbps)". Now I do have a prism 2.5 card which should support the
setting 11. But obvious, something's not completely right.

Setting -t 3 works for me. Just wanted to let you know.

Regards,
Nils

-----Oorspronkelijk bericht-----
Van: Todd C. Miller [mailto:Todd.Miller@courtesan.com] 
Verzonden: maandag 26 april 2004 19:27
Aan: N.J. Reuvers
CC: misc@openbsd.org
Onderwerp: Re: Wifi troubles: device timeout, init failed


In message <000501c42b02$d4e01240$0401a8c0@cc348776a>
	so spake "N.J. Reuvers" (n.j.reuvers):

> I am having almost the same problems now. I have upgraded my kernel to

> 3.5 -current (took the snapshot from 24 april 2004). This message is 
> turning up in my message log:

Are you using WEP?  If so it may be that your HostAP is getting hammered
and the card is unable to keep up with the WEP decryption.

Try editing wi_attach() and changing:
    sc->wi_cmd_count = 500;

To:
    sc->wi_cmd_count = 1500;

And see if that helps.

Alternately, you could use software WEP.

 - todd