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
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.
<div class=3D"gmail_quote">On Tue, Jul 27, 2010 at 6:31 PM, Brandon Lozza <=
span dir=3D"ltr"><<a href=3D"mailto:brandon@pwnage.ca">brandon@pwnage.c a=
</a>></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 <<a href=3D=
"mailto:metherid@gmail.com">metherid@gmail.com </a>> wrote:<br>
> On 07/28/2010 04:06 AM, Sam Varshavchik wrote:<br>
> =A0> According to this two year-old post, it's possible to buil=
d Firefox<br>
> =A0> with gstreamer support:<br>
> =A0><br>
> =A0> <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>
> =A0><br>
> =A0><br>
> =A0> Dunno if any of that is true today.<br>
> =A0><br>
> =A0> There's precedent for Firefox using system components inst=
ead of<br>
> =A0> bundled ones. Firefox already uses hunspell instead of its own=
bundled<br>
> =A0> dictionary, for spell checking. It makes sense for Firefox to =
use<br>
> =A0> gstreamer, instead of any bundled codecs.<br>
><br>
><br>
> The blog post talks about a non upstreamed patch and Firefox doesn'=
;t use<br>
> =A0Gstreamer at all now. =A0 It isn't just a matter of a bundled v=
s system<br>
> =A0components at this point. =A0 =A0Non upstreamed patches are not a o=
ption for<br>
> =A0Firefox for trademark reasons as well.<br>
><br>
><br>
> =A0Rahul<br>
><br>
> =A0--<br>
> =A0devel mailing list<br>
> =A0<a href=3D"mailto:devel@lists.fedoraproject.org">deve l@lists.fedora=
project.org</a><br>
> =A0<a href=3D"https://admin.fedoraproject.org/mailman/listinfo/devel" =
target=3D"_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a=
><br>
><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>
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
--===============8443600981867468111==--
07-28-2010, 01:19 AM
Larry Vaden
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
07-28-2010, 01:38 AM
Phil Savoie
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
07-28-2010, 09:39 AM
John Doe
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
07-28-2010, 11:04 AM
Phil Savoie
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
07-28-2010, 05:49 PM
Dave Miller
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
07-28-2010, 06:07 PM
Akemi Yagi
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
07-29-2010, 10:01 AM
John Doe
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