From owner-freebsd-stable@FreeBSD.ORG Mon Sep 28 04:52:59 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AF9F106566C for ; Mon, 28 Sep 2009 04:52:59 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2945E8FC0A for ; Mon, 28 Sep 2009 04:52:58 +0000 (UTC) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id n8S4qwCv023040 for ; Sun, 27 Sep 2009 23:52:58 -0500 (CDT) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id n8S4qw5V023039 for freebsd-stable@freebsd.org; Sun, 27 Sep 2009 23:52:58 -0500 (CDT) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Sun, 27 Sep 2009 23:52:58 -0500 From: Scott Lambert To: freebsd-stable@freebsd.org Message-ID: <20090928045258.GH4858@sysmon.tcworks.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20090927111924.GG4858@sysmon.tcworks.net> <4ABFC20A.3070100@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ABFC20A.3070100@freebsd.org> User-Agent: Mutt/1.4.2.2i Subject: Re: 8-RC1: iwn0 suspend/resume issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2009 04:52:59 -0000 On Sun, Sep 27, 2009 at 12:50:34PM -0700, Sam Leffler wrote: > Scott Lambert wrote: > > I did just notice: > > > > iwn0: Reg Domain: \M^?\M^?\M^?\M^?iwn0: iwn_mem_lock: could not lock memory > > > > Maybe I should set the regulatory domain? But having just spent a few > > minutes trying, it doesn't seem to be interested... > > > > lambert@slambert:~> sudo ifconfig wlan0 regdomain FCC > > ifconfig: SIOCS80211: Device busy > > wlan0 is marked UP; you cannot set regulatory state unless the interface > is down. > > > Exit 1 > > lambert@slambert:~> sudo ifconfig iwn0 regdomain FCC > > ifconfig: unable to get regulatory domain info: Invalid argument > > iwn0 is the wrong interface to use; use wlan0 Ah, a little education is a dangerous thing. Setting regdomain does not give errors when I use wlan0 and it is configured down. > Regarding regdomain stuff; AFAIK you cannot alter regulatory state of > any intel wireless card; it will enforce whatever is in the EEPROM. > Can't recall if the driver pushes EEPROM state up to net80211; if > not then it should and it should also reject all requests to change > regulatory until there's fw that supports it. It did let me set country to jp and regdomain to JAPAN while playing. That may not mean much. The iwn driver is confused right now because it has been through a suspend and resume cycle. Thank you, Sam! -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org