extremely odd wi(4) scenario

Dan Ponte dcp1990 at neptune.atopia.net
Wed Jun 8 02:30:35 GMT 2005


Hi all.
	I posted quite a while back about some problems I was having
with firmware v1.4.9. So, tonight I decided to try other versions.
	Using my windows machine (which also dual boots FreeBSD), I
upgraded the card to 1.8.2. It worked fine in windows, and also in
FreeBSD on that machine.
	I then put the card back in the server. This time, however,
status was always "no carrier," and with hw.wi.debug=1, it would always
go from state "INIT -> INIT." Now for the very weird part: if I ran
dstumbler with the -o option, the link light turned on, it displayed
"INIT -> RUN", and it saw my AP, but I still could not connect. Upon
quitting dstumbler, status went back to INIT. If I put the card in
monitor or hostap mode, it goes to RUN but I obviously cannot do
anything since this is a BSS network.
	This same thing happens on 1.5.6 and 1.7.4. I am currently using
1.3.4, which I had ok luck with before I went to 1.4.9.
	I'm stumped. Maybe you aren't.
-Dan
-- 
Dan Ponte
http://www.theamigan.net/
All of the true things I am about to tell you are shameless lies.
		-- The Book of Bokonon / Kurt Vonnegut Jr.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20050607/09573486/attachment.bin


More information about the freebsd-hardware mailing list