From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 12 06:36:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80FBB4D0; Sun, 12 Jan 2014 06:36:37 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 576D41901; Sun, 12 Jan 2014 06:36:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=ZYOPYy+vim9178OltmgYiCICh6pCErOl7uNnpouWR5o=; b=SdSjb/HAlcouTk/R9sSKEyxIb9qAP9i6lioVEA6bA6CKzWakuzyvmBxFsw8qZvyhqJmsRhMK5Xb6U5HU8D8uGrcaRYsTzonM3vtdjKp5cxzSIGVlgGLrTTxWH6jvC3hF7zpCw8fRJCvVlp3ulZ4yWIAujQIP8J++uI2j39d8dmg=; Received: from [120.172.226.147] (port=27218 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1W2Eeq-002chD-TH; Sat, 11 Jan 2014 23:36:29 -0700 Date: Sun, 12 Jan 2014 14:36:14 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: IWN performance very bad with 10.0-RC5 Message-ID: <20140112143614.3313f509@X220.alogt.com> In-Reply-To: References: <20140111132338.7a7fc14c@X220.alogt.com> <20140111133610.313a4bca@X220.alogt.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Kevin Oberman , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Sun, 12 Jan 2014 06:36:37 -0000 Hi, On Fri, 10 Jan 2014 21:45:59 -0800 Adrian Chadd wrote: > Please help dig up which change broke it. Even just test out the head > iwn code from 6 months ago. I came to a very strange result. I have iwn in the kernel since June 2012 using 10. I also have had run in the kernel of another machine since February 2011. I could not even add runfw to the kernel those days running some 8 stable. I kept it that way until now. run was always working. iwn gave problems starting between August and November of last year on my access point but still worked on other places. I used iwn to connect successfully to another wireless network mid November 2013. After adding the firmware to the kernel for both iwn and run, I could compile the kernel and iwn started to work. runfw did not break compilation. I wonder now if the iwn or run could even work without firmware or if the firmware was automatically loaded even when iwn or run where compiled into the kernel. Erich