You are not logged in.

#1 2012-06-17 13:46:04

melw
Member
Registered: 2011-04-09
Posts: 95

Solution for AR9287 Wireless?

Anyone know a way to get the Atheros AR9287 wireless to work properly?
At the moment my wireless are working fine, then it's slow as hell, back to good and so on.
I've been searching forums, googled and so on for hours.
Nothing that seems to be working and the issue seems to be rather old. Seems like it's been a known issue since 2010.

Anyone knows a solution for this?


I know I'm paranoid, but am I paranoid enought....

Offline

#2 2012-06-17 14:29:37

shellscriptcoder
Member
From: United States
Registered: 2012-06-15
Posts: 13

Re: Solution for AR9287 Wireless?

Can you please tell us what you've tried already? And perhaps post the output of

dmesg | grep ath9k

Also, what is the make of your computer?

Offline

#3 2012-06-17 15:10:47

snovik
Member
Registered: 2012-05-06
Posts: 97

Re: Solution for AR9287 Wireless?

encryption flags of the driver? That was a solution that helped me. Unfortunately I do have a link which describes exactly the solution.

I think this was solution for my case http://askubuntu.com/questions/37409/wh … eless-card

Last edited by snovik (2012-06-17 15:12:31)

Offline

#4 2012-06-18 02:40:07

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

Havn't tried much, really. After googleing coming up with several "solutions" i wrote this instead of trying all possible solutions. Have been checking router, tried with other computer and so on to make sure the problem isn't in the router or something like that. Comes down to wireless AR9287 in Linux. And to be honest, the best answers usually comes from arch forum instead of the scattered ones on google.

Will have a look at the link and will fix the output from dmesg tomorrow.


I know I'm paranoid, but am I paranoid enought....

Offline

#5 2012-06-18 10:24:05

shellscriptcoder
Member
From: United States
Registered: 2012-06-15
Posts: 13

Re: Solution for AR9287 Wireless?

And to be honest, the best answers usually comes from arch forum instead of the scattered ones on google.

That's a given. smile

Is your computer an Acer? Because those aren't very well-supported by some versions of the kernel. Have you upgraded to the latest version of the kernel yet?

Offline

#6 2012-06-18 10:48:19

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: Solution for AR9287 Wireless?

Driver quality can fluctuate, try a compat-wireless snapshot maybe? There are PKGBUILDs in the AUR.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#7 2012-06-18 10:50:29

jakobcreutzfeldt
Member
Registered: 2011-05-12
Posts: 1,033

Re: Solution for AR9287 Wireless?

It seems to me that the specific outcome of even failed attempts at solutions found online would be better than nothing for helping to diagnose the problem...

Offline

#8 2012-06-18 18:13:21

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

shellscriptcoder:
This is the output of dmesg | grep ath9k:

[    4.184805] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[    4.185014] Registered led device: ath9k-phy0

And yes, it's an Acer. Acer Aspire 3750ZG to be more specific. Ran a pacman -Syu for sure, but nothing more to update.

Snovik:
Tried that and changed to WPA2 instead of WPA. Uses AES (read it somewhere to use AES only... Not sure where i read it though). Maybe alittle more stable, but it's not running as smooth as it should.

.:B:. :
Having problem with the AUR packages. Seems like the ones in AUR doesn't work since kernel 3.0. Tried the latest stable version from wireless.kernel.org. I don't know what the hell i'm doing wrong, but following the instructions for building and installing the package doesn't work at all for me. Don't remember the proper english word for this, but it's "Åtgärd nekas" in swedish and it should be access denied or something in english (2 hours of sleep makes me.. Stupid)

jakobcreutzfeldt:
Asking here first since most of the "sollutions" i found was rather old. Most 2010 and 2011. If there was a good solution, arch forums usually works better then try all googled solutions.

Last edited by melw (2012-06-18 18:40:21)


I know I'm paranoid, but am I paranoid enought....

Offline

#9 2012-06-18 19:51:09

shellscriptcoder
Member
From: United States
Registered: 2012-06-15
Posts: 13

Re: Solution for AR9287 Wireless?

melw wrote:

shellscriptcoder:
This is the output of dmesg | grep ath9k:

[    4.184805] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[    4.185014] Registered led device: ath9k-phy0

And yes, it's an Acer. Acer Aspire 3750ZG to be more specific. Ran a pacman -Syu for sure, but nothing more to update.

Snovik:
Tried that and changed to WPA2 instead of WPA. Uses AES (read it somewhere to use AES only... Not sure where i read it though). Maybe alittle more stable, but it's not running as smooth as it should.

.:B:. :
Having problem with the AUR packages. Seems like the ones in AUR doesn't work since kernel 3.0. Tried the latest stable version from wireless.kernel.org. I don't know what the hell i'm doing wrong, but following the instructions for building and installing the package doesn't work at all for me. Don't remember the proper english word for this, but it's "Åtgärd nekas" in swedish and it should be access denied or something in english (2 hours of sleep makes me.. Stupid)

jakobcreutzfeld
Asking here first since most of the "sollutions" i found was rather old. Most 2010 and 2011. If there was a good solution, arch forums usually works better then try all googled solutions.

Wait... What do you mean by 'problems with the AUR?' I'm on 3.4.2-2 and I have no problems with the AUR... Are you using something like packer or yuauort to automatically make the packages or are you building them from source?

Offline

#10 2012-06-18 21:41:44

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

shellscriptcoder wrote:
melw wrote:

shellscriptcoder:
This is the output of dmesg | grep ath9k:

[    4.184805] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[    4.185014] Registered led device: ath9k-phy0

And yes, it's an Acer. Acer Aspire 3750ZG to be more specific. Ran a pacman -Syu for sure, but nothing more to update.

Snovik:
Tried that and changed to WPA2 instead of WPA. Uses AES (read it somewhere to use AES only... Not sure where i read it though). Maybe alittle more stable, but it's not running as smooth as it should.

.:B:. :
Having problem with the AUR packages. Seems like the ones in AUR doesn't work since kernel 3.0. Tried the latest stable version from wireless.kernel.org. I don't know what the hell i'm doing wrong, but following the instructions for building and installing the package doesn't work at all for me. Don't remember the proper english word for this, but it's "Åtgärd nekas" in swedish and it should be access denied or something in english (2 hours of sleep makes me.. Stupid)

jakobcreutzfeld
Asking here first since most of the "sollutions" i found was rather old. Most 2010 and 2011. If there was a good solution, arch forums usually works better then try all googled solutions.

Wait... What do you mean by 'problems with the AUR?' I'm on 3.4.2-2 and I have no problems with the AUR... Are you using something like packer or yuauort to automatically make the packages or are you building them from source?

I'm downloading the tarball and uses makepkg.
I'm trying with the package called compat-wireless-patched-daily 2011_03_31-1 from AUR. Not sure what pkg to use, so i chose that one. Getting this error when using makepkg:

[1m[38;5;2m==>[m(B[1m Applying some patches[m(B
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
|index 0855cac..221bed6 100644
|--- a/net/mac80211/tx.c
|+++ b/net/mac80211/tx.c
--------------------------
Patching file net/mac80211/tx.c using Plan A...
Hunk #1 succeeded at 781 (offset 104 lines).
done
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|commit fffd6e63ea75850dafbf2ccfb38a4189f43c0282
|Author: Maxim Levitsky <maximlevitsky@xxxxxxxxx>
|Date:   Tue Jun 1 15:43:21 2010 +0300
|
|    wireless: allow to retrieve the channel set on monitor interface
|    
|    This will allow to preserve compatibility with userspace
|    
|    Signed-off-by: Maxim Levitsky <maximlevitsky@xxxxxxxxx>
|
|diff --git a/net/wireless/chan.c b/net/wireless/chan.c
|index b01a6f6..09d979b 100644
|--- a/net/wireless/chan.c
|+++ b/net/wireless/chan.c
--------------------------
Patching file net/wireless/chan.c using Plan A...
Hunk #1 succeeded at 82 (offset 33 lines).
Hunk #2 succeeded at 134 (offset 55 lines).
Hmm...  Ignoring the trailing garbage.
done
[1m[38;5;2m==>[m(B[1m Supported 802.11 drivers:[m(B
[1m[38;5;2m==>[m(B[1m 	ath5k[m(B
[1m[38;5;2m==>[m(B[1m 	ath9k[m(B
[1m[38;5;2m==>[m(B[1m 	ath9k_htc[m(B
[1m[38;5;2m==>[m(B[1m 	carl9170[m(B
[1m[38;5;2m==>[m(B[1m 	b43[m(B
[1m[38;5;2m==>[m(B[1m 	zd1211rw[m(B
[1m[38;5;2m==>[m(B[1m 	rt2x00[m(B
[1m[38;5;2m==>[m(B[1m 	wl1251[m(B
[1m[38;5;2m==>[m(B[1m 	wl12xx[m(B
[1m[38;5;2m==>[m(B[1m 	ath6kl[m(B
[1m[38;5;2m==>[m(B[1m 	brcm80211[m(B
[1m[38;5;2m==>[m(B[1m Supported group drivers:[m(B
[1m[38;5;2m==>[m(B[1m 	atheros <  ath5k ath9k carl9170 zd1211rw >[m(B
[1m[38;5;2m==>[m(B[1m 	ath <  ath5k ath9k carl9170 >[m(B
[1m[38;5;2m==>[m(B[1m 	iwlagn <  iwlagn >[m(B
[1m[38;5;2m==>[m(B[1m 	intel <  iwl3945 iwlagn >[m(B
[1m[38;5;2m==>[m(B[1m 	rtl818x <  rtl8180 rtl8187 >[m(B
[1m[38;5;2m==>[m(B[1m 	rtlwifi <  rtl8192ce >[m(B
[1m[38;5;2m==>[m(B[1m 	wl12xx <  wl1251 wl12xx (SPI and SDIO)>  [m(B
[1m[38;5;2m==>[m(B[1m Supported group drivers: Bluetooth & Ethernet:[m(B
[1m[38;5;2m==>[m(B[1m 	atlxx <  atl1 atl2 atl1e atl1c >[m(B
[1m[38;5;2m==>[m(B[1m 	bt <  Linux bluetooth drivers >[m(B
[1m[38;5;4m  ->[m(B[1m Please write the name of your driver or group, if you don't know which ones or want all please type 'all'[m(B
[35mProcessing new driver-select request...[00m
Backup exists: [36mMakefile.bk[00m
Backup exists: [36mMakefile.bk[00m
Backup exists: [36mMakefile.bk[00m
Backup exists: [36mMakefile.bk[00m
Backup exists: [36mdrivers/net/wireless/Makefile.bk[00m
Backup exists: [36mdrivers/net/wireless/ath/Makefile.bk[00m
Backup exists: [36mnet/wireless/Makefile.bk[00m
Backup exists: [36mdrivers/net/Makefile.bk[00m
Backup exists: [36mdrivers/ssb/Makefile.bk[00m
Backup exists: [36mdrivers/misc/eeprom/Makefile.bk[00m
Backup exists: [36mMakefile.bk[00m
[1m[38;5;2m==>[m(B[1m Starting build of ath9k drivers [m(B
/bin/sh: line 0: [: 39: unary operator expected
/bin/sh: line 0: test: too many arguments
/sbin/modprobe: invalid option -- 'l'
/sbin/modprobe: invalid option -- 'l'
make -C /lib/modules/3.4.2-2-ARCH/build M=/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31 modules
make[1]: Entering directory `/usr/src/linux-3.4.2-2-ARCH'
/sbin/modprobe: invalid option -- 'l'
/sbin/modprobe: invalid option -- 'l'
  CC [M]  /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/compat/main.o
In file included from include/net/net_namespace.h:13:0,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/net/net_namespace.h:7,
                 from include/linux/netdevice.h:49,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/net/netns/mib.h:15:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/net/netns/mib.h:15:15: error: missing binary operator before token "("
In file included from include/net/net_namespace.h:23:0,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/net/net_namespace.h:7,
                 from include/linux/netdevice.h:49,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/net/netns/xfrm.h:59:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/net/netns/xfrm.h:59:15: error: missing binary operator before token "("
In file included from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/net/net_namespace.h:7:0,
                 from include/linux/netdevice.h:49,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/net/net_namespace.h:80:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/net/net_namespace.h:80:15: error: missing binary operator before token "("
In file included from include/linux/netdevice.h:54:0,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/net/netprio_cgroup.h:40:5: warning: "IS_BUILTIN" is not defined [-Wundef]
include/net/netprio_cgroup.h:40:15: error: missing binary operator before token "("
include/net/netprio_cgroup.h:55:7: warning: "IS_MODULE" is not defined [-Wundef]
include/net/netprio_cgroup.h:55:16: error: missing binary operator before token "("
In file included from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5:0,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/linux/netdevice.h:148:39: error: missing binary operator before token "("
include/linux/netdevice.h:154:7: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:154:17: error: missing binary operator before token "("
include/linux/netdevice.h:160:6: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:160:16: error: missing binary operator before token "("
In file included from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.29.h:5:0,
                 from /home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/include/linux/compat-2.6.h:24,
                 from <command-line>:0:
include/linux/netdevice.h:965:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:965:15: error: missing binary operator before token "("
include/linux/netdevice.h:982:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:982:15: error: missing binary operator before token "("
include/linux/netdevice.h:1125:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:1125:15: error: missing binary operator before token "("
include/linux/netdevice.h:1128:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:1128:15: error: missing binary operator before token "("
include/linux/netdevice.h:1291:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:1291:15: error: missing binary operator before token "("
include/linux/netdevice.h:1295:5: warning: "IS_ENABLED" is not defined [-Wundef]
include/linux/netdevice.h:1295:15: error: missing binary operator before token "("
make[3]: *** [/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/compat/main.o] Error 1
make[2]: *** [/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/compat] Error 2
make[1]: *** [_module_/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31] Error 2
make[1]: Leaving directory `/usr/src/linux-3.4.2-2-ARCH'
make: *** [modules] Error 2

Last edited by melw (2012-06-19 14:06:57)


I know I'm paranoid, but am I paranoid enought....

Offline

#11 2012-06-18 23:35:36

shellscriptcoder
Member
From: United States
Registered: 2012-06-15
Posts: 13

Re: Solution for AR9287 Wireless?

I'm downloading the tarball and uses makepkg.
I'm trying with the package called compat-wireless-patched-daily 2011_03_31-1 from AUR. Not sure what pkg to use, so i chose that one. Getting this error when using makepkg:

make[3]: *** [/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/compat/main.o] Fel 1
make[2]: *** [/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31/compat] Fel 2
make[1]: *** [_module_/home/eae/aur/compat-wireless-patched-daily/src/compat-wireless-2011-03-31] Fel 2
make[1]: Lämnar katalogen "/usr/src/linux-3.4.2-2-ARCH"
make: *** [modules] Fel 2

Erm... Would you mind giving a few more details on the output of makepkg? For example, the entire block of text before the first error would be fine, or as much as you think would give a bit more information...

Offline

#12 2012-06-19 07:18:48

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: Solution for AR9287 Wireless?

Try prefixing your build command with LANG=C, like this:

$ LANG=C makepkg

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#13 2012-06-19 14:09:22

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

Output changed. Used prefix .:B:. wrote.


I know I'm paranoid, but am I paranoid enought....

Offline

#14 2012-06-19 15:29:55

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: Solution for AR9287 Wireless?

You should update to the latest release.

Try this PKGBUILD: http://sprunge.us/RNcH

Somehow the latest compat-wireless snapshot is older than the most recent kernel release though (3.4 was released in June). The older code might work just fine though.

If you're interested (and can/want to modify the PKGBUILD a bit) then you can try the wireless code that will be supplied by the 3.5 kernel:

http://linuxwireless.org/en/users/Downl … e_releases


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#15 2012-06-20 18:51:51

Usul
Member
Registered: 2007-05-17
Posts: 31

Re: Solution for AR9287 Wireless?

Seems to be a new bug in the kernel model, some guys discussing it on the kernel mailing list:

http://www.spinics.net/lists/linux-wire … 92434.html

The description does exactly match the symptoms I'm seeing too.

Edit: There is already a patch in the pipeline http://permalink.gmane.org/gmane.linux. … eral/93099

Last edited by Usul (2012-06-20 18:53:57)

Offline

#16 2012-06-24 22:26:14

kuba_g
Member
Registered: 2010-08-29
Posts: 4

Re: Solution for AR9287 Wireless?

Nothing that seems to be working and the issue seems to be rather old. Seems like it's been a known issue since 2010.

You are right. I have problem with this driver since 2010. The best working kernel for this wireless card is 2.6.37.6. Later they have changed some things and ping on newer kernels looked like this:
64 bytes from 10.0.0.138: icmp_req=503 ttl=64 time=13575 ms
64 bytes from 10.0.0.138: icmp_req=504 ttl=64 time=12882 ms
64 bytes from 10.0.0.138: icmp_req=505 ttl=64 time=12083 ms
64 bytes from 10.0.0.138: icmp_req=506 ttl=64 time=11107 ms
64 bytes from 10.0.0.138: icmp_req=507 ttl=64 time=12078 ms
64 bytes from 10.0.0.138: icmp_req=508 ttl=64 time=11533 ms

I've tried to send feedback to developers to solve this problem but it seems that no one cares. I am using 2.6.37 for 2 years, no xen, no kvm, old drivers ;/

Offline

#17 2012-06-24 22:26:41

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

.:B:.: Tried your version of the PKGBUILD and i tried making some of changes of my own (tried changing the source to the stable 3.4 version). Still getting the same error message. Tried download and build compat-wireless. That's not working very well for me. First, i'm no good at compiling my own stuff, i'm pretty much used to pacman and AUR. Even following the guide on how to build and install fails. Must be doing something wrong i guess.

Usul:
Looks like the same problem. But i don't know what they are talking bout and i don't really understand how to make use of the patch either.


I know I'm paranoid, but am I paranoid enought....

Offline

#18 2012-06-24 22:52:38

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

kuba_g wrote:

Nothing that seems to be working and the issue seems to be rather old. Seems like it's been a known issue since 2010.

You are right. I have problem with this driver since 2010. The best working kernel for this wireless card is 2.6.37.6. Later they have changed some things and ping on newer kernels looked like this:
64 bytes from 10.0.0.138: icmp_req=503 ttl=64 time=13575 ms
64 bytes from 10.0.0.138: icmp_req=504 ttl=64 time=12882 ms
64 bytes from 10.0.0.138: icmp_req=505 ttl=64 time=12083 ms
64 bytes from 10.0.0.138: icmp_req=506 ttl=64 time=11107 ms
64 bytes from 10.0.0.138: icmp_req=507 ttl=64 time=12078 ms
64 bytes from 10.0.0.138: icmp_req=508 ttl=64 time=11533 ms

I've tried to send feedback to developers to solve this problem but it seems that no one cares. I am using 2.6.37 for 2 years, no xen, no kvm, old drivers ;/

My pinging arn't all that bad. This is an example of how my pinging are behaving:

64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=32 ttl=53 time=23.3 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=33 ttl=53 time=72.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=34 ttl=53 time=30.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=35 ttl=53 time=29.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=36 ttl=53 time=28.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=37 ttl=53 time=84.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=38 ttl=53 time=422 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=39 ttl=53 time=476 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=40 ttl=53 time=1227 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=41 ttl=53 time=439 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=42 ttl=53 time=442 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=43 ttl=53 time=197 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=44 ttl=53 time=328 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=45 ttl=53 time=757 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=46 ttl=53 time=1107 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=47 ttl=53 time=1848 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=48 ttl=53 time=2477 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=49 ttl=53 time=1498 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=50 ttl=53 time=1388 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=51 ttl=53 time=37.4 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=52 ttl=53 time=416 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=53 ttl=53 time=80.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=55 ttl=53 time=28.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=56 ttl=53 time=26.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=57 ttl=53 time=357 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=58 ttl=53 time=25.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=59 ttl=53 time=157 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=60 ttl=53 time=551 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=61 ttl=53 time=1124 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=62 ttl=53 time=325 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=63 ttl=53 time=2513 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=64 ttl=53 time=1614 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=65 ttl=53 time=1224 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=66 ttl=53 time=1968 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=67 ttl=53 time=1140 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=68 ttl=53 time=376 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=69 ttl=53 time=1835 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=70 ttl=53 time=1518 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=71 ttl=53 time=5439 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=72 ttl=53 time=4441 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=73 ttl=53 time=4572 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=74 ttl=53 time=4392 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=75 ttl=53 time=3591 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=76 ttl=53 time=2669 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=77 ttl=53 time=238 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=78 ttl=53 time=1181 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=79 ttl=53 time=1588 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=80 ttl=53 time=569 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=81 ttl=53 time=432 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=82 ttl=53 time=429 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=83 ttl=53 time=123 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=84 ttl=53 time=168 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=85 ttl=53 time=396 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=86 ttl=53 time=25.7 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=87 ttl=53 time=543 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=88 ttl=53 time=232 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=89 ttl=53 time=23.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=90 ttl=53 time=21.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=91 ttl=53 time=30.9 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=92 ttl=53 time=30.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=93 ttl=53 time=38.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=94 ttl=53 time=27.9 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=95 ttl=53 time=27.4 ms

As you can see, it goes from ~25ms to as high as ~5000ms.


I know I'm paranoid, but am I paranoid enought....

Offline

#19 2012-06-25 20:28:03

kuba_g
Member
Registered: 2010-08-29
Posts: 4

Re: Solution for AR9287 Wireless?

melw wrote:

My pinging arn't all that bad. This is an example of how my pinging are behaving:

64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=32 ttl=53 time=23.3 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=33 ttl=53 time=72.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=34 ttl=53 time=30.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=35 ttl=53 time=29.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=36 ttl=53 time=28.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=37 ttl=53 time=84.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=38 ttl=53 time=422 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=39 ttl=53 time=476 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=40 ttl=53 time=1227 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=41 ttl=53 time=439 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=42 ttl=53 time=442 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=43 ttl=53 time=197 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=44 ttl=53 time=328 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=45 ttl=53 time=757 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=46 ttl=53 time=1107 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=47 ttl=53 time=1848 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=48 ttl=53 time=2477 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=49 ttl=53 time=1498 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=50 ttl=53 time=1388 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=51 ttl=53 time=37.4 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=52 ttl=53 time=416 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=53 ttl=53 time=80.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=55 ttl=53 time=28.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=56 ttl=53 time=26.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=57 ttl=53 time=357 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=58 ttl=53 time=25.0 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=59 ttl=53 time=157 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=60 ttl=53 time=551 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=61 ttl=53 time=1124 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=62 ttl=53 time=325 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=63 ttl=53 time=2513 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=64 ttl=53 time=1614 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=65 ttl=53 time=1224 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=66 ttl=53 time=1968 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=67 ttl=53 time=1140 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=68 ttl=53 time=376 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=69 ttl=53 time=1835 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=70 ttl=53 time=1518 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=71 ttl=53 time=5439 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=72 ttl=53 time=4441 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=73 ttl=53 time=4572 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=74 ttl=53 time=4392 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=75 ttl=53 time=3591 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=76 ttl=53 time=2669 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=77 ttl=53 time=238 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=78 ttl=53 time=1181 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=79 ttl=53 time=1588 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=80 ttl=53 time=569 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=81 ttl=53 time=432 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=82 ttl=53 time=429 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=83 ttl=53 time=123 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=84 ttl=53 time=168 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=85 ttl=53 time=396 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=86 ttl=53 time=25.7 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=87 ttl=53 time=543 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=88 ttl=53 time=232 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=89 ttl=53 time=23.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=90 ttl=53 time=21.8 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=91 ttl=53 time=30.9 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=92 ttl=53 time=30.2 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=93 ttl=53 time=38.6 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=94 ttl=53 time=27.9 ms
64 bytes from ftp.sunet.se (194.71.11.69): icmp_req=95 ttl=53 time=27.4 ms

As you can see, it goes from ~25ms to as high as ~5000ms.

Your pings are very bad smile same as mine. If you care about driver for your card please send your results to linux wireless mailing list and support my fight smile . If you want pings like this:

--- 192.168.1.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 1.564/1.846/2.204/0.185 ms

compile and install kernel 2.6.37.6

Offline

#20 2012-07-19 16:20:24

Usul
Member
Registered: 2007-05-17
Posts: 31

Re: Solution for AR9287 Wireless?

Kernel 3.4.5 has some bug fixes for ath*, my problems are gone with this kernel smile

Offline

#21 2012-07-22 10:55:50

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

Sweet. Will try it out when i get back from work.


I know I'm paranoid, but am I paranoid enought....

Offline

#22 2012-07-23 21:27:34

melw
Member
Registered: 2011-04-09
Posts: 95

Re: Solution for AR9287 Wireless?

Seems to be working better, but not as good as it should. Looking at pings to my ISP it returns with some higher pings. Maybe 1 of 10 is higher (~over 100ms to 500ms) and the normal time is ~30ms.

When i'm just looking at forums and stuff it can get really slow for afew seconds and then getting back to normal after afew seconds. Better, but still it's not working properly.


I know I'm paranoid, but am I paranoid enought....

Offline

Board footer

Powered by FluxBB