From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 15:52:27 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 6E93FA63 for ; Sat, 12 Jan 2013 15:52:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by mx1.freebsd.org (Postfix) with ESMTP id D93D7DDA for ; Sat, 12 Jan 2013 15:52:26 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id hm11so428509wib.2 for ; Sat, 12 Jan 2013 07:52:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jILWEkW07gOGZJJgxnQMhfypQ7vG0D4OWx46T86gFcs=; b=A2N0ND+8MxFjhEIEOl/WS7JJZoA16H9agT5stBQZU8WaXBlbJ9wXrCi5AlXMdq3NDJ ke3KbR74ZsMc4vC7ohttoRs1NGc09B+oJuPuV2aFhKB2JKV/MKptrdz+vI31e5jO8z/F /N1GI2SCau3rW7iOvgldallSfK7kVb1AWRKW9BTTeVlnRyiwXYYwTKiYIuBnOahJOL1s t8DMJ2IuqGyA2nvFw9qx59Uy3ducoHliTKX19gRc+NFQg9gVf61An/eqGplflgY/1U+o wp+VOcWPfYl7HpEJM4tZTOQ9IjbPmnmRtc79GqJ407KUoUHQtD/wXEP7kbxwS3SB7Zzf 2+qw== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr126945333wjc.1.1358005940081; Sat, 12 Jan 2013 07:52:20 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 07:52:19 -0800 (PST) In-Reply-To: <20130112154404.GH67643@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> Date: Sat, 12 Jan 2013 07:52:19 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 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 15:52:27 -0000 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. Thanks, 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.