Date: Sun, 27 Jan 2013 22:04:21 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Adrian Chadd <adrian@freebsd.org> Cc: paranormal <paranormal@isgroup.com.ua>, freebsd-wireless@freebsd.org Subject: Re: stuck beacon hung wifi adapter AR5008 Message-ID: <11510589486.20130127220421@serebryakov.spb.ru> In-Reply-To: <CAJ-VmomWA%2Bc2f=d2otFbiHQaWS-bpc6uboURrkh1C3mpst37RA@mail.gmail.com> References: <1359223263.8698.17.camel@eva02> <1102411019.20130127140605@serebryakov.spb.ru> <CAJ-Vmok61mpFGeSCOkj_Xj=5d17KDocw61zGv-4EnwW36=q4vg@mail.gmail.com> <1255037243.20130127214457@serebryakov.spb.ru> <CAJ-VmomWA%2Bc2f=d2otFbiHQaWS-bpc6uboURrkh1C3mpst37RA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Adrian. You wrote 27 =FF=ED=E2=E0=F0=FF 2013 =E3., 21:59:32: >> AC> For 2GHz in noisy environments, use it in HT20 mode. >> I'm using HT20, and it seems, card in my box overheats with 802.11n >> clients (it hangs very hard under load with 802.11n client), so I >> don't use 802.11n on notebook (I want to change box to new one, >> atom-based, but every month here are more high-priority expenditures >> than $200+ on MoBo, case, memory, etc). AC> Hm, overheating is a problem. It's quite likely that your issues are AC> due to this. It is why I don't poke you about this problem till I exclude overheating for sure. --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11510589486.20130127220421>