Cant find network, atheros (configured)

(suse 11.0 - 32bit, Atheros 5211)

Hello.

After a good sweat, I managed to configure Atheros with madwifi.
Installed wpa_supplicant too, started the card.

But no matter what I try, it is always in “Scanning” and cannot find network.

On my router linksys, I tried:

  1. WPA2, AES
  2. WPA2, AES + TKIP
  3. WPA, AES
  4. WPA, TKIP
  5. WEP

Card is configured to:
DHCP, Managed, essid (with same name as in router),
WPA-PSK (I reckon that router should be set to “WPA Personal”)
Passphrase (same as in router)

on a second time “ifup” :


laptux:/etc # ifup wlan0
    wlan0     device: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
    wlan0     warning: WPA configured but may be unsupported
    wlan0     warning: by this device
    wlan0     warning: wpa_supplicant already running on interface
DHCP client is already running on wlan0

I do not know what else to do. Any ideas?
Thanks

What does the end of the dmesg output say about wlan0?

Sorry, I do not know how to use dmesg. Say what to type.

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

dmesg

Good luck.

beli0135 wrote:
| Sorry, I do not know how to use dmesg. Say what to type.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIfpxK3s42bA80+9kRAoGUAJ4hZ/BdA/ZL44r40ZDtxno40NZQTACeN2ip
1EsCbf7YgAAfpl0wNUqBbNc=
=eR+K
-----END PGP SIGNATURE-----

beli0135 wrote:
> Sorry, I do not know how to use dmesg. Say what to type.

In a terminal, type ‘dmesg’. It displays the contents of the log for the current
boot.

One part is this:

SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.11 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.11 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002
CPU1 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000001
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.11 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.11 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 200.162.194.244, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 200.162.192.29, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 66.180.174.35, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
printk: 2 messages suppressed.
martian source 192.168.0.11 from 63.236.73.20, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
printk: 4 messages suppressed.
martian source 192.168.0.11 from 78.47.172.13, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
printk: 4 messages suppressed.
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
printk: 1 messages suppressed.
martian source 192.168.0.11 from 63.236.73.20, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
printk: 1 messages suppressed.
martian source 192.168.0.11 from 78.47.172.13, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 63.236.73.20, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 66.180.174.35, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 78.47.172.13, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 216.239.116.151, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
martian source 192.168.0.11 from 63.236.73.20, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.12 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.11 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
martian source 192.168.0.11 from 66.180.174.35, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.11 DST=216.239.116.157 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=43010 DF PROTO=TCP SPT=9748 DPT=80 WINDOW=6432 RES=0x00 ACK FIN URGP=0
martian source 192.168.0.11 from 78.47.172.13, on dev eth0
ll header: 00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00
SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.11 DST=130.57.4.15 LEN=497 TOS=0x00 PREC=0x00 TTL=64 ID=4278 DF PROTO=TCP SPT=20650 DPT=80 WINDOW=63 RES=0x00 ACK PSH FIN URGP=0
SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.11 DST=66.180.174.35 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=54632 DF PROTO=TCP SPT=22964 DPT=80 WINDOW=91 RES=0x00 ACK FIN URGP=0 OPT (0101080A000002773189AA98)
SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.11 DST=130.57.4.15 LEN=567 TOS=0x00 PREC=0x00 TTL=64 ID=59284 DF PROTO=TCP SPT=20651 DPT=80 WINDOW=54 RES=0x00 ACK PSH FIN URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=78.47.172.13 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47959 DF PROTO=TCP SPT=11650 DPT=80 WINDOW=272 RES=0x00 ACK FIN URGP=0 OPT (0101080A000010FC19511E17)
SFW2-INext-DROP-DEFLT-INV IN=eth0 OUT= MAC=00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00 SRC=63.236.73.20 DST=192.168.0.11 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=26775 DF PROTO=TCP SPT=80 DPT=20321 WINDOW=54 RES=0x00 ACK FIN URGP=0 OPT (0101080A11433905FFFF93A4)
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=216.239.116.157 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=43011 DF PROTO=TCP SPT=9748 DPT=80 WINDOW=6432 RES=0x00 ACK FIN URGP=0
SFW2-INext-DROP-DEFLT-INV IN=eth0 OUT= MAC=00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00 SRC=216.239.116.157 DST=192.168.0.11 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=30312 PROTO=TCP SPT=80 DPT=9748 WINDOW=8190 RES=0x00 ACK FIN URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=130.57.4.15 LEN=497 TOS=0x00 PREC=0x00 TTL=64 ID=4279 DF PROTO=TCP SPT=20650 DPT=80 WINDOW=63 RES=0x00 ACK PSH FIN URGP=0
SFW2-INext-DROP-DEFLT-INV IN=eth0 OUT= MAC=00:1f:c6:1f:5c:3a:00:1d:7e:f1:dd:2a:08:00 SRC=216.239.116.157 DST=192.168.0.11 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=34278 PROTO=TCP SPT=80 DPT=9748 WINDOW=8190 RES=0x00 ACK FIN URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=130.57.4.15 LEN=567 TOS=0x00 PREC=0x00 TTL=64 ID=59285 DF PROTO=TCP SPT=20651 DPT=80 WINDOW=54 RES=0x00 ACK PSH FIN URGP=0
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=63.236.73.20 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=21801 DF PROTO=TCP SPT=20321 DPT=80 WINDOW=227 RES=0x00 ACK FIN URGP=0 OPT (0101080A0000563E1142F7A0)
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=66.180.174.35 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=54633 DF PROTO=TCP SPT=22964 DPT=80 WINDOW=91 RES=0x00 ACK FIN URGP=0 OPT (0101080A000059B73189AA98)
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.11 DST=78.47.172.13 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47960 DF PROTO=TCP SPT=11650 DPT=80 WINDOW=272 RES=0x00 ACK FIN URGP=0 OPT (0101080A000076FC19511E17)

One thing to try is to blacklist the built in ath5 suse drivers and try and see if you can also connect to the wireless network set to “open”, once that works then try enabling the security. I was running into similar problems as you were.

Tried, but nothing happens.
Just for test, I dropped suse and installed Kubuntu… same problem with wireless.
Simply, cannot find network.

Seems that my atheros, on my Asus is highy unfriendly and uncooperative.

Hummm, what I did was uninstall the ath5 built in driver, install the madwifi ones and once it detected the card enteed the essid name ( open unsecure at first ) then played with it until connected, then added security.

If both suse and kbuntu are giving you trouble, email the madwifi guys with your cards info and see if they might have missed it. Is this one of those built in usb deals on an asus board? my P5k deluxe wifi gave me head aches in 10.3 for a while until a kernel update fixed it.

beli0135 wrote:
> Tried, but nothing happens.
> Just for test, I dropped suse and installed Kubuntu… same problem
> with wireless.
> Simply, cannot find network.
>
> Seems that my atheros, on my Asus is highy unfriendly and
> uncooperative.

Please open a terminal and enter the following:

/sbin/lspci
/sbin/lspci -n

One line of the first output should mention your wireless device. Match the bus
address (the numbers at the front with the second set of outputs and post those
two lines. If your first output does not show the wireless, then try

lsusb

If your wireless shows up there, post that line.

Larry

…I never give up.

I have installed 10.3, downloaded new kernel, set it up, compiled, then backed up.

Installed 11.0 back on, did make modules_install and make install and it started to function properly. Now I have wireless driver directly from kernel.
Card is properly reckognized and configured.

Now I have another problem. wpa_supplicant is installed.
Network on router (cisco linksys) is set to WPA personal, with AES and passphrase.
However, KWiFiManager cannot find any networks. (even though there are 2 unprotected networks around, as well as few WPA2 and bunch of WPA in the range - windows XP reports it)

When I do: #> ifup wlan0
it gives me following warning: “WPA Configured but may be unsupported by this device.”
“wpa_supplicant aready running on interface”

Wireless is configured to DHCP,
Operating mode: managed
ESSID: varnus (name of my network set on router)
Authentication: WPA-PSK
Key input type: passphrase

Any suggestions?

Anyone can help?

beli0135 wrote:

>
> Anyone can help?
>
>

You have installed the Madwifi drivers, that much you’ve made plain.

By the fact that ‘wlan0’ exists, you are NOT using the madwifi drivers, you
are still using the ATH5K module.

As was mentioned before, you need to blacklist the ath5k driver, which will
THEN allow the madwifi drivers to find the card. Your wifi will then be
named ‘ath0’.

You need to put ‘blacklist ath5k’ into a file in the /etc/modprobe.d subdir.

This command (as root) will do that:

echo “blacklist ath5k” > /etc/modprobe.d/ath5k.blacklist

Then reboot your system. If you have installed the Madwifi drivers
properly, you should get ‘ath0’ as your wireless nic name. Everything
should work at that point.

There is a MadWifi repository, which may be used to automatically install
Madwifi drivers, without you needing to compile and install then yourself.
The repo driver will also update as necessary if the kernel is updated. If
you installed the drivers by hand, you will lose wireless when the kernel
is updated, until you remember (how) to recompile/reinstall the driver
again.

The MadWifi Repo is highly recommended as a solution.

But you still need to blacklist ath5k.


L R Nix
lornix@lornix.com

I have the same card and its working perfectly under kubuntu.So there is something u are doing wrong.Unfortunatelly i have opensuse intalled on the desktop pc wich does not have the same card.Im afraid i cant help u,but again card works on ubuntu.So see what u are doing wrong.

Question:U cannot see any wireless neteworks at all?

I am not using madwifi. I did clean install of openSUSE 11.0, downloaded kernel 2.6.26, enabled atheros driver, compiled and installed.
Atheros was immediately reckognized, and I set it up.

Now, I added wpa_supplicant.conf in this manner:


ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
network={
	ssid="varnus"
	scan_ssid=1
	proto=WPA
	pairwise=TKIP
	key_mgmt=WPA-PSK
	psk="secret passphrase"
}

butm it just rolls over nothing as usual.


RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds

Do I really need MadWiFi, since I have kernel driver?

Did you REALLY get to kernel 2.6.26? The rest of us are all still back at
2.6.25.11-0.1
[Do ‘uname -a’]

As has been pointed out elsewhere, the LAST thing you want to try is to learn
how to compile your own driver (only after everything ELSE fails). [And compiling
your own kernel is even more of an advanced exercise.]

YES, you really need MadWifi driver, since your present one is returning
ZERO BYTES from the attempt to scan for existing APs. [That’s exactly
what it did for me, which is why I blacklisted it (ath5k) and installed the
(older) madwifi drivers.]

You do NOT need to compile the madwifi driver
(if you are running a distributed kernel, which you should be.)
Instead, you can use these instructions to install:
Atheros madwifi - openSUSE

[Didn’t some wise person say something about ‘You can lead a horse to water, but…’?]

[Didn’t some wise person say something about ‘You can lead a horse to water, but…’?]

I have dne nothing to offend you in any way, and I do demand to be addressed with a respect, as to any other member.

I do know how to compile a kernel and I do have substantial knowledge, however, I do not have knowledge about wireless, that is why I addressed the member here to help.
And I do not see why I ‘should’ use original kernel? It is compiled with so much modules and drivers, and for i586, so this doesn’t run as I want it to. But that is for another thread.

OK, I understand that I need MadWiFi driver, so I will black-list atheros kernel driver, and I will compile it from source.
Thanks for advice.
I will post the progress.

First I downloaded madwifi source, but didn’t compiled and I am too tired to debug right now.
So, what I did.

  1. I booted suse’s pae kernel that was installed by default.
  2. blacklisted ath5k
  3. rebooted
  4. installed madwifi for the pae kernel from repository
  5. modprobe ath_pci
  6. rebooted

DOESNT WORK!

in Yast, there is Atheros - Not Configured, edit button disabled, I can’t put ath_pci in module combobox.

I tried doing modprobe fewtimes more and rebooting, same thing.

FINALLY!!

It is working, but on the most stupid workaround.

OK, I told you above that it didn’t wanna load ath_pci…
Then I went to a sysconfig and forced module loading. That didnt helped either.
Then I installed windows driver through ndiswrapper and set card to load that module. modprobed it, and rebooted.

Then, I went to YaST, and guess what? The card was up with ath_pci !!! Why it didn’t want to load before I modprobed ndiswrapper, I really do not know, but now is working… Stupid, but working.

Well, stopped working after reboot…
I am so pissed off now… :frowning: