From mboxrd@z Thu Jan 1 00:00:00 1970 From: John W. Linville Date: Tue, 2 Dec 2008 15:22:22 -0500 Subject: [ath9k-devel] ar9281 In-Reply-To: <43e72e890812010925x192f1f22laefc2f679ee4e4aa@mail.gmail.com> References: <1228151600.23262.55.camel@ungoliant.gsptech.fedex.com> <43e72e890812010925x192f1f22laefc2f679ee4e4aa@mail.gmail.com> Message-ID: <20081202202222.GA22707@tuxdriver.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Mon, Dec 01, 2008 at 09:25:33AM -0800, Luis R. Rodriguez wrote: > On Mon, Dec 1, 2008 at 9:13 AM, Pat O'Neil wrote: > > Greetings all, > > > > I've got a recent toshiba qosmio laptop, 64bit that has an ar9281 > > chipset that was "almost" working under F9, as after downloading the > > wireless git and compiling I could get it to come up and associate, but > > the performance was extremely slow, with ping times of 10's of seconds, > > etc. I also sometimes got the aforementioned "No ProbeResp from current > > AP ... - assume out of range" error. > > > > Since then I've loaded Fedora 10, and have hit a new snag with its > > bundled version of ath9k, as in the dmesg log I see the following: > > > > ...snip... > > > > ath9k: 0.1 > > ath_pci: software IOTLB in use, aborting. > > > > ...snip... > > Fedora 10 kernel is broken as a workaround to a kernel bug in ath9k > they decided to disable ath9k when the swiotbl is used due to a bug > that *we actually did fix*. They should fix their kernel. They may > have an updated kernel you may want to check. > > http://bugzilla.kernel.org/show_bug.cgi?id=11811 Not quite that simple. Those patches as written don't apply to 2.6.27, and F10 won't be on 2.6.28 for quite some time (since 2.6.28 has yet to be released). Now, if you know of 2.6.27 versions of those patches... :-) John -- John W. Linville Linux should be at the core linville at tuxdriver.com of your literate lifestyle.