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.
>
On Tue, May 12, 2009 at 8:03 AM, Bob Copeland <[email protected]> wro=
te:
> On Mon, May 11, 2009 at 6:18 PM, Justin P. Mattock
> <[email protected]> wrote:
>> 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).
>
> So the iphone causes problems when connecting from another machine
> with ath9k, but it works ok in other kernels, or when iphone is not
> connected? =A0It could be related to power saving.
>
> --
> Bob Copeland %% http://www.bobcopeland.com
>
The setup I have is one router(netgear cheap but
works)
with macbook pro, imac, and an iphone. I guess I'm an
apple groupie, minus the OS!!
(two dells also, that I'm going to bring back from the
dead when I get a chance).
With 2.6.29-rc8 I've noticed this twice
the first time about a month ago.
basically I turned on the macbook
had the radio streaming, as well as T.V.
then a few seconds later all connections
died on the macbook, then after freaking
out I decided to reset the router, but still
system runs(macbook) and then everything
dies. Then freaking out for the second time,
I decided to shut everything off of the router
except the macbook, and voila no problem streaming.
Then after about ten minuets of non interruption
I turned the iphone wireless back on, and bam
the macbook had a dead connection again.
(leaving me dazed and confused, and that's without
any liquid propulsion).
The second time with the same kernel
was about a few days ago, but this time
after resetting the router, shutting everything
off except the macbook, and then turning the
iphone back on seemed to run fine.(leading me
to believe something might be wrong with the
router).
As for 2.6.30-rc4 not sure, still need to
get the wireless running smoothly, and then
I'll go from there.
--=20
Justin P. Mattock
On Mon, May 11, 2009 at 6:18 PM, Justin P. Mattock
<[email protected]> wrote:
> 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).
So the iphone causes problems when connecting from another machine
with ath9k, but it works ok in other kernels, or when iphone is not
connected? It could be related to power saving.
--
Bob Copeland %% http://www.bobcopeland.com
On Mon, 11 May 2009 23:53:13 +0200 Jiri Slaby wrote:
> > 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).
Same here with 2.6.30-rc4, b43 and either Cisco (MAC-Addr starts with
00:40:96) or HP ProCurve (??? - they do WiFi? - MAC-Addr starts with
00:1F:FE) APs. No encryption, quite noisy environment (University).
No problem with ipw2200 (actually 2915) in the same hardware (Thinkpad
X31). Neither with the b43 and a standard Linksys WRT54GL (in the same!
noisy university-env).
Regards
Evgeni
On Mon, May 11, 2009 at 3:24 PM, Luis R. Rodriguez <[email protected]> wrote:
> On Mon, May 11, 2009 at 2:53 PM, Jiri Slaby <[email protected]> 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?
>
> Can you provide more details, like the AP you used, and card you have?
> (dmesg log would be nice).
>
> ?Luis
>
The AP I use is a
netgear 54g(cheap 40 dollar router from
bestbuy)
attached is dmesg and lspci
disregard the kernel commits
2.6.30-rc4-00004-gfb422e6
(those are from the bluetooth patches a few
days ago) without them the kernel is at
2.6.30-rc4.
--
Justin P. Mattock
On Mon, 11 May 2009 23:53:13 +0200 Jiri Slaby wrote:
> > 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).
Same here with 2.6.30-rc4, b43 and either Cisco (MAC-Addr starts with
00:40:96) or HP ProCurve (??? - they do WiFi? - MAC-Addr starts with
00:1F:FE) APs. No encryption, quite noisy environment (University).
No problem with ipw2200 (actually 2915) in the same hardware (Thinkpad
X31). Neither with the b43 and a standard Linksys WRT54GL (in the same!
noisy university-env).
Regards
Evgeni
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
On Mon, May 11, 2009 at 2:53 PM, Jiri Slaby <[email protected]> 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:
>>
>> [ =C2=A0 36.337419] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
1
>> [ =C2=A0 36.530106] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
2
>> [ =C2=A0 36.730100] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
3
>> [ =C2=A0 36.930101] wlan0: direct probe to AP 00:1e:2a:00:67:f0 time=
d out
>> [ =C2=A0 44.421728] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
1
>> [ =C2=A0 44.620080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
2
>> [ =C2=A0 44.820080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try =
3
>> [ =C2=A0 45.020076] wlan0: direct probe to AP 00:1e:2a:00:67:f0 time=
d out
>>
>> The type of encryption used is just
>> a standard WEP key(no WPA).
>>
>> has this been resolved already?
Can you provide more details, like the AP you used, and card you have?
(dmesg log would be nice).
Luis