From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:24:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CCBBEA28 for ; Sat, 12 Jan 2013 16:24:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 6AE37EF3 for ; Sat, 12 Jan 2013 16:24:15 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu3wx-00096S-IF; Sat, 12 Jan 2013 20:28:51 +0400 Date: Sat, 12 Jan 2013 20:28:51 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112162851.GI67643@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> <20130111075136.GA67643@zxy.spb.ru> <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 12 Jan 2013 16:24:15 -0000 On Sat, Jan 12, 2013 at 07:52:19AM -0800, Adrian Chadd wrote: > Ah, is it perhaps rfkill related? > > I've seen issues with rfkill before, where it is implemented as > "disable the power to the entire slot" rather than assert the RF kill > line to the device. > It's possible this is how it has to happen with the intel NICs? > > do you have an rfkill button on the keyboard to enable/disable wireless? > Try toggling that, then do pciconf -lv again? > > You can read the entire set of pci configuration registers: > > pciconf -rb pciX.X.X.X 0:255 > > If they show up as 0xffffffff then the NIC is disconnected/powered > off/hung. Try toggling the RF kill key on your keyboard, then re-read > those config registers. No rfkill button on the keyboard, but have hardware rf switch. This switch now work only for bluetooth (switching off don't relay to atheros card). Fresh boot, driver working Switch off: # pciconf -rb pci0:6:5:0 0:255 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Switch on: # pciconf -rb pci0:6:5:0 0:255 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 go to sleep, resume (switch still on): # pciconf -rb pci0:6:5:0 0:255 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > Adrian > > > > On 12 January 2013 07:44, Slawa Olhovchenkov wrote: > > On Sat, Jan 12, 2013 at 07:27:02AM -0800, Adrian Chadd wrote: > > > >> Hi, > >> > >> There's no firmware for the AR9220 .. it's all in the driver/HAL. > >> > >> If XP restore isn't working; maybe there's something in the ACPI/BIOS > >> that's screwing things up? > > > > I am use last available BIOS. > > After restore don't working only this card and this card don't have > > tab 'Power manager' in windows device manager. > > > > I found in the internet information about other issuse with this > > wn861n (and windows) (for example -- > > http://www.nothingbuttablets.com/forum/showthread.php?p=80851), but > > using last driver don't help for me.