From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: ath9k seems to be broken on 2.6.30-rc4 with a macbook pro
Date: Mon, 11 May 2009 15:18:54 -0700 [thread overview]
Message-ID: <1242080334.1991.11.camel@unix> (raw)
In-Reply-To: <4A089E49.7080403@gmail.com>
On Mon, 2009-05-11 at 23:53 +0200, Jiri Slaby wrote:
> Adding some CCs.
>
> On 05/11/2009 07:02 PM, Justin Mattock wrote:
> > I've been trying to diagnose an issue
> > with 2.6.30-rc4. At first thinking it
> > was not the kernel, but the network manager
> > (in my case I use wicd).
> > with 2.6.29-rc8 the system starts up,
> > connects no problem.
> > but as soon as I load 2.6.30-rc4
> > I get limited connection to none.
> > in dmesg I see:
> >
> > [ 36.337419] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 1
> > [ 36.530106] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 2
> > [ 36.730100] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 3
> > [ 36.930101] wlan0: direct probe to AP 00:1e:2a:00:67:f0 timed out
> > [ 44.421728] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 1
> > [ 44.620080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 2
> > [ 44.820080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 3
> > [ 45.020076] wlan0: direct probe to AP 00:1e:2a:00:67:f0 timed out
> >
> > The type of encryption used is just
> > a standard WEP key(no WPA).
> >
> > has this been resolved already?
> >
> > Also I'm noticing(but not that big of a deal)
> > if I set in sysctl.conf:
> >
> > net.ipv4.conf.all.arp_ignore=8
> > net.ipv4.conf.wlan0.arp_ignore=8
> > net.ipv4.conf.wmaster0.arp_ignore=8
> > net.ipv4.conf.lo.arp_ignore=8
> > net.ipv4.conf.all.arp_announce=2
> > net.ipv4.conf.wlan0.arp_announce=2
> > net.ipv4.conf.wmaster0.arp_announce=2
> > net.ipv4.conf.lo.arp_announce=2
> >
> > watching a movie on hulu, about 15/20 minuets
> > into enjoyment, hulu craps out(starts re-buffering)
> > then re initializes after about 30 secs later.
> > but if I comment those out(set back to default)
> > hulu will run fine.
> >
>
Cool.
Another odd thing Ive experienced as well
with 2.6.29-rc8 is if my iphone is
connected to the router I'll have a hard time connecting
to anything until I disconnect the iphone
from the router.(my guess is the router is getting
old).
regards,
Justin P. Mattock
next prev parent reply other threads:[~2009-05-11 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd18b0c30905111002y4aeb2033ma2fbb2730f5acdaf@mail.gmail.com>
2009-05-11 21:53 ` ath9k seems to be broken on 2.6.30-rc4 with a macbook pro Jiri Slaby
2009-05-11 22:18 ` Justin P. Mattock [this message]
2009-05-12 15:03 ` Bob Copeland
2009-05-12 16:43 ` Justin Mattock
2009-05-11 22:24 ` Luis R. Rodriguez
2009-05-11 23:23 ` Justin Mattock
2009-05-12 10:39 ` Evgeni Golov
[not found] ` <dd18b0c30905120728v156d4e1g808a853d23ba0ae6@mail.gmail.com>
2009-05-12 17:46 ` Evgeni Golov
2009-05-12 20:04 ` Justin Mattock
2009-05-12 23:01 ` Luis R. Rodriguez
[not found] ` <1242169748.14227.15.camel@johannes.local>
2009-05-12 23:36 ` Justin P. Mattock
2009-05-13 20:19 ` Justin Mattock
2009-05-12 10:39 ` Evgeni Golov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242080334.1991.11.camel@unix \
--to=justinmattock@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).