Another Atheros not working

English Network/Internet
#1

I can’t get my Atheros wireless card to work. It appears to have set up correctly in YaST → Network Services → Network Settings. However, it doesn’t appear in Knetwork.

From another post’s suggestions here is my info:

sudo /sbin/lspci -nn | egrep “Ethernet|Atheros|Network”
00:08.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor [168c:0013] (rev 01)
00:0b.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)

uname -r
2.6.25.18-0.2-default

cat /etc/SuSE-release
openSUSE 11.0 (i586)
VERSION = 11.0

rp -qa | egrep “ndiswrapper|madwifi”
bash: rp: command not found

sudo /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:CA:45:CE:F0
inet addr:96.26.245.40 Bcast:96.26.255.255 Mask:255.255.192.0
inet6 addr: fe80::240:caff:fe45:cef0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15486 errors:0 dropped:0 overruns:0 frame:0
TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0
collisions:72 txqueuelen:1000
RX bytes:8595676 (8.1 Mb) TX bytes:354570 (346.2 Kb)
Interrupt:18 Base address:0x8000

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

wlan0 Link encap:Ethernet HWaddr 00:18:4D:78:BE:97
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-18-4D-78-BE-97-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)

lsmod | grep ath
ath5k 96644 0
mac80211 178328 1 ath5k

sudo /usr/sbin/iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.

The plan is to use a wireless router using DHCP. (Worked before). Currently using ethernet cable.

#2

Parthenolide wrote:
> I can’t get my Atheros wireless card to work. It appears to have set up
> correctly in YaST → Network Services → Network Settings. However,
> it doesn’t appear in Knetwork.

One other command to run - ‘dmesg | grep ath’. Does that yield any clues?

Larry

#3

dmesg | grep ath
ath5k_pci 0000:00:08.0: registered as ‘phy0’
ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
ath5k phy0: RF2112A 2GHz radio found (0x56)
ath5k phy0: noise floor calibration timeout (2422MHz)

#4

You forgot to specify your ESSID in YaST > Network Devices > Network Settings > [your wireless card]. You can get the correct ESSID by issuing su and then iwlist scan.

#5

iwlist scan
lo Interface doesn’t support scanning.

wmaster0 Interface doesn’t support scanning.

wlan0 No scan results

eth0 Interface doesn’t support scanning.

pan0 Interface doesn’t support scanning.

#6

I did the iwlist from another computer. The the essid value used during the setup is correct, as is the shared key.

I’m wondering if this is a kde3/kde4 version issue. The dependencies of a number of packages are off, i.e., some have upgrades and show blue. Others in in red indicating that They are an upgrade from the packages that are available. There are a number of other things not working well, like the updater, etc.

#7

I have the exact same situation. Because this thread is active I will just add all my stuff looks just like the posters.

One thing that bothers me and I can find no documentation about it. Ath5k is supposed to work with the AR5213 chip but the poster and I have a AR5213A chip. I wonder if this is the problem.

Myself I haven’t tried ndiswrapper yet because I have read that the ath5k drive will set up the card to use the full 300mw radio and the full 54mb data throughput.

#8

Under suse 11, I was never able to get the ath5k driver working. The madwifi driver functions tolerably for normal station (client) use. I would recommend trying the madwifi driver.

I have a working version of ath5k under a wireless testing kernel, which gives me hopes that this will work out of the box with suse 11.1.

#9

Enabling Atheros wireless under SuSE 11.1 is significantly different that under previous releases. It uses a new driver called ath5k, versus the old madwifi driver approach. The ath5k driver is much easier to use as one does not have to use the command line to load drivers, etc.

To accomplish:

  1. YaST → Network Devices → Network Settings
    A gray pop-up window appears indicating a Warning, that Network manager settings is controlled by network manager and cannot be set by YaST. Click okay.

  2. This should take you to the section of global settings. Check the radio box for “traditional method with ifup” and click okay.

  3. This should cause Network Settings to exit with the completed changes.

  4. repeat: YaST → Network Devices → Network Settings
    Click on the Atheros network card, and edit the settings. Hit Ok to complete settings for Network Settings.

  5. repeat: YaST → Network Devices → Network Settings
    Click on the tab for Global options. Click radio button for user controlled with Network Manager. Click ok.

  6. Wireless network should be active. If not, go into Network Manager and make appropriate changes, such as auto-connect, etc.

#10

Parthen, you SAVED THE DAY, man. I’ve been tearing my hair out for hours. THANK YOU!!!
Who’s of thought that little setting was wrong?