From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 22:24:01 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00652106566B for ; Thu, 13 Mar 2008 22:24:00 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net [203.16.214.145]) by mx1.freebsd.org (Postfix) with ESMTP id 73F0B8FC1C for ; Thu, 13 Mar 2008 22:23:59 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AogFAL9A2Ud5LWvf/2dsb2JhbACBWqhp X-IronPort-AV: E=Sophos;i="4.25,496,1199626200"; d="scan'208";a="75049769" Received: from ppp121-45-107-223.lns10.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.107.223]) by ipmail05.adl2.internode.on.net with ESMTP; 14 Mar 2008 08:38:37 +1030 Received: from [192.168.155.54] (taurus.internal.clearchain.com [192.168.155.54]) (authenticated bits=0) by mail.clearchain.com (8.14.2/8.14.2) with ESMTP id m2DM8IFG062770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 08:38:18 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <47D9A5E3.1020900@clearchain.com> Date: Fri, 14 Mar 2008 08:38:35 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Sam Leffler References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl> <47D6FB5B.3020107@clearchain.com> <1205366956.2082.13.camel@localhost> <47D88DC0.1010903@freebsd.org> In-Reply-To: <47D88DC0.1010903@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (mail.clearchain.com [192.168.154.1]); Fri, 14 Mar 2008 08:38:21 +1030 (CST) Cc: freebsd-net@freebsd.org, Yousif Hassan , Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2008 22:24:01 -0000 Sam Leffler wrote: > Yousif Hassan wrote: >> On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: >> >>> Alphons "Fonz" van Werven wrote: >>> >>>> Mel wrote: >>>> >>>> >>>>>> Do the recent patches by Andrew make a difference? >>>>>> >>>>>> http://people.freebsd.org/~thompsa/wpi_head.diff >>>>>> http://people.freebsd.org/~thompsa/wpi_releng7.diff >>>>>> >> >> (ccing freebsd-net) >> >> Ben, >> >> I had a go with this patch today on top of 7.0-RELEASE. >> >> The good: >> - Switching off the radio and back on finally works - nice work. >> - Scanning seems faster (but see caveat below) >> - Association is MUCH faster (mind you, I don't use an encrypted AP). >> - The "failed to align memory" stuff when the driver loads up - >> fixed. - The fact that it reloaded in the kernel even if I manually >> kldunloaded >> if_wpi.ko - fixed >> >> The slightly wonky: >> - As reported by someone else: >> wpi0: timeout resetting Tx ring 1 >> wpi0: timeout resetting Tx ring 3 >> wpi0: timeout resetting Tx ring 4 >> appear on startup and occasionally on kldload - however they don't >> appear to adversely affect too much >> >> The ugly: >> - I can only do an ifconfig wpi0 scan every OTHER time - in between >> successful attempts, I get >> wpi0: fatal firmware error >> wpi0: timeout resetting Tx ring (or: timeout resetting Tx ring 0) >> wpi0: link state changed to DOWN >> >> This wouldn't be so bad since it works every other time, but the >> problem is that every time I do a scan, it sets the link state down, >> causing the connection to drop - doesn't seem normal. Of course then it >> comes right back up but the network interruption is not so great. >> >> Hmm - what else? The whole thing seems - livelier. I need to run some >> throughput benchmarks but traffic to/from the card on my local network >> seems faster and more responsive. Hopefully this isn't the placebo >> effect. ;) >> >> Great work to you & rest of team on this patch... it's more than usable >> at this point! >> > > wpi doesn't yet support background scan so doing an explicit scan from > the command line will disconnect you from any ap you care connected > to. It shouldn't be hard to add bgscan--but that's easy for me to say :) > It's certainly on my todo list! Cheers, Benjamin