From owner-freebsd-mobile@FreeBSD.ORG Thu Oct 4 16:07:54 2007 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A20F616A418 for ; Thu, 4 Oct 2007 16:07:54 +0000 (UTC) (envelope-from pankov_p@mail.ru) Received: from mx34.mail.ru (mx38.mail.ru [194.67.23.34]) by mx1.freebsd.org (Postfix) with ESMTP id 61C1013C478 for ; Thu, 4 Oct 2007 16:07:54 +0000 (UTC) (envelope-from pankov_p@mail.ru) Received: from [88.84.200.94] (port=12209 helo=[172.16.1.21]) by mx34.mail.ru with asmtp id 1IdTDr-000P4A-00; Thu, 04 Oct 2007 20:06:47 +0400 From: Pankov Pavel Organization: MPEI To: freebsd-mobile@freebsd.org Date: Thu, 4 Oct 2007 20:07:48 +0400 User-Agent: KMail/1.9.7 References: <4703B7EF.6030603@gmx.net> <1191486698.1475.40.camel@localhost> <200710041651.12012.fbsd.mobile@rachie.is-a-geek.net> In-Reply-To: <200710041651.12012.fbsd.mobile@rachie.is-a-geek.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710042007.49097.pankov_p@mail.ru> Cc: Mel Subject: Re: Intel 3945ABG with ipw driver on CURRENT X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2007 16:07:54 -0000 On Thursday 04 October 2007 18:51:10 Mel wrote: > On Thursday 04 October 2007 10:31:38 Tom Evans wrote: > > On Wed, 2007-10-03 at 17:55 +0100, Rui Paulo wrote: > > > On 10/3/07, Frank Staals wrote: > > > > Hey, > > > > > > > > Last week I finally received my Dell Latitude D630 which is using the > > > > Intel 3945ABG chipset for it's wireless connectivity. This should be > > > > supported with the ipw driver which is available in CURRENT. > > > > Unfortunately my card is not detected when loading the module. > > > > > > If your card is a 3945ABG, then you need the wpi driver, which is not > > > included (yet, I hope) in FreeBSD. > > > > > > Try here: > > > http://www.clearchain.com/wiki/Wpi > > > > > > Regards. > > > > This prompted me to give the wpi driver another go. Both the snapshot > > 20070923-freebsd-wpi and the version available in perforce fail to load, > > due to > > link_elf: symbol _mtx_assert undefined > > > > FreeBSD version is (csup'ed ~1hr before build time) > > FreeBSD zoot.mintel.co.uk 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Oct 3 > > 11:47:24 BST 2007 root@zoot.mintel.co.uk:/usr/obj/usr/src/sys/ZOOT > > i386 > > Does ZOOT have WITNESS? > > It loads for me, but locks up machine randomly, sometimes on scan, > sometimes on up, sometimes on assigning an IP. It points to the lock set at > the end of _init(). Ben knows. Try this patch, please. It makes wpi absolutely stable for me (it looses link sometimes, but it doesn't panic anymore at least: --- 20070923-freebsd-wpi/sys/dev/wpi/if_wpi.c~ 2007-09-23 18:21:03.000000000 +0400 +++ 20070923-freebsd-wpi/sys/dev/wpi/if_wpi.c 2007-09-29 21:31:58.000000000 +0400 @@ -725,8 +725,9 @@ ic->ic_newstate = wpi_newstate; ieee80211_media_init(ic, wpi_media_change, ieee80211_media_status); - sc->amrr.amrr_min_success_threshold = 1; - sc->amrr.amrr_max_success_threshold = 15; + ieee80211_amrr_init(&sc->amrr, ic, + IEEE80211_AMRR_MIN_SUCCESS_THRESHOLD, + IEEE80211_AMRR_MAX_SUCCESS_THRESHOLD); /* whilst ieee80211_ifattach will listen for ieee80211 frames, * we also want to listen for the lower level radio frames