Re: ar9281

On Tue, Dec 2, 2008 at 12:49 PM, John W. Linville
<linville <at> tuxdriver.com> wrote:
> On Tue, Dec 02, 2008 at 12:36:36PM -0800, Luis R. Rodriguez wrote:
>> On Tue, Dec 2, 2008 at 12:22 PM, John W. Linville
>> <linville <at> tuxdriver.com> wrote:
>> > 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 <Pat.ONeil <at> fedex.com> 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.