From owner-freebsd-questions@FreeBSD.ORG Mon Feb 23 01:37:49 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60B80106564A for ; Mon, 23 Feb 2009 01:37:49 +0000 (UTC) (envelope-from jcurley@MIT.EDU) Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1CAA38FC0A for ; Mon, 23 Feb 2009 01:37:48 +0000 (UTC) (envelope-from jcurley@MIT.EDU) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id n1N1bkZ2029533; Sun, 22 Feb 2009 20:37:46 -0500 (EST) Received: from [192.168.0.3] (c-71-232-50-230.hsd1.ma.comcast.net [71.232.50.230]) (authenticated bits=0) (User authenticated as jcurley@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id n1N1biLC019351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 22 Feb 2009 20:37:45 -0500 (EST) From: Curley To: Jan Henrik Sylvester Date: Sun, 22 Feb 2009 20:37:41 -0500 User-Agent: KMail/1.9.10 References: <499EE943.8050006@janh.de> In-Reply-To: <499EE943.8050006@janh.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902222037.42225.jcurley@mit.edu> X-Scanned-By: MIMEDefang 2.42 X-Spam-Flag: NO X-Spam-Score: 0.00 Cc: questions-list freebsd , Erik Johnson Subject: Re: FreeBSD 7.1: iwi problem with intel 2200 pro wireless card X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 01:37:49 -0000 Moving the license agreement phrase did not change the driver/firmware behavior. I changed the firmware timeout setting (http://lists.freebsd.org/pipermail/freebsd-mobile/2006-July/008849.html), and this seemed to help somewhat. Now I sometimes pick up a wireless network after rebooting, but the connection is not stable; moreover, I cannot change networks. I've come to the same conclusion, that fixing a broken iwi driver is more trouble than purchasing a cheap wireless card. This machine has undergone a few warranty repairs (including a motherboard replacement). I wonder if that complicates the driver issue. I'm just getting started with FreeBSD; therefore, your replies were especially helpful: Thanks for responding! Best Wishes, John On Friday 20 February 2009 12:32:51 pm Jan Henrik Sylvester wrote: > Erik Johnson wrote: > > I noticed on your loader.conf that you have the license at the end of > > "WiFi Config. I placed mine at the beginning. as in the example below. > > Have you tried loading that first? I'm not sure if it makes a difference > > but might be worth a try. I'm interested in hearing back and keeping in > > contact since we share similar config for older hardware. > > > > > > ------------------------------------------------------- > > legal.intel_iwi.license_ack=1 > > if_iwi_load="YES" > > wlan_load="YES" > > firmware_load="YES" > > iwi_bss_load="YES" > > iwi_ibss_load="YES" > > iwi_monitor_load="YES" > > The ordering in loader.conf does not matter. > > I abandoned iwi some time ago: > http://lists.freebsd.org/pipermail/freebsd-current/2009-February/003125.htm >l > > You might want to read the whole thread. Disabling bgscan is mentioned > there somewhere. IIRC, that is a good idea. > > Do you really need ibss and monitor? Have you tried not loading three > different firmwares at the same time? > > Last time I used iwi, I did not have to load the firmware manually. Up > to 6.1 that was a requirement, but from 6.2 on, iwi could do it > automatically. (And it worked better that way, IIRC.) > > Since the manual page tells you to do so, the loading of the firmware > must have changed. When manual loading was required on 6.1, loading > multiple at the same time was not a good idea. > > I never got monitor to receive any packages on 7.0, even after manually > loading the firmware. It did work on 6.2, though. ibss was never really > reliable. > > Cheers, > Jan Henrik