From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 00:54:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EDA216A41F for ; Tue, 26 Jul 2005 00:54:07 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 497CD43D45 for ; Tue, 26 Jul 2005 00:54:07 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from tirun (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 581EB82 for ; Mon, 25 Jul 2005 20:54:06 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: freebsd-current@freebsd.org Content-Type: text/plain Date: Mon, 25 Jul 2005 20:54:04 -0400 Message-Id: <1122339244.13570.17.camel@tirun> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently reboots X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 00:54:07 -0000 I've been trying to use the iwi driver with wpa_supplicant to autodetect my home network (WPA-TKIP) and campus network (open). So far, I've had no success getting it to associate with my Linksys BEFW11S4 router/AP; I can't figure out how to get a key in common between them --- an ASCII key simply fails, and wpa_supplicant and the Linksys have very different ideas about the length of hex keys (the Linksys wants 40 hex digits). Things are even worse trying to use it on campus: the driver continually spews "iwi0: unknown authentication state 1" and "iwi0: fatal error" messages, and after a few minutes the machine (IBM Thinkpad T42, 2378-R4U) silently reboots. No panic message, no core dump, just freezes for about a second and then displays the BIOS screen (much as if I'd hit a reset button, not that there is one aside from holding the power button for 10 seconds). This happens even if the only entry in /etc/wpa_supplicant.conf is for the open network. Both networks are 802.11b. I've been unable to collect any significant debugging information from the latter because of the silent reboot. Is iwi considered usable at this point, or should I give up and try to get the NDIS driver working? (I had tried it initially but couldn't get it to accept an SSID; this was before wpa_supplicant hit the tree so I was using an ifconfig in /etc/start_if.ndis_iwi0... it also failed to work, with no error message, from the command line. Of course, NDIS support has been reworked since then.) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH