Atheros Wireless

i have a Acer aspire 7535 with 4 gig ram 320 gig hard drive and it is a 64 bit AMD Athlon QL 65
it has an atheros wireless card in it everything says that it is working i have the light on and it is picking up the network. but firefox is saying that it cannot locate the server.
i ran the startup using asc and i have no red input at all i have the ip address listed as well but cannot get on the internet unless i connect with the etho wired. any ideas as what i should look for? this has got me stummped…

What are you using to try to connect? knetworkmanager or YAST->isup? (default). You would define the connection parameters by the method you wish to use to connect then firefox or koncourror etc can connect. On many systems ipv6 can pose a problem and may need to be deactivated. Another thing is that with wireless, there can be interfering walls and other electronics that may bother connections, so moving the netbook to another location may clear this up.

It’s sometimes necessary to code the IP addresses of the gateway and the Name Servers into the config for the wireless card (so that sites on the Internet can be found). But whether that’s the solution for you depends on whether you’re getting a good connection to the router/modem that suppleis the internet to your computer. If you are getting a good connection then finding sites on the internet needs to be addressed.

To check this, please run these commands and report back:

  • /usr/sbin/iwconfig
  • /sbin/ifconfig
  • /sbin/route
  • cat /etc/resolv.conf | grep nameserver

Also, please tell us if you are using Gnome or KDE and (as techwiz03 noted) if using a networkmanager of yast to control the network settings

I have more info on my problem
i am using kde and it is an theros 928 series driver that is loaded it is active and it is by rights the right driver the router is less than 10 feet from the system and i am using the network manager to set-up withKernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 1 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo

default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

this is the read-out from /sbin/route

this is the read-out from /sbin/ifconfig

eth0 Link encap:Ethernet HWaddr 00:26:2D:57:BB:CD
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::226:2dff:fe57:bbcd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10358 errors:0 dropped:0 overruns:0 frame:1
TX packets:8385 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12086880 (11.5 Mb) TX bytes:1161998 (1.1 Mb)
Interrupt:16

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:136 errors:0 dropped:0 overruns:0 frame:0
TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9328 (9.1 Kb) TX bytes:9328 (9.1 Kb)

wlan0 Link encap:Ethernet HWaddr 0C:60:76:16:21:E6
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 0C-60-76-16-21-E6-00-00-00-00-00-00-00-00-00-00
UP RUNNING MTU:0 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)

this is the read-out from /usr/sbin/iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Are You sure You’ve got the proper driver ?
What does this command tell You ?

/usr/sbin/iwlist scan

Also please use the code tags while posting the output of terminal commands here as it greatly improves readability.
Posting in Code Tags - A Guide

Best regards,
Greg

Problem may be found … look at the above segments. Knetworkmanager does not have the ESSID nor the access point so even though you have a recognized hwaddress and adapter, it cannot negotiate since it doesn’t have a defined connection and valid parameters to use. I would suggest how I fixed this on my system. In my case, knetworkmanager would not do association until I used YAST->ifup method to set the ESSID and encrypt psw to get the network connection working. Then I went back and changed to knetworkmanager (after changing YAST from ifup to knetwork managed) and it then recognized the ESSID and psw to make the association. Please note that if you are regularly connecting to the same access point (your router at home) all the time, ifup will work best for you. knetworkmanager is for use when you regularly change the access point on the fly between multiple possible networks. Also, as I have found, you must create one working network config as I noted under YAST->ifup method first then switch to knetworkmanager and again make sure that defined connection is working before knetworkmanager will accept and work with other networks.

This is not true. You can create the profile using knetworkmanager only. You don’t have to switch to ifup and then to knetworkmanager.

Best regards,
Greg

Oh you mean they have finally fixed knetworkmanager to be able to initialize a connection? It has always been able to replicate new instances once it has a working one but AFAICT it never could create an instance without ifup doing the creation first. This is good news then.

Yes it can. I have never used ifup and I can create profiles with knetworkmanager perfectly fine.

Best regards,
Greg

On 01/08/2011 08:06 AM, glistwan wrote:
>
> techwiz03;2275453 Wrote:
>> Oh you mean they have finally fixed knetworkmanager to be able to
>> initialize a connection? It has always been able to replicate new
>> instances once it has a working one but AFAICT it never could create an
>> instance without ifup doing the creation first. This is good news then.
> Yes it can. I have never used ifup and I can create profiles with
> knetworkmanager perfectly fine.

What version of openSUSE are you using? The exposure of “wmaster0” was
eliminated a long time ago.

You are correct that knetworkmanager can create a connection without ever using
ifup. The presence of /etc/sysconfig/network/ifcfg-wlan0 is not required.

Everyone who replied to this thread, Thank You! i now have wireless on this machine. the system was not picking up the domain settings and it took a while to figure out the problem. The Atheros card works by default on this system.and network manager did not need to be reconfigured. i did however have to disable the ipv6 in order to pick up the network correctly.

Great news. Thanks for the feedback.

Best regards,
Greg