Date: Sat, 12 Jan 2013 07:52:19 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <CAJ-Vmomy4jVNs9r0H2XzVO-Q6tq7=O4EzJn-NLCOO=n%2BSJce_g@mail.gmail.com> 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> <CAJ-VmonkpnV=H0-pP-6Rv%2BvHoU4Sdi-7KzgLKz9%2BHjmXtuZGkA@mail.gmail.com> <20130111075136.GA67643@zxy.spb.ru> <CAJ-VmomBRDBk9oOaZo-6kvLWYvFxrH99XhyHH9FeyUta6pqzww@mail.gmail.com> <20130112105245.GF67643@zxy.spb.ru> <CAJ-Vmom18Pr2kq0qAymjintpg1Crgrna8%2By=7fBk8Vy7nqP5_A@mail.gmail.com> <20130112154404.GH67643@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <slw@zxy.spb.ru> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmomy4jVNs9r0H2XzVO-Q6tq7=O4EzJn-NLCOO=n%2BSJce_g>