Date: Mon, 20 Mar 2006 14:06:05 -0800 From: Darren Pilgrim <darren.pilgrim@bitfreak.org> To: dima <_pppp@mail.ru> Cc: Max Laier <max@love2party.net>, freebsd-net@freebsd.org Subject: Re: New version of iwi(4) - Call for testers [regression!] Message-ID: <441F274D.1030107@bitfreak.org> In-Reply-To: <E1FLRfM-000PcS-00._pppp-mail-ru@f11.mail.ru> References: <E1FLRfM-000PcS-00._pppp-mail-ru@f11.mail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
dima wrote: > > I had a chance to test the driver more throughly today. It can't connect > to some access points. Sometimes reboot helps, sometimes not. I didn't > experience this with the driver currently present in the tree; well, I > used /usr/ports/net/iwi-firmware (not the kmod version). This can be the > case. > > When I run the 2 following commands in the script it sometimes > fails to load the firmware properly: > > # ifconfig iwi0 inet 192.168.1.2 netmask 255.255.255.0 up > # iwiconfig -i iwi0 -d /boot/firmware -m bss > > It seems that if_iwi module needs some time to initialize the card > properly (I have a 2915 one); and it's really ready to boot a firmware > in several milliseconds. What is the "iwiconfig" program and why are you using it with Max's driver? The first command is all that is needed to get the interface up and configured, assuming you're using static IPs on an open AP.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441F274D.1030107>