FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 07-27-2010, 11:33 PM
Phil Savoie
 
Default Wifi not working

Hello,

I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can
see it. it comes up in NetworkManager but never gets an IP. the router
is a linksys using WPA/PSK security. Would/could someone please help me
out trying to get this to work? Output of several commands follows:

dmesg:

ath: EEPROM regdomain: 0x69
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x69
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
phy0: Atheros AR9285 MAC/BB Rev:2 AR5133 RF Rev:e0: mem=0xf8bc0000, irq=185

cat /etc/modprobe.conf:

alias wlan0 ath9k


tail /var/log/messages:

Jul 27 19:31:02 smurf3 NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) complete.
Jul 27 19:31:02 smurf3 NetworkManager: <info> (wlan0): device state
change: 9 -> 3
Jul 27 19:31:02 smurf3 NetworkManager: <info> (wlan0): deactivating
device (reason: 0).
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0)
starting connection 'Auto pszone'
Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state
change: 3 -> 4
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) scheduled...
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) started...
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) scheduled...
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) complete.
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) starting...
Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state
change: 4 -> 5
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation
(wlan0/wireless): access point 'Auto pszone' has security, but secrets
are required.
Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state
change: 5 -> 6
Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) complete.
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) scheduled...
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) started...
Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): device state
change: 6 -> 4
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) scheduled...
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) complete.
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) starting...
Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): device state
change: 4 -> 5
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto pszone' has security, and secrets
exist. No new secrets needed.
Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'ssid'
value 'pszone'
Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'scan_ssid'
value '1'
Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'key_mgmt'
value 'WPA-PSK'
Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'psk' value
'<omitted>'
Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) complete.
Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: set interface
ap_scan to 1
Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: disconnected -> scanning
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: scanning -> associating
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: associating -> associated
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: associated -> 4-way handshake
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: 4-way handshake -> group handshake
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant
connection state: group handshake -> completed
Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation
(wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected
to wireless network 'pszone'.
Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) scheduled.
Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) started...
Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): device state
change: 5 -> 7
Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0)
Beginning DHCP transaction.
Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client
V3.0.5-RedHat
Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems
Consortium.
Jul 27 19:31:38 smurf3 dhclient: All rights reserved.
Jul 27 19:31:38 smurf3 dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Jul 27 19:31:38 smurf3 dhclient:
Jul 27 19:31:38 smurf3 NetworkManager: <info> dhclient started with pid
30770
Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) complete.
Jul 27 19:31:38 smurf3 NetworkManager: <info> DHCP: device wlan0 state
changed normal exit -> preinit
Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df
Jul 27 19:31:38 smurf3 dhclient: Sending on LPF/wlan0/c4:17:fe:bb:6a:df
Jul 27 19:31:38 smurf3 dhclient: Sending on Socket/fallback
Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 4
Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 11
Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 14
Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 20
Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP
transaction took too long (>45s), stopping it.
Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP
transaction, dhcp client pid 30770
Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) scheduled...
Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) started...
Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): device state
change: 7 -> 9
Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) failed
for access point (pszone)
Jul 27 19:32:23 smurf3 NetworkManager: <info> Marking connection 'Auto
pszone' invalid.
Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) failed.
Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) complete.
Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): device state
change: 9 -> 3
Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): deactivating
device (reason: 0)

Thank you,

Phil
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Wed Jul 28 02:30:01 2010
Return-path: <devel-bounces@lists.fedoraproject.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Wed, 28 Jul 2010 01:49:33 +0300
Received: from bastion02.fedoraproject.org ([209.132.181.3]:44517 helo=bastion.fedoraproject.org)
by s2.java-tips.org with esmtp (Exim 4.69)
(envelope-from <devel-bounces@lists.fedoraproject.org>)
id 1Odsxp-0004bb-J3
for tom@linux-archive.org; Wed, 28 Jul 2010 01:49:33 +0300
Received: from lists.fedoraproject.org (collab1.vpn.fedoraproject.org [192.168.1.21])
by bastion02.phx2.fedoraproject.org (Postfix) with ESMTP id 8B33A10FD48;
Tue, 27 Jul 2010 23:33:15 +0000 (UTC)
Received: from collab1.fedoraproject.org (localhost.localdomain [127.0.0.1])
by lists.fedoraproject.org (Postfix) with ESMTP id EBDAA3267A1;
Tue, 27 Jul 2010 23:33:14 +0000 (UTC)
X-Original-To: devel@lists.fedoraproject.org
Delivered-To: devel@lists.fedoraproject.org
Received: from smtp-mm3.fedoraproject.org (smtp-mm3.fedoraproject.org
[152.46.7.226])
by lists.fedoraproject.org (Postfix) with ESMTP id 1AF5E326791
for <devel@lists.fedoraproject.org>;
Tue, 27 Jul 2010 23:33:13 +0000 (UTC)
Received: from mail-ww0-f51.google.com (mail-ww0-f51.google.com [74.125.82.51])
by smtp-mm3.fedoraproject.org (Postfix) with ESMTP id 9429E37D4B
for <devel@lists.fedoraproject.org>;
Tue, 27 Jul 2010 23:33:12 +0000 (UTC)
Received: by mail-ww0-f51.google.com with SMTP id 15so373124wwe.20
for <devel@lists.fedoraproject.org>;
Tue, 27 Jul 2010 16:33:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.52.140 with SMTP id e12mr9772167wec.87.1280273588847; Tue,
27 Jul 2010 16:33:08 -0700 (PDT)
Received: by 10.216.180.7 with HTTP; Tue, 27 Jul 2010 16:33:08 -0700 (PDT)
In-Reply-To: <AANLkTiktuZD2artMwFBXTAC0oqUb25p5iENBVQKRT4Du@mai l.gmail.com>
References: <4C4F554C.7030103@gmail.com>
<AANLkTimwJxweP=uMoVAcXWM2wnON3NfR6gyXe1DCGja0@mai l.gmail.com>
<4C4F58C5.3000702@gmail.com>
<cone.1280270190.733987.10081.500@commodore.emai l-scan.com>
<4C4F6292.6020001@gmail.com>
<AANLkTiktuZD2artMwFBXTAC0oqUb25p5iENBVQKRT4Du@mai l.gmail.com>
Date: Tue, 27 Jul 2010 18:33:08 -0500
Message-ID: <AANLkTikH83YvSncz32gJ7aDeAzNKwQ7GfHbF1ppT2J6i@mai l.gmail.com>
Subject: Re: Firefox 4 for Fedora 14?
From: =?ISO-2022-JP?B?Q29uYW4gS3VkbyAoGyRCJUshPCVrISYlNCVzJVEbKEIp? =
<ngompa13@gmail.com>
To: Development discussions related to Fedora <devel@lists.fedoraproject.org>
X-BeenThere: devel@lists.fedoraproject.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Development discussions related to Fedora
<devel@lists.fedoraproject.org>
List-Id: Development discussions related to Fedora
<devel.lists.fedoraproject.org>
List-Unsubscribe: <https://admin.fedoraproject.org/mailman/listinfo/devel>,
<mailto:devel-request@lists.fedoraproject.org?subject=unsubscrib e>
List-Archive: <http://lists.fedoraproject.org/pipermail/devel>
List-Post: <mailto:devel@lists.fedoraproject.org>
List-Help: <mailto:devel-request@lists.fedoraproject.org?subject=help>
List-Subscribe: <https://admin.fedoraproject.org/mailman/listinfo/devel>,
<mailto:devel-request@lists.fedoraproject.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8443600981867468111=="
Sender: devel-bounces@lists.fedoraproject.org
Errors-To: devel-bounces@lists.fedoraproject.org

--===============8443600981867468111==
Content-Type: multipart/alternative; boundary=0016e6dee7ca7a85fe048c66ec97

--0016e6dee7ca7a85fe048c66ec97
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jul 27, 2010 at 6:31 PM, Brandon Lozza <brandon@pwnage.ca> wrote:

> On 7/27/10, Rahul Sundaram <metherid@gmail.com> wrote:
> > On 07/28/2010 04:06 AM, Sam Varshavchik wrote:
> > > According to this two year-old post, it's possible to build Firefox
> > > with gstreamer support:
> > >
> > >
> http://www.bluishcoder.co.nz/2008/04/firefox-html5-video-with-gstreamer.html
> > >
> > >
> > > Dunno if any of that is true today.
> > >
> > > There's precedent for Firefox using system components instead of
> > > bundled ones. Firefox already uses hunspell instead of its own bundled
> > > dictionary, for spell checking. It makes sense for Firefox to use
> > > gstreamer, instead of any bundled codecs.
> >
> >
> > The blog post talks about a non upstreamed patch and Firefox doesn't use
> > Gstreamer at all now. It isn't just a matter of a bundled vs system
> > components at this point. Non upstreamed patches are not a option for
> > Firefox for trademark reasons as well.
> >
> >
> > Rahul
> >
> > --
> > devel mailing list
> > devel@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> >
>
> what about iceweasel or icefox instead
>
> the trademark problem makes it non free
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>

Then that would make most Linux distributions non-free, including Fedora.
So, meh. Fedora also has a policy of trying not to add patches to their own
packages, so it jives just fine with Mozilla's trademark policy.

Plus, those names suck, keep the Mozilla Firefox name.

--0016e6dee7ca7a85fe048c66ec97
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Jul 27, 2010 at 6:31 PM, Brandon Lozza <=
span dir=3D"ltr">&lt;<a href=3D"mailto:brandon@pwnage.ca">brandon@pwnage.c a=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class=3D"h5">On 7/27/10, Rahul Sundaram &lt;<a href=3D=
"mailto:metherid@gmail.com">metherid@gmail.com </a>&gt; wrote:<br>
&gt; On 07/28/2010 04:06 AM, Sam Varshavchik wrote:<br>
&gt; =A0&gt; According to this two year-old post, it's possible to buil=
d Firefox<br>
&gt; =A0&gt; with gstreamer support:<br>
&gt; =A0&gt;<br>
&gt; =A0&gt; <a href=3D"http://www.bluishcoder.co.nz/2008/04/firefox-html5-=
video-with-gstreamer.html" target=3D"_blank">http://www.bluishcoder.co.nz/2=
008/04/firefox-html5-video-with-gstreamer.html</a><br>
&gt; =A0&gt;<br>
&gt; =A0&gt;<br>
&gt; =A0&gt; Dunno if any of that is true today.<br>
&gt; =A0&gt;<br>
&gt; =A0&gt; There's precedent for Firefox using system components inst=
ead of<br>
&gt; =A0&gt; bundled ones. Firefox already uses hunspell instead of its own=
bundled<br>
&gt; =A0&gt; dictionary, for spell checking. It makes sense for Firefox to =
use<br>
&gt; =A0&gt; gstreamer, instead of any bundled codecs.<br>
&gt;<br>
&gt;<br>
&gt; The blog post talks about a non upstreamed patch and Firefox doesn&#39=
;t use<br>
&gt; =A0Gstreamer at all now. =A0 It isn't just a matter of a bundled v=
s system<br>
&gt; =A0components at this point. =A0 =A0Non upstreamed patches are not a o=
ption for<br>
&gt; =A0Firefox for trademark reasons as well.<br>
&gt;<br>
&gt;<br>
&gt; =A0Rahul<br>
&gt;<br>
&gt; =A0--<br>
&gt; =A0devel mailing list<br>
&gt; =A0<a href=3D"mailto:devel@lists.fedoraproject.org">deve l@lists.fedora=
project.org</a><br>
&gt; =A0<a href=3D"https://admin.fedoraproject.org/mailman/listinfo/devel" =
target=3D"_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a=
><br>
&gt;<br>
<br>
</div></div>what about iceweasel or icefox instead<br>
<br>
the trademark problem makes it non free<br>
<div><div></div><div class=3D"h5">--<br>
devel mailing list<br>
<a href=3D"mailto:devel@lists.fedoraproject.org">deve l@lists.fedoraproject.=
org</a><br>
<a href=3D"https://admin.fedoraproject.org/mailman/listinfo/devel" target=
=3D"_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br><div>Then that would make most Linux dis=
tributions non-free, including Fedora. So, meh. Fedora also has a policy of=
trying not to add patches to their own packages, so it jives just fine wit=
h Mozilla's trademark policy.</div>
<div><br></div><div>Plus, those names suck, keep the Mozilla Firefox name.<=
/div>

--0016e6dee7ca7a85fe048c66ec97--

--===============8443600981867468111==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
--===============8443600981867468111==--
 
Old 07-28-2010, 01:19 AM
Larry Vaden
 
Default Wifi not working

On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie <psavoie1783@rogers.com> wrote:
> Beginning DHCP transaction.
> Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client
> V3.0.5-RedHat
> Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems
> Consortium.
> Jul 27 19:31:38 smurf3 dhclient: All rights reserved.
> Jul 27 19:31:38 smurf3 dhclient: For info, please visit
> http://www.isc.org/sw/dhcp/
> Jul 27 19:31:38 smurf3 dhclient:
> Jul 27 19:31:38 smurf3 NetworkManager: <info> *dhclient started with pid
> 30770
> Jul 27 19:31:38 smurf3 NetworkManager: <info> *Activation (wlan0) Stage
> 3 of 5 (IP Configure Start) complete.
> Jul 27 19:31:38 smurf3 NetworkManager: <info> *DHCP: device wlan0 state
> changed normal exit -> preinit
> Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df
> Jul 27 19:31:38 smurf3 dhclient: Sending on * LPF/wlan0/c4:17:fe:bb:6a:df
> Jul 27 19:31:38 smurf3 dhclient: Sending on * Socket/fallback
> Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to
> 255.255.255.255 port 67 interval 4
> Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to
> 255.255.255.255 port 67 interval 11
> Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to
> 255.255.255.255 port 67 interval 14
> Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to
> 255.255.255.255 port 67 interval 20
> Jul 27 19:32:23 smurf3 NetworkManager: <info> *Device 'wlan0' DHCP
> transaction took too long (>45s), stopping it.
> Jul 27 19:32:23 smurf3 NetworkManager: <info> *wlan0: canceled DHCP
> transaction, dhcp client pid 30770

It would seem that one possibility is that the AP is not running a
DHCP server.

Another is that if the AP is running a DHCP server, it is restricting
IP addresses to known clients.

kind regards/ldv
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-28-2010, 01:38 AM
Phil Savoie
 
Default Wifi not working

Larry Vaden wrote:

> It would seem that one possibility is that the AP is not running a
> DHCP server.
>
> Another is that if the AP is running a DHCP server, it is restricting
> IP addresses to known clients.
>
> kind regards/ldv

Hi Larry,

Thanks for your reply. This wifi card is a known host with win 7 (the
other half of the dual boot) running fine.

BTW, I forgot to mention that I am running Centos 5.5.

Regards,

Phil
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-28-2010, 09:39 AM
John Doe
 
Default Wifi not working

From: Phil Savoie <psavoie1783@rogers.com>

> I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can
> see it. it comes up in NetworkManager but never gets an IP. the router
> is a linksys using WPA/PSK security. Would/could someone please help me
> out trying to get this to work? Output of several commands follows:

Could it be IPv6?

JD



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-28-2010, 11:04 AM
Phil Savoie
 
Default Wifi not working

John Doe wrote:
> Could it be IPv6?
>
> JD
>

I don't think so as I disabled IPV6 on install. But I do appreciate
your suggestion.

Thanks,

Phil
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-28-2010, 05:49 PM
Dave Miller
 
Default Wifi not working

Larry Vaden <vaden@...> writes:

>
> On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie <psavoie1783 <at>
rogers.com> wrote:
> > Beginning DHCP transaction.
>>TRIMMED<<
> > Jul 27 19:32:23 smurf3 NetworkManager: <info> *Device 'wlan0' DHCP
> > transaction took too long (>45s), stopping it.
> > Jul 27 19:32:23 smurf3 NetworkManager: <info> *wlan0: canceled DHCP
> > transaction, dhcp client pid 30770
>
> It would seem that one possibility is that the AP is not running a
> DHCP server.
>
> Another is that if the AP is running a DHCP server, it is restricting
> IP addresses to known clients.
>
> kind regards/ldv
> _______________________________________________
> CentOS mailing list
> CentOS <at> centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

A couple of suggestions:

1) I had very similar problems with some of the Broadcom drivers for my
laptop ("transaction took too long"). An easy test is to *BRIEFLY* disable
security on the AP and see if your system connects. If the two systems
connect then there is a problem syncing with WPA security. A possible
alternative is to use ndiswrapper and the Windows driver instead of the
native Linux driver. I've been really happy with ndiswrapper even if it
means I'm "impure" for using a Windows driver.

2) The actual key exchange is handled by a daemon called wpa_supplicant.
It can be finicky. The config files are /etc/sysconfig/wpa_supplicant
and /etc/wpa_supplicant/wpa_supplicant.cnf You may have better luck
fiddling with some of the settings in the configuration files. As an
example, ndiswrapper works better for me with -D wext instead of -D
ndiswrapper.

I've also seen restating wpa_supplicant (as root, "service wpa_supplicant
restart) fix things. Also, I've had better luck just getting the
wpa_supplicant configuration right and not using NetworkManager (service
NetworkManager stop). I just do a "ifup wlan0" from the command line.

Cheers,
Dave


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-28-2010, 06:07 PM
Akemi Yagi
 
Default Wifi not working

On Wed, Jul 28, 2010 at 10:49 AM, Dave Miller <dave@davenjudy.org> wrote:

> I've also seen restating wpa_supplicant (as root, "service wpa_supplicant
> restart) fix things. *Also, I've had better luck just getting the
> wpa_supplicant configuration right and not using NetworkManager (service
> NetworkManager stop). *I just do a "ifup wlan0" from the command line.

For, anyone who'd rather go for a non-NetworkManager route, this
article may help:

http://home.roadrunner.com/~computertaijutsu/wireless.html
(maintained by Scott Robbins)

Akemi
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 07-29-2010, 10:01 AM
John Doe
 
Default Wifi not working

From: Dave Miller <dave@davenjudy.org>

> Larry Vaden <vaden@...> writes:
>
> >
> > On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie <psavoie1783 <at>
> rogers.com> wrote:
> > > Beginning DHCP transaction.
> >>TRIMMED<<
> > > Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP
> > > transaction took too long (>45s), stopping it.
> > > Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP
> > > transaction, dhcp client pid 30770
> >
> > It would seem that one possibility is that the AP is not running a
> > DHCP server.
> >
> > Another is that if the AP is running a DHCP server, it is restricting
> > IP addresses to known clients.
> >
> > kind regards/ldv
> > _______________________________________________
> > CentOS mailing list
> > CentOS <at> centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
>
> A couple of suggestions:
>
> 1) I had very similar problems with some of the Broadcom drivers for my
> laptop ("transaction took too long"). An easy test is to *BRIEFLY* disable
> security on the AP and see if your system connects. If the two systems
> connect then there is a problem syncing with WPA security. A possible
> alternative is to use ndiswrapper and the Windows driver instead of the
> native Linux driver. I've been really happy with ndiswrapper even if it
> means I'm "impure" for using a Windows driver.
>
> 2) The actual key exchange is handled by a daemon called wpa_supplicant.
> It can be finicky. The config files are /etc/sysconfig/wpa_supplicant
> and /etc/wpa_supplicant/wpa_supplicant.cnf You may have better luck
> fiddling with some of the settings in the configuration files. As an
> example, ndiswrapper works better for me with -D wext instead of -D
> ndiswrapper.
>
> I've also seen restating wpa_supplicant (as root, "service wpa_supplicant
> restart) fix things. Also, I've had better luck just getting the
> wpa_supplicant configuration right and not using NetworkManager (service
> NetworkManager stop). I just do a "ifup wlan0" from the command line.

Doesn't it look like the wpa connection is successful?
It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure)
successful. Connected to wireless network 'pszone'."
Only stages 3/4 (the DHCP part) seems to fail...
The DHCPDISCOVER times out.
Google says that some people with linksys DHCP problems in linux rebooted it or
flashed it...

JD



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 03:02 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org