[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez <lrodriguez@atheros.com>]

On Thu, Jan 29, 2009 at 11:28:32AM -0800, Alexander Bartha wrote:
> Hello Luis
> 
> thanks for your answer i have done debugging and attached log files as attachment. The log file from building crda is from my portage (gentoo system) cause crda is in the software tree of gentoo. The first working solution was to go back from 1.0.1 crda to crda 0.9.5 this works with the ath9k driver "compat-wireless-2.6.tar.bz2"--from-26.01.2009

OK so everything looks good except I am in doubt your udev rule file is being setup
in place correctly. Can you do:

cat /lib/udev/rules.d/85-regulatory.rules
cat /etc/udev/rules.d/regulatory.rules

> Do you know some problems from the ath9k where the driver loses the connection and renewal the ip per dhcpd???
> there the output of /var/log/messages in this case:
> Jan 29 17:56:19 ws1 wpa_cli: interface wlan0 CONNECTED
> Jan 29 17:56:20 ws1 dhcpcd[8482]: wlan0: dhcpcd 4.0.7 starting
> Jan 29 17:56:20 ws1 dhcpcd[8482]: wlan0: broadcasting for a lease
> Jan 29 17:56:21 ws1 dhcpcd[8482]: wlan0: offered 192.168.1.100 from 192.168.1.1
> Jan 29 17:56:21 ws1 dhcpcd[8482]: wlan0: checking 192.168.1.100 is available on attached networks
> Jan 29 17:56:26 ws1 dhcpcd[8482]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
> Jan 29 17:56:26 ws1 dhcpcd[8482]: wlan0: leased 192.168.1.100 for 86400 seconds
> Jan 29 17:56:29 ws1 [  238.543007] wlan0: no IPv6 routers present
> Jan 29 18:00:01 ws1 cron[8538]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
> Jan 29 18:00:01 ws1 cron[8539]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
> Jan 29 18:01:27 ws1 [  537.287651] wlan0: disassociated (Reason: 4)
> Jan 29 18:01:27 ws1 dhcpcd[8507]: wlan0: carrier lost
> Jan 29 18:01:27 ws1 wpa_cli: interface wlan0 DISCONNECTED
> Jan 29 18:01:28 ws1 [  538.288019] wlan0: associate with AP f5d6b6a8
> Jan 29 18:01:28 ws1 dhcpcd[8507]: wlan0: received SIGTERM, stopping
> Jan 29 18:01:29 ws1 [  538.487016] wlan0: associate with AP f5d6b6a8
> Jan 29 18:01:29 ws1 [  538.687013] wlan0: associate with AP f5d6b6a8
> Jan 29 18:01:29 ws1 [  538.887013] wlan0: association with AP f5d6b6a8 timed out
> Jan 29 18:01:30 ws1 [  539.826138] wlan0: authenticate with AP f5d6b6a8
> Jan 29 18:01:30 ws1 [  539.828127] wlan0: authenticated
> Jan 29 18:01:30 ws1 [  539.828132] wlan0: associate with AP f5d6b6a8
> Jan 29 18:01:30 ws1 [  539.832140] wlan0: RX ReassocResp from f2ebe02a (capab=0x411 status=0 aid=2)
> Jan 29 18:01:30 ws1 [  539.832145] wlan0: associated
> Jan 29 18:01:30 ws1 wpa_cli: interface wlan0 CONNECTED
> Jan 29 18:01:31 ws1 dhcpcd[9429]: wlan0: dhcpcd 4.0.7 starting
> Jan 29 18:01:31 ws1 dhcpcd[9429]: wlan0: broadcasting for a lease
> Jan 29 18:01:32 ws1 dhcpcd[9429]: wlan0: offered 192.168.1.100 from 192.168.1.1
> Jan 29 18:01:32 ws1 dhcpcd[9429]: wlan0: checking 192.168.1.100 is available on attached networks
> Jan 29 18:01:38 ws1 dhcpcd[9429]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
> Jan 29 18:01:38 ws1 dhcpcd[9429]: wlan0: leased 192.168.1.100 for 86400 seconds
> 
> 
> ??????????? time to try a newer driver???????.

wireless-testing is always being updated, can't say I have seen this issue myself,
but again try the latest and if you see issue please report them.

  Luis