Date: Fri, 11 Apr 2014 14:49:30 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Gleb Smirnoff <glebius@freebsd.org> Cc: Alexandr <shuriku@shurik.kiev.ua>, Tom Murphy <freebsd@pertho.net>, freebsd-current <freebsd-current@freebsd.org>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <CAJ-Vmok=a7nbb=y1AWAyqKJZLS215OcOjtYb9FEXHf_iwA890Q@mail.gmail.com> In-Reply-To: <20140411134904.GF902@glebius.int.ru> References: <20140228230705.GA28290@syn.pertho.net> <CAJ-Vmokcs-rdHTMGGSi80JcrMSszLyzuC=KDFgZ33zMZbXZPJw@mail.gmail.com> <CAJ-Vmo=4c5q6r36RnNorMhVmJKA9yqydZiMoJ=Rcky8zphscAQ@mail.gmail.com> <20140403100207.GA23640@syn.pertho.net> <CAJ-Vmonnu%2BWnuh1U0sQ0mUgL-6NSSmM541mFAJnmpZ_84-Z-9w@mail.gmail.com> <20140408104650.GN44326@FreeBSD.org> <CAJ-Vmo=fHNGG69X4Q2FKh6cWaQvL4WYUbjJ6ALKOfynPq8LdDQ@mail.gmail.com> <20140411101816.GC902@glebius.int.ru> <CAJ-Vmoko1-w6hVD2oUduttrUh7gLy7y78yX3QDj8oTj-U9KX1A@mail.gmail.com> <20140411104958.GD902@glebius.int.ru> <20140411134904.GF902@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 April 2014 06:49, Gleb Smirnoff <glebius@freebsd.org> wrote: > On Fri, Apr 11, 2014 at 02:49:58PM +0400, Gleb Smirnoff wrote: > T> On Fri, Apr 11, 2014 at 03:19:52AM -0700, Adrian Chadd wrote: > T> A> Ok, i have some of these. > T> A> > T> A> Which version of iwn(4) and net80211(4) work for you? We should do > T> A> some bisecting of iwn/net80211 together to figure it out. > T> > T> I will bisect entire kernel. A lot of manual fixing needs to be > T> applied to older iwn/net80211 to get it compilable with modern > T> kernel. > > Very strange. I bisected from 254098 up to today, moving closer and > closer to current revision and finally came to it. No problems :( > > But I clearly remember that before I started this process, my > download speed was 30 - 60 KBytes/s. > > May be this was some firmware issue that persisted during reboots? > Old driver gave it a kick and new driver now works good? Yes, > sounds mad. It's quite possible. I've seen this before with the intel stuff. Let me know if it happens again? -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok=a7nbb=y1AWAyqKJZLS215OcOjtYb9FEXHf_iwA890Q>