Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire

Jonathan E. Brickman Mon, 28 Sep 2009 16:18:48 -0700

I can't get any list of wireless networks at all. When I tell it to connect as if it were a wired, the lower-left dot goes green, the swirl keeps on going for several minutes, and then it reports connected, even though I have not typed in a key. After it reports connected, the ifconfig looks like this:
eth0 Link encap:Ethernet HWaddr 00:08:0d:9f:18:f4 inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::208:dff:fe9f:18f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34336 errors:0 dropped:0 overruns:0 frame:0 TX packets:20792 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47215866 (45.0 MB) TX bytes:1691300 (1.6 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:578 errors:0 dropped:0 overruns:0 frame:0 TX packets:578 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:29489 (28.7 KB) TX bytes:29489 (28.7 KB) wlan0 Link encap:Ethernet HWaddr 00:90:96:82:ea:85 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wmaster0 Link encap:UNSPEC HWaddr 00-90-96-82-EA-85-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

J.E.B.

Hi,

Your ifconfig says it is a wlan0 device so it's quite strange that gnome says it is a wired 802.1x wired network.

What messages do you get if you attempt to connect?

Cheers.

Patrick Shirkey
64 Studio Support Team

On 09/28/2009 10:43 PM, Jonathan E. Brickman wrote:

Below is a PNG; hope it makes it:

64studio 3b3 thinks that the wireless NIC is a wired NIC.

J.E.B.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Jonathan E. Brickman wrote:

Greetings.  I have just installed 3.0b3 into my old Toshiba laptop.  All 
is very well so far, except that the Atheros AR5212/AR5213 wifi is 
detected as a wired, not wireless, interface, and so the wireless 
network detection system isn't being engaged.  What can I do to help?

Can you be more specific?  I have no idea what "detected as a wired" means.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrAVg4ACgkQwRXgH3rKGfMUywCdEzPRPs6emUcBIZdII1DWJeqT
afgAnR2ehR+kKF6NbglYMHEZUAM2HwXh
=kZCs
-----END PGP SIGNATURE-----
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel


_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

Re: [64studio-devel] 3b3 wifi issue: AR5212/AR5213 detected as wire

Reply via email to