From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 17 14:33:47 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F194A106564A for ; Fri, 17 Aug 2012 14:33:46 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id AB7DC8FC12 for ; Fri, 17 Aug 2012 14:33:46 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q7HEXjoD059791; Fri, 17 Aug 2012 08:33:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q7HEXjcv059788; Fri, 17 Aug 2012 08:33:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 17 Aug 2012 08:33:45 -0600 (MDT) From: Warren Block To: Bernhard Schmidt In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Fri, 17 Aug 2012 08:33:45 -0600 (MDT) Cc: freebsd-wireless@freebsd.org, Yuval Prag Subject: Re: Intel Pro/Wireless 2200BG crash on FreeBSD-8.3 i386 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2012 14:33:47 -0000 On Fri, 17 Aug 2012, Bernhard Schmidt wrote: > On Fri, Aug 17, 2012 at 7:00 AM, Yuval Prag wrote: >> Hi Im looking for help and some more info on the subject. >> >> the only post i found is from april 2008 the post suggests to add the >> capability to the driver based on or copy from a different WiFi >> NIC driver and it is not working still same error > > Another then that, you are not giving much information. From the > description it sounds like you are using WPA, did you try to run > wpa_supplicant in debug mode? Smells like you are getting connected > but the encryption is going wrong somehow. The old 2100 card in a Thinkpad T42 needed a firmware update to be able to handle WPA. That firmware was hidden in a Windows driver update. Maybe this is a similar problem.