From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Mon, 2 Feb 2009 09:49:54 -0800 Subject: [ath9k-devel] ath9k WMP300nv2 (AR5416) In-Reply-To: <20090130224802.194360@gmx.net> References: <20090124184942.256880@gmx.net> <18812.40344.405972.672492@gargle.gargle.HOWL> <20090128131722.218060@gmx.net> <20090128193355.GD26656@tesla> <20090129192832.83600@gmx.net> <20090129194651.GC10772@tesla> <20090130162123.104260@gmx.net> <20090130165946.GE6534@tesla> <20090130224802.194360@gmx.net> Message-ID: <20090202174954.GA4509@tesla> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Fri, Jan 30, 2009 at 02:48:02PM -0800, Alexander Bartha wrote: > > Well evening > > i have tried to --mv /etc/udev/rules.d/regulatory.rules /lib/udev/rules.d/85-regulatory.rules-- > and --rmmod ath9k mac80211 cfg80211-- then --modprobe ath9k-- but i get in var/log/messages "link is not ready" "links is not ready" is not a bad message, it means you are just not associated and you can start now trying to associate. > then have removed crda 0.9.5 and installed crda1.0.1 During compiling of crda it detected file collisions in "/lib/udev/rules.d/85-regulatory.rules That's because the new version of crda-1.0.1 installs the file into /lib/udev/rules.d/85-regulatory.rules. So long as you have the file it is OK. > then > modprobe ath9k but also i get in var/log/messages "link is not ready". Again this is OK! > Then i have --mv /lib/udev/rules.d/85-regulatory.rules /etc/udev/rules.d/regulatory.rules-- and have removed the 1.0.1 crda and installed crda 0.9.5 during the compiling i got : Detected file collision(s):/etc/udev/rules.d/regulatory.rules. The version of CRDA won't matter much, you just need the rules file in proper place and a crda bin in /sbin/crda. Most of the changes from 0.9.5 to 1.0.1 were purely to help distributions out. One of the changes for exampl was to use now /lib/udev/rules.d/ intstead of /etc/udev/rules.d. I recommend to just use the latest version of crda anyway. > After that i have --modprobe ath9k-- and i got a ip from my linksys router. > Now i am realy confused. The think i know is that only crda0.9.5 works with my system maybe a newer udev would do the job. I only have installed udev 124 maybe it is to old. I'm pretty sure most version of udev should work fine with this, crda isn't using any complex setting from udev. > The problem with the dhcpd: > /var/log/messages: > Jan 30 23:23:00 ws1 [ 8926.298958] wlan0: associated > Jan 30 23:23:00 ws1 wpa_cli: interface wlan0 CONNECTED > Jan 30 23:23:02 ws1 dhcpcd[23605]: wlan0: dhcpcd 4.0.7 starting > Jan 30 23:23:02 ws1 dhcpcd[23605]: wlan0: broadcasting for a lease > Jan 30 23:23:03 ws1 dhcpcd[23605]: wlan0: offered 192.168.1.100 from 192.168.1.1 > Jan 30 23:23:03 ws1 dhcpcd[23605]: wlan0: checking 192.168.1.100 is available on attached networks > Jan 30 23:23:07 ws1 dhcpcd[23605]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1 > Jan 30 23:23:07 ws1 dhcpcd[23605]: wlan0: leased 192.168.1.100 for 86400 seconds > Jan 30 23:30:01 ws1 cron[23666]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons ) > Jan 30 23:31:37 ws1 [ 9443.502625] wlan0: disassociated (Reason: 4) You may want to fine tune your AP to not kick people off after a period of innactivity. You can find the reasons on IEEE-802.11 2007 doc: