[ath9k-devel] ath9k WMP300nv2 (AR5416)

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

Hello Luis

thanks for all your mails they have helped.

Today i have solved my problem with the crda-1.0.1-r1.

Problemdiscription:
Only crda-0.9.5 works correct with my system. "crda-1.0.1-r1 or crda-1.0.1 dont call the second part of the frequenzes"

Solution:
Newest udev + newest hal + newest hal-info + newest cryptsetup from the gentoo package (portage) tree did the job.

Now i have the next question:
is this normal that i have to reload after each reboot my cfg80211, mac80211 and ath9k? I have installed compat-wireless-2009-02-06 but this was since i used my first dirver from your hompage. My system is loading automatically at boot cfg80211 mac80211 and ath9k but if i dont reload the driver the network cant start. 

Oh the newest driver (compat-wireless-2009-02-06) has a easter egg cause the led of the network card is blinking after loading ath9k. 

Please dont misunderstand me now this is the first time that the led on my LinksysWMP300nv2 works correctly.

Thanks for helping

Well evening

Alexander Bartha
-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

On Fri, Feb 06, 2009 at 12:22:05PM -0800, Alexander Bartha wrote:
> Hello Luis
> 
> thanks for all your mails they have helped.
> 
> Today i have solved my problem with the crda-1.0.1-r1.
> 
> Problemdiscription:
> Only crda-0.9.5 works correct with my system. "crda-1.0.1-r1 or crda-1.0.1 dont call the second part of the frequenzes"
> 
> Solution:
> Newest udev + newest hal + newest hal-info + newest cryptsetup from the gentoo package (portage) tree did the job.
> 
> Now i have the next question:
> is this normal that i have to reload after each reboot my cfg80211, mac80211 and ath9k? I have installed compat-wireless-2009-02-06 but this was since i used my first dirver from your hompage. My system is loading automatically at boot cfg80211 mac80211 and ath9k but if i dont reload the driver the network cant start.

Nope, you should not need to reload the modules unless you are
upgrading to a new set of modules. Can you explain what issues
you have during a fresh boot and fresh install of compat-wireless?

Are you using wpa_supplicant? Are you using Network Manager? Are
you using encryption? Are you using 11n?

Good to hear.

  Luis

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

hello Luis,

Hardware:
Wireless Card: LinksysWMP300Nv2
Wireless Router: LinksysWRT160
Router Wireless Config: 802.11N, Channel 12 (because there are many routers in the neighborhood using the lower channels)
SecurityMode: WPA2-Personal, Encryption: TKIP or AES

Packages:
Kernel: gentoo-sources-2.6.28-r1
linux-headers-2.6.28-r1
wpa_supplicant-0.6.4
compat-wireless-2009-02-14
iw-0.9.9
wireless-tools-29

my wpa_supplicant.conf:
update_config=1

ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
fast_reauth=1

# Ensure that only root can read the WPA configuration
#ctrl_interface_group=0
#
# Let wpa_supplicant take care of scanning and AP selection
ap_scan=1
#country=AT


network={
  ssid="MySSid"
# scan_ssid=1
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=TKIP CCMP
  group=TKIP CCMP
  psk="MyPsk"
  priority=2
}
(END) 

My Network-Konfiguration-File:/etc/init.d/net

modules=( "wpa_supplicant" )
wpa_supplicant_wlan0="-Dwext"
config_wlan0=( "dhcp" )
dhcpcd_wlan0="-t 10"
dhcp_wlan0="nonis"
channel_wlan0="12"
dns_domain_lo="localdnsdomain"



Error description:

When i boot my System i have to rmmod cfg80211 mac80211 ath9k + modprobe ath9k otherwise my Wlan Card (LinksysWMP300Nv2) does not 

work --the leds on my WlanCard will be turned off when wpa_supplicant is starting! After the reload the WlanCard work fine.

The goal at this problem is that in var/log/messages i have the same output as my problem with crda-0.9.5 (the second part of the 

frequences of crda isnt there).


Output:
[    6.422739] cfg80211: Using static regulatory domain info
[    6.422743] cfg80211: Regulatory domain: US
[    6.422746] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    6.422751] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[    6.422756] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    6.422760] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    6.422765] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    6.422770] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    6.422774] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    6.422779] cfg80211: Calling CRDA for country: US
[    6.491245] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[    6.507775] dib0700: loaded with support for 8 different device-types
[    6.507803] dvb_usb_dib0700 1-6:1.0: usb_probe_interface
[    6.507809] dvb_usb_dib0700 1-6:1.0: usb_probe_interface - got id
[    6.508112] dvb-usb: found a 'Terratec Cinergy DT USB XS Diversity' in cold state, will try to load a firmware
[    6.508118] usb 1-6: firmware: requesting dvb-usb-dib0700-1.20.fw
[    6.704575] hub 4-0:1.0: hub_suspend
[    6.704587] usb usb4: bus auto-suspend
[    6.704590] usb usb4: suspend_rh
[    6.919213] phy0: Selected rate control algorithm 'ath9k_rate_control'
[    6.924986] cfg80211: Calling CRDA for country: AT
[    6.925034] Registered led device: ath9k-phy0::radio
[    6.925058] Registered led device: ath9k-phy0::assoc
[    6.925083] Registered led device: ath9k-phy0::tx
[    6.925110] Registered led device: ath9k-phy0::rx
[    6.925138] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9140000, irq=20
[    6.925200] EMU10K1_Audigy 0000:04:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    6.930218] Installing spdif_bug patch: Audigy 2 ZS [SB0350]
[    6.947297] modprobe used greatest stack depth: 5956 bytes left
[    7.510643] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[    7.713502] dib0700: firmware started successfully.
[    8.214020] dvb-usb: found a 'Terratec Cinergy DT USB XS Diversity' in warm state.
[    8.214077] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    8.214313] DVB: registering new adapter (Terratec Cinergy DT USB XS Diversity)
[    8.410142] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[    8.569765] DiB0070: successfully identified
[    8.569771] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    8.570046] DVB: registering new adapter (Terratec Cinergy DT USB XS Diversity)
[    8.703395] DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
[    8.862768] DiB0070: successfully identified
[    8.862776] dvb-usb: Terratec Cinergy DT USB XS Diversity successfully initialized and connected.
[    8.862934] usbcore: registered new interface driver dvb_usb_dib0700
[    8.863139] modprobe used greatest stack depth: 4828 bytes left
[   11.888046] EXT3 FS on sda3, internal journal
[   12.362694] fuse init (API version 7.10)
[   12.384776] NTFS driver 2.1.29 [Flags: R/O MODULE].
[   12.398131] DLM (built Feb 10 2009 21:16:48) installed
[   12.429838] rtc_cmos 00:03: RTC can wake from S4
[   12.430015] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[   12.430049] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
[   12.891170] XFS mounting filesystem sda6
[   12.949000] Ending clean XFS mount for filesystem: sda6
[   12.984465] kjournald starting.  Commit interval 5 seconds
[   12.984713] EXT3 FS on sda11, internal journal
[   12.984721] EXT3-fs: mounted filesystem with journal data mode.
[   13.004941] kjournald starting.  Commit interval 5 seconds
[   13.005191] EXT3 FS on sda12, internal journal
[   13.005198] EXT3-fs: mounted filesystem with journal data mode.
[   13.055841] XFS mounting filesystem sda5
[   13.111428] Ending clean XFS mount for filesystem: sda5
[   13.158084] XFS mounting filesystem sda7
[   13.204406] Ending clean XFS mount for filesystem: sda7
[   13.246122] XFS mounting filesystem sda8
[   13.303238] Ending clean XFS mount for filesystem: sda8
[   13.341860] XFS mounting filesystem sda13
[   13.670415] Ending clean XFS mount for filesystem: sda13
[   13.842149] Adding 1004052k swap on /dev/sda2.  Priority:-1 extents:1 across:1004052k
[   17.638040] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[   19.733463] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[   21.684544] ADDRCONF(NETDEV_UP): wlan0: link is not ready

if i dont reload the modules "ADDRCONF(NETDEV_UP): wlan0: link is not ready" is the last relevant message in /var/log/messages!
if i only stop and start my /etc/init.d/net.wlan0 init script it also fails with the same output in var log message "link is not ready". 
After boot when i dont relaod cfg, mac, ath9k "iwlist channel" knows only channel 1-11. But when i am reloading cfg, mac and 
ath9k "iwlist channel" knows Channel 1-13. 

My Ap is working on Channel 12! 

Clear if he dont knows channel 12 and channel 13 he could not connect to my AP.

Is there any posibility to get it work without the relaod of cfg80211 mac80211 ath9k???

PS: I have tried the kernel from linux-wireless (wireless-testing.git 2.6.29-rc4 wow thats new!!!) but the problem was the same.

Maybe my partition layout is relevant to that problem (mounting some partition to late???) but i dont think so.
fstab:
/dev/sda1               /boot           ext2            noatime         1 2
/dev/sda3               /               ext3            noatime         0 1
/dev/sda6               /usr            xfs             noatime         0 1
/dev/sda11              /usr/bin        ext3            noatime         0 1
/dev/sda12              /usr/sbin       ext3            noatime         0 1
/dev/sda2               none            swap            sw              0 0
/dev/sda5               /home           xfs             noatime         0 1             
/dev/sda7               /opt            xfs             noatime         0 1
/dev/sda8               /var            xfs             noatime         0 1
/dev/sda13              /archiv         xfs             noatime         0 1
tmpfs                   /dev/shm        tmpfs           defaults        0 0
tmpfs                   /tmp            tmpfs           defaults        0 0
/dev/hda                /mnt/dvd        auto            noauto,user,users,ro  0 0
/dev/fd0                /mnt/floppy     auto            noauto          0 0

Well evening from Vienna
-- 
Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL 
f?r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

On Sat, Feb 14, 2009 at 3:06 PM, Alexander Bartha <alex.xy.privat@gmx.at> wrote:
> hello Luis,
>
> Hardware:
> Wireless Card: LinksysWMP300Nv2
> Wireless Router: LinksysWRT160
> Router Wireless Config: 802.11N, Channel 12 (because there are many routers in the neighborhood using the lower channels)
> SecurityMode: WPA2-Personal, Encryption: TKIP or AES
>
> Packages:
> Kernel: gentoo-sources-2.6.28-r1
> linux-headers-2.6.28-r1
> wpa_supplicant-0.6.4
> compat-wireless-2009-02-14
> iw-0.9.9
> wireless-tools-29
>
> my wpa_supplicant.conf:
> update_config=1
>
> ctrl_interface=/var/run/wpa_supplicant
> eapol_version=2
> fast_reauth=1
>
> # Ensure that only root can read the WPA configuration
> #ctrl_interface_group=0
> #
> # Let wpa_supplicant take care of scanning and AP selection
> ap_scan=1
> #country=AT
>
>
> network={
>  ssid="MySSid"
> # scan_ssid=1
>  proto=RSN
>  key_mgmt=WPA-PSK
>  pairwise=TKIP CCMP
>  group=TKIP CCMP
>  psk="MyPsk"
>  priority=2
> }
> (END)
>
> My Network-Konfiguration-File:/etc/init.d/net
>
> modules=( "wpa_supplicant" )
> wpa_supplicant_wlan0="-Dwext"
> config_wlan0=( "dhcp" )
> dhcpcd_wlan0="-t 10"
> dhcp_wlan0="nonis"
> channel_wlan0="12"
> dns_domain_lo="localdnsdomain"
>
>
>
> Error description:
>
> When i boot my System i have to rmmod cfg80211 mac80211 ath9k + modprobe ath9k otherwise my Wlan Card (LinksysWMP300Nv2) does not
>
> work --the leds on my WlanCard will be turned off when wpa_supplicant is starting! After the reload the WlanCard work fine.
>
> The goal at this problem is that in var/log/messages i have the same output as my problem with crda-0.9.5 (the second part of the
>
> frequences of crda isnt there).
>
>
> Output:
> [    6.422739] cfg80211: Using static regulatory domain info
> [    6.422743] cfg80211: Regulatory domain: US
> [    6.422746]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> [    6.422751]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> [    6.422756]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [    6.422760]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [    6.422765]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [    6.422770]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [    6.422774]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> [    6.422779] cfg80211: Calling CRDA for country: US
> [    6.491245] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> [    6.507775] dib0700: loaded with support for 8 different device-types
> [    6.507803] dvb_usb_dib0700 1-6:1.0: usb_probe_interface
> [    6.507809] dvb_usb_dib0700 1-6:1.0: usb_probe_interface - got id
> [    6.508112] dvb-usb: found a 'Terratec Cinergy DT USB XS Diversity' in cold state, will try to load a firmware
> [    6.508118] usb 1-6: firmware: requesting dvb-usb-dib0700-1.20.fw
> [    6.704575] hub 4-0:1.0: hub_suspend
> [    6.704587] usb usb4: bus auto-suspend
> [    6.704590] usb usb4: suspend_rh
> [    6.919213] phy0: Selected rate control algorithm 'ath9k_rate_control'
> [    6.924986] cfg80211: Calling CRDA for country: AT
> [    6.925034] Registered led device: ath9k-phy0::radio
> [    6.925058] Registered led device: ath9k-phy0::assoc
> [    6.925083] Registered led device: ath9k-phy0::tx
> [    6.925110] Registered led device: ath9k-phy0::rx
> [    6.925138] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9140000, irq=20

<-- snip -->

> if i dont reload the modules "ADDRCONF(NETDEV_UP): wlan0: link is not ready" is the last relevant message in /var/log/messages!

That is not a critical message, it means nothing bad. It just means
your card is not associated yet. Once it gets associated, you "link"
goes up.

> if i only stop and start my /etc/init.d/net.wlan0 init script it also fails with the same output in var log message "link is not ready".

That is not bad, it just means you are not associated.

> After boot when i dont relaod cfg, mac, ath9k "iwlist channel" knows only channel 1-11.

I believe Gentoo crda package may be installing the udev rule in the
wrong place. We used to use /lib/udev/rules.d and recently started
using /lib/udev/rules.d/ which seems to be more of an appropriate
place. Check which one you have. If you have both remove both and try
in only one location.

Can you recompile and install compat-wireless with this added to config.mk:

CONFIG_ATH9K_DEBUG=y

Then load ath9k like this:

modprobe ath9k debug=0x00000080

Before loading ath9k remember to unload all wireless modules you can
do that from compat-wireless by doing:

make unload

Then provide the output of:

iw list

> But when i am reloading cfg, mac and
> ath9k "iwlist channel" knows Channel 1-13.

There may be an issue with the udev rule location, here's a backport
of a patch I just posted though which may help too since you are
reloading right now (but reloading should not be required).

  Luis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: same-hint.patch
Type: text/x-patch
Size: 1281 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090214/c9b10c9f/attachment.bin 

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

Hello Luis,

i have rebuild compat-wireless with CONFIG_ATH9K_DEBUG=y in config.mk
then -- make unload -- modprobe ath9k debug=0x00000080 --
iw list-- (Output)
-2009-02-16 # iw list
Wiphy phy0
	Band 1:
		HT capabilities: 0x104e
			 * 20/40 MHz operation
			 * SM PS disabled
			 * 40 MHz short GI
			 * max A-MSDU len 3839
			 * DSSS/CCK 40 MHz
		HT A-MPDU factor: 0x0003 (65535 bytes)
		HT A-MPDU density: 0x0006 (8 usec)
		HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (20.0 dBm)
			* 2484 MHz [14] (disabled)
		Bitrates:
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
	Supported interface modes:
		 * IBSS
		 * Station
		 * AP
		 * AP(VLAN)
		 * Monitor
Looks good but after boot i never have channel 12 or 13.
The led on my LinksysWMP300Nv2 Card turned off after starting wpa_supplicant. At this point i cant get any connection to my AP. The only way is to reload cfg80211 mac80211 ath9k. After the reload he connects my outomatically to my AP without starting the /etc/init.d/net.wlan0 start script.

I have also patched the /usr/src/compat-wireless-2009-02-16/net/wireless/reg.c file with the same-hint.patch

what to do next???

The patch has not changed the need of reloading cfg80211 mac80211 and ath9k after boot if i want use my LinksysWMP300Nv2. 

Udev:
/lib/udev/rules.d/85-regulatory.rules
the location seems to be ok.
but at boot of my system he never loads the second part of the frequences
when cfg80211 loads.

Well evening from Vienna

Alexander Bartha 

 
-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

On Mon, Feb 16, 2009 at 12:51 PM, Alexander Bartha
<alex.xy.privat@gmx.at> wrote:
> Hello Luis,
>
> i have rebuild compat-wireless with CONFIG_ATH9K_DEBUG=y in config.mk
> then -- make unload -- modprobe ath9k debug=0x00000080 --
> iw list-- (Output)

You forgot to provide the kernel log when loading ath9k with debug.

  Luis

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

Hello Luis
i have no kernel.log. All my attemps to get a kernel.log or kern.log with syslog-ng where in vain. Mhhh????
Here is a list of my logfiles in /var/log/ Directory:
cups/             kdm.log           messages.3.gz     syslog
dmesg             lastlog           messages.4.gz     uucp.log
emerge-fetch.log  mail.err          mysql/            wtmp
emerge.log        maillog           news/             wtmp.1.gz
faillog           mail.log          portage/          xdm.log
gdm/              messages          rc.log            Xorg.0.log
genkernel.log     messages.1.gz     samba/            Xorg.0.log.old
HOSTS/            messages.2.gz     sandbox/          

So how i can debug ath9k or get the debug messages????

Well day

Alexander Bartha
-------- Original-Nachricht --------
> Datum: Mon, 16 Feb 2009 13:42:10 -0800
> Von: "Luis R. Rodriguez" <lrodriguez@atheros.com>
> An: Alexander Bartha <alex.xy.privat@gmx.at>
> CC: ath9k-devel at lists.ath9k.org, Luis.Rodriguez at atheros.com
> Betreff: Re: [ath9k-devel] ath9k WMP300nv2 (AR5416)

> On Mon, Feb 16, 2009 at 12:51 PM, Alexander Bartha
> <alex.xy.privat@gmx.at> wrote:
> > Hello Luis,
> >
> > i have rebuild compat-wireless with CONFIG_ATH9K_DEBUG=y in config.mk
> > then -- make unload -- modprobe ath9k debug=0x00000080 --
> > iw list-- (Output)
> 
> You forgot to provide the kernel log when loading ath9k with debug.
> 
>   Luis

-- 
Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL 
f?r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

Hello Luis
i have no kernel.log. All my attemps to get a kernel.log or kern.log with syslog-ng where in vain. Mhhh????
Here is a list of my logfiles in /var/log/ Directory:
cups/             kdm.log           messages.3.gz     syslog
dmesg             lastlog           messages.4.gz     uucp.log
emerge-fetch.log  mail.err          mysql/            wtmp
emerge.log        maillog           news/             wtmp.1.gz
faillog           mail.log          portage/          xdm.log
gdm/              messages          rc.log            Xorg.0.log
genkernel.log     messages.1.gz     samba/            Xorg.0.log.old
HOSTS/            messages.2.gz     sandbox/          

So how i can debug ath9k or get the debug messages????

Well day
-------- Original-Nachricht --------
> Datum: Mon, 16 Feb 2009 13:42:10 -0800
> Von: "Luis R. Rodriguez" <lrodriguez@atheros.com>
> An: Alexander Bartha <alex.xy.privat@gmx.at>
> CC: ath9k-devel at lists.ath9k.org, Luis.Rodriguez at atheros.com
> Betreff: Re: [ath9k-devel] ath9k WMP300nv2 (AR5416)

> On Mon, Feb 16, 2009 at 12:51 PM, Alexander Bartha
> <alex.xy.privat@gmx.at> wrote:
> > Hello Luis,
> >
> > i have rebuild compat-wireless with CONFIG_ATH9K_DEBUG=y in config.mk
> > then -- make unload -- modprobe ath9k debug=0x00000080 --
> > iw list-- (Output)
> 
> You forgot to provide the kernel log when loading ath9k with debug.
> 
>   Luis

-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Pavel Roskin]

On Fri, 2009-02-20 at 18:46 +0100, Alexander Bartha wrote:
> Hello Luis
> i have no kernel.log. All my attemps to get a kernel.log or kern.log with syslog-ng where in vain. Mhhh????
> Here is a list of my logfiles in /var/log/ Directory:
> cups/             kdm.log           messages.3.gz     syslog
> dmesg             lastlog           messages.4.gz     uucp.log
> emerge-fetch.log  mail.err          mysql/            wtmp
> emerge.log        maillog           news/             wtmp.1.gz
> faillog           mail.log          portage/          xdm.log
> gdm/              messages          rc.log            Xorg.0.log
> genkernel.log     messages.1.gz     samba/            Xorg.0.log.old
> HOSTS/            messages.2.gz     sandbox/          
> 
> So how i can debug ath9k or get the debug messages????

Kernel log is shown by the dmesg command.  The kernel has a certain
amount of memory for the log, so only older messages are not shown once
the memory is exhausted.  However, it's normally enough memory to hold
the full log from the boot time.

Kernel messages are normally logged to /var/log/messages, but the debug
messages may be omitted.  The kernel messages during the boot are
preserved in /var/log/dmesg until the next reboot.

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Alexander Bartha]

Hello to everybody at linuxwireless

Since the "Submodule" ath comes aht9k says in messages:

May  7 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channel
May  7 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) on reg 0x9860: 0x0
0049d19 & 0x00000001 != 0x00000000
May  7 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset channel (2422 Mhz) res
et status 4294967291
May  7 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channel
May  7 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) on reg 0x9860: 0x0
0049d19 & 0x00000001 != 0x00000000

i have tried different versions of the modules but since compat-wireless-2009-04-16 i get this errors.

till that all works fine sometime the driver have little problems after not using the network. thanks for the drivers

well evening from vienna

Alexander Bartha
-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss f?r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Pavel Roskin]

On Fri, 2009-05-08 at 23:12 +0200, Alexander Bartha wrote:
> Hello to everybody at linuxwireless
> 
> Since the "Submodule" ath comes aht9k says in messages:
> 
> May  7 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channel
> May  7 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) on reg 0x9860: 0x0
> 0049d19 & 0x00000001 != 0x00000000
> May  7 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset channel (2422 Mhz) res
> et status 4294967291
> May  7 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channel
> May  7 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) on reg 0x9860: 0x0
> 0049d19 & 0x00000001 != 0x00000000
> 
> i have tried different versions of the modules but since compat-wireless-2009-04-16 i get this errors.
> 
> till that all works fine sometime the driver have little problems after not using the network. thanks for the drivers

I track wireless-testing.git and I saw it in the last weeks.  I think it
happens after about 260 pings at the normal speed (i.e. not with flood
ping).  I was thinking about bisecting the problem, but I don't have
much time right now.

Last time I saw it was on Monday.  There were some changes to ath9k
since then, so maybe it's fixed.

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Fri, May 8, 2009 at 2:40 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Fri, 2009-05-08 at 23:12 +0200, Alexander Bartha wrote:
>> Hello to everybody at linuxwireless
>>
>> Since the "Submodule" ath comes aht9k says in messages:
>>
>> May ?7 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channel
>> May ?7 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) on reg 0x9860: 0x0
>> 0049d19 & 0x00000001 != 0x00000000
>> May ?7 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset channel (2422 Mhz) res
>> et status 4294967291
>> May ?7 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channel
>> May ?7 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) on reg 0x9860: 0x0
>> 0049d19 & 0x00000001 != 0x00000000
>>
>> i have tried different versions of the modules but since compat-wireless-2009-04-16 i get this errors.
>>
>> till that all works fine sometime the driver have little problems after not using the network. thanks for the drivers
>
> I track wireless-testing.git and I saw it in the last weeks. ?I think it
> happens after about 260 pings at the normal speed (i.e. not with flood
> ping). ?I was thinking about bisecting the problem, but I don't have
> much time right now.
>
> Last time I saw it was on Monday. ?There were some changes to ath9k
> since then, so maybe it's fixed.

This may have been caused by the idle patches for which Johannes has
posted a fix. This should get merged soon so give it a few more days
and try again.

If you want something a little more stable you can go with the stable
compat-wireless releases:

http://wireless.kernel.org/en/users/Download/stable

  Luis

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Fri, May 8, 2009 at 2:53 PM, Luis R. Rodriguez <mcgrof@gmail.com> wr=
ote:
> On Fri, May 8, 2009 at 2:40 PM, Pavel Roskin <proski@gnu.org> wrote:
>> On Fri, 2009-05-08 at 23:12 +0200, Alexander Bartha wrote:
>>> Hello to everybody at linuxwireless
>>>
>>> Since the "Submodule" ath comes aht9k says in messages:
>>>
>>> May =C2=A07 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channe=
l
>>> May =C2=A07 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) =
on reg 0x9860: 0x0
>>> 0049d19 & 0x00000001 !=3D 0x00000000
>>> May =C2=A07 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset chan=
nel (2422 Mhz) res
>>> et status 4294967291
>>> May =C2=A07 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channe=
l
>>> May =C2=A07 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) =
on reg 0x9860: 0x0
>>> 0049d19 & 0x00000001 !=3D 0x00000000

I can reproduce, and I tried without the idle patches but I still see
the issue. I see this issue only after suspend. Did you suspend and
get this as well? I see this using AR5416. If you are seeing this on
suspend can you try with the patch I posted to linux-wireless to see
if it helps a little?

  Luis

>>> i have tried different versions of the modules but since compat-wir=
eless-2009-04-16 i get this errors.
>>>
>>> till that all works fine sometime the driver have little problems a=
fter not using the network. thanks for the drivers
>>
>> I track wireless-testing.git and I saw it in the last weeks. =C2=A0I=
 think it
>> happens after about 260 pings at the normal speed (i.e. not with flo=
od
>> ping). =C2=A0I was thinking about bisecting the problem, but I don't=
 have
>> much time right now.
>>
>> Last time I saw it was on Monday. =C2=A0There were some changes to a=
th9k
>> since then, so maybe it's fixed.
>
> This may have been caused by the idle patches for which Johannes has
> posted a fix. This should get merged soon so give it a few more days
> and try again.
>
> If you want something a little more stable you can go with the stable
> compat-wireless releases:
>
> http://wireless.kernel.org/en/users/Download/stable
>
> =C2=A0Luis
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Fri, May 8, 2009 at 2:53 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Fri, May 8, 2009 at 2:40 PM, Pavel Roskin <proski@gnu.org> wrote:
>> On Fri, 2009-05-08 at 23:12 +0200, Alexander Bartha wrote:
>>> Hello to everybody at linuxwireless
>>>
>>> Since the "Submodule" ath comes aht9k says in messages:
>>>
>>> May ?7 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channel
>>> May ?7 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) on reg 0x9860: 0x0
>>> 0049d19 & 0x00000001 != 0x00000000
>>> May ?7 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset channel (2422 Mhz) res
>>> et status 4294967291
>>> May ?7 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channel
>>> May ?7 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) on reg 0x9860: 0x0
>>> 0049d19 & 0x00000001 != 0x00000000

I can reproduce, and I tried without the idle patches but I still see
the issue. I see this issue only after suspend. Did you suspend and
get this as well? I see this using AR5416. If you are seeing this on
suspend can you try with the patch I posted to linux-wireless to see
if it helps a little?

  Luis

>>> i have tried different versions of the modules but since compat-wireless-2009-04-16 i get this errors.
>>>
>>> till that all works fine sometime the driver have little problems after not using the network. thanks for the drivers
>>
>> I track wireless-testing.git and I saw it in the last weeks. ?I think it
>> happens after about 260 pings at the normal speed (i.e. not with flood
>> ping). ?I was thinking about bisecting the problem, but I don't have
>> much time right now.
>>
>> Last time I saw it was on Monday. ?There were some changes to ath9k
>> since then, so maybe it's fixed.
>
> This may have been caused by the idle patches for which Johannes has
> posted a fix. This should get merged soon so give it a few more days
> and try again.
>
> If you want something a little more stable you can go with the stable
> compat-wireless releases:
>
> http://wireless.kernel.org/en/users/Download/stable
>
> ?Luis
>

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Pavel Roskin]

Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:

> I can reproduce, and I tried without the idle patches but I still see
> the issue. I see this issue only after suspend. Did you suspend and
> get this as well? I see this using AR5416. If you are seeing this on
> suspend can you try with the patch I posted to linux-wireless to see
> if it helps a little?

I saw this on AR9280 without any suspends.  The card doesn't support  
the 802.11a range, so it's not a direct equivalent of the problem I  
bisected with ath5k (invalid rates when scanning and transmitting).

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Pavel Roskin]

Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:

> I can reproduce, and I tried without the idle patches but I still see
> the issue. I see this issue only after suspend. Did you suspend and
> get this as well? I see this using AR5416. If you are seeing this on
> suspend can you try with the patch I posted to linux-wireless to see
> if it helps a little?

I saw this on AR9280 without any suspends.  The card doesn't support  
the 802.11a range, so it's not a direct equivalent of the problem I  
bisected with ath5k (invalid rates when scanning and transmitting).

-- 
Regards,
Pavel Roskin

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote:
> Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>
>> I can reproduce, and I tried without the idle patches but I still se=
e
>> the issue. I see this issue only after suspend. Did you suspend and
>> get this as well? I see this using AR5416. If you are seeing this on
>> suspend can you try with the patch I posted to linux-wireless to see
>> if it helps a little?
>
> I saw this on AR9280 without any suspends. =C2=A0The card doesn't sup=
port the
> 802.11a range, so it's not a direct equivalent of the problem I bisec=
ted
> with ath5k (invalid rates when scanning and transmitting).

Thanks for the heads up Pavel. So can you guys test with this option
set as follows:

CONFIG_MAC80211_DEFAULT_PS_VALUE=3D0

If using compat-wireless just stuff it into config.mk.

This fixes my issues and points towards PS code. This could be how we
handle PS in ath9k (more likely) or mac80211. For now please disable
this if using ath9k until we figure out what causes this.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote:
> Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>
>> I can reproduce, and I tried without the idle patches but I still see
>> the issue. I see this issue only after suspend. Did you suspend and
>> get this as well? I see this using AR5416. If you are seeing this on
>> suspend can you try with the patch I posted to linux-wireless to see
>> if it helps a little?
>
> I saw this on AR9280 without any suspends. ?The card doesn't support the
> 802.11a range, so it's not a direct equivalent of the problem I bisected
> with ath5k (invalid rates when scanning and transmitting).

Thanks for the heads up Pavel. So can you guys test with this option
set as follows:

CONFIG_MAC80211_DEFAULT_PS_VALUE=0

If using compat-wireless just stuff it into config.mk.

This fixes my issues and points towards PS code. This could be how we
handle PS in ath9k (more likely) or mac80211. For now please disable
this if using ath9k until we figure out what causes this.

  Luis

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Pavel Roskin]

On Mon, 2009-05-11 at 00:40 -0700, Luis R. Rodriguez wrote:
> On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote:
> > Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
> >
> >> I can reproduce, and I tried without the idle patches but I still see
> >> the issue. I see this issue only after suspend. Did you suspend and
> >> get this as well? I see this using AR5416. If you are seeing this on
> >> suspend can you try with the patch I posted to linux-wireless to see
> >> if it helps a little?
> >
> > I saw this on AR9280 without any suspends.  The card doesn't support the
> > 802.11a range, so it's not a direct equivalent of the problem I bisected
> > with ath5k (invalid rates when scanning and transmitting).
> 
> Thanks for the heads up Pavel. So can you guys test with this option
> set as follows:
> 
> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
> 
> If using compat-wireless just stuff it into config.mk.
> 
> This fixes my issues and points towards PS code. This could be how we
> handle PS in ath9k (more likely) or mac80211. For now please disable
> this if using ath9k until we figure out what causes this.

It looks like there are two issues, and I confused them.  One is
characterized by the kernel messages about the channel, the one
originally reported in this thread.  I have seen it, but I don't
remember the exact circumstances.

Another issue is connection loss to a WPA enabled AP after several
minutes.  That's what I have seen with AR9280.  iwconfig still shows an
association, but no traffic can flow.

I just want to tell that it's two different issues.  The later is much
more critical for me, but it would take about 15 minutes to verify every
step if bisecting.  Unfortunately, I don't have time to bisect it now,
but maybe I'll do it later during this week.

-- 
Regards,
Pavel Roskin

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Pavel Roskin]

On Mon, 2009-05-11 at 00:40 -0700, Luis R. Rodriguez wrote:
> On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote:
> > Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
> >
> >> I can reproduce, and I tried without the idle patches but I still see
> >> the issue. I see this issue only after suspend. Did you suspend and
> >> get this as well? I see this using AR5416. If you are seeing this on
> >> suspend can you try with the patch I posted to linux-wireless to see
> >> if it helps a little?
> >
> > I saw this on AR9280 without any suspends.  The card doesn't support the
> > 802.11a range, so it's not a direct equivalent of the problem I bisected
> > with ath5k (invalid rates when scanning and transmitting).
> 
> Thanks for the heads up Pavel. So can you guys test with this option
> set as follows:
> 
> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
> 
> If using compat-wireless just stuff it into config.mk.
> 
> This fixes my issues and points towards PS code. This could be how we
> handle PS in ath9k (more likely) or mac80211. For now please disable
> this if using ath9k until we figure out what causes this.

It looks like there are two issues, and I confused them.  One is
characterized by the kernel messages about the channel, the one
originally reported in this thread.  I have seen it, but I don't
remember the exact circumstances.

Another issue is connection loss to a WPA enabled AP after several
minutes.  That's what I have seen with AR9280.  iwconfig still shows an
association, but no traffic can flow.

I just want to tell that it's two different issues.  The later is much
more critical for me, but it would take about 15 minutes to verify every
step if bisecting.  Unfortunately, I don't have time to bisect it now,
but maybe I'll do it later during this week.

-- 
Regards,
Pavel Roskin

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Mon, May 11, 2009 at 3:06 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Mon, 2009-05-11 at 00:40 -0700, Luis R. Rodriguez wrote:
>> On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote=
:
>> > Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>> >
>> >> I can reproduce, and I tried without the idle patches but I still=
 see
>> >> the issue. I see this issue only after suspend. Did you suspend a=
nd
>> >> get this as well? I see this using AR5416. If you are seeing this=
 on
>> >> suspend can you try with the patch I posted to linux-wireless to =
see
>> >> if it helps a little?
>> >
>> > I saw this on AR9280 without any suspends. =C2=A0The card doesn't =
support the
>> > 802.11a range, so it's not a direct equivalent of the problem I bi=
sected
>> > with ath5k (invalid rates when scanning and transmitting).
>>
>> Thanks for the heads up Pavel. So can you guys test with this option
>> set as follows:
>>
>> CONFIG_MAC80211_DEFAULT_PS_VALUE=3D0
>>
>> If using compat-wireless just stuff it into config.mk.
>>
>> This fixes my issues and points towards PS code. This could be how w=
e
>> handle PS in ath9k (more likely) or mac80211. For now please disable
>> this if using ath9k until we figure out what causes this.
>
> It looks like there are two issues, and I confused them. =C2=A0One is
> characterized by the kernel messages about the channel, the one
> originally reported in this thread. =C2=A0I have seen it, but I don't
> remember the exact circumstances.
>
> Another issue is connection loss to a WPA enabled AP after several
> minutes. =C2=A0That's what I have seen with AR9280. =C2=A0iwconfig st=
ill shows an
> association, but no traffic can flow.
>
> I just want to tell that it's two different issues. =C2=A0The later i=
s much
> more critical for me, but it would take about 15 minutes to verify ev=
ery
> step if bisecting. =C2=A0Unfortunately, I don't have time to bisect i=
t now,
> but maybe I'll do it later during this week.

Thanks for the heads up, lets address this in another thread then.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Mon, May 11, 2009 at 3:06 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Mon, 2009-05-11 at 00:40 -0700, Luis R. Rodriguez wrote:
>> On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@gnu.org> wrote:
>> > Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>> >
>> >> I can reproduce, and I tried without the idle patches but I still see
>> >> the issue. I see this issue only after suspend. Did you suspend and
>> >> get this as well? I see this using AR5416. If you are seeing this on
>> >> suspend can you try with the patch I posted to linux-wireless to see
>> >> if it helps a little?
>> >
>> > I saw this on AR9280 without any suspends. ?The card doesn't support the
>> > 802.11a range, so it's not a direct equivalent of the problem I bisected
>> > with ath5k (invalid rates when scanning and transmitting).
>>
>> Thanks for the heads up Pavel. So can you guys test with this option
>> set as follows:
>>
>> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
>>
>> If using compat-wireless just stuff it into config.mk.
>>
>> This fixes my issues and points towards PS code. This could be how we
>> handle PS in ath9k (more likely) or mac80211. For now please disable
>> this if using ath9k until we figure out what causes this.
>
> It looks like there are two issues, and I confused them. ?One is
> characterized by the kernel messages about the channel, the one
> originally reported in this thread. ?I have seen it, but I don't
> remember the exact circumstances.
>
> Another issue is connection loss to a WPA enabled AP after several
> minutes. ?That's what I have seen with AR9280. ?iwconfig still shows an
> association, but no traffic can flow.
>
> I just want to tell that it's two different issues. ?The later is much
> more critical for me, but it would take about 15 minutes to verify every
> step if bisecting. ?Unfortunately, I don't have time to bisect it now,
> but maybe I'll do it later during this week.

Thanks for the heads up, lets address this in another thread then.

  Luis

[ath9k-devel] Antwort: Re: ath9k module-Unable to set channel-since ath comes

[alexander.bartha at drz-wien.at]

Hello to linuxwireless

thanks for response. The stabel compat-wireless-2.6.30-rc4.tar.bz2 release 
works well. The bleeding edge compat-wireless works to but only till the 
new submodule ath comes in live (compat-wireless-2009-04-12.tar.bz2 is the 
last version which i have tasted and which works well).

well day from vienna

Alexander Bartha
Abteilungsleiter NOC (EDV) und OnlineVerkauf
Tel.: +43 1 982 16 48 304
Fax: +43 1 982 16 48 18
E-Mail: alexander.bartha at drz-wien.at

Die Wiener Volkshochschulen GmbH
Projekt DRZ-Wien
Vogtgasse 29
1140 Wien
UID - ATU 63945413



"Luis R. Rodriguez" <mcgrof@gmail.com> 
10.05.2009 20:41

An
Pavel Roskin <proski@gnu.org>
Kopie
Alexander Bartha <alex.xy.privat@gmx.at>, ath9k-devel at lists.ath9k.org, 
linux-wireless <linux-wireless@vger.kernel.org>
Thema
Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes 






On Fri, May 8, 2009 at 2:53 PM, Luis R. Rodriguez <mcgrof@gmail.com> 
wrote:
> On Fri, May 8, 2009 at 2:40 PM, Pavel Roskin <proski@gnu.org> wrote:
>> On Fri, 2009-05-08 at 23:12 +0200, Alexander Bartha wrote:
>>> Hello to everybody at linuxwireless
>>>
>>> Since the "Submodule" ath comes aht9k says in messages:
>>>
>>> May  7 22:11:34 ws1 [ 4442.304763] ath9k: Unable to set channel
>>> May  7 22:11:34 ws1 [ 4442.425550] ath9k: timeout (100000 us) on reg 
0x9860: 0x0
>>> 0049d19 & 0x00000001 != 0x00000000
>>> May  7 22:11:34 ws1 [ 4442.425555] ath9k: Unable to reset channel 
(2422 Mhz) res
>>> et status 4294967291
>>> May  7 22:11:34 ws1 [ 4442.425560] ath9k: Unable to set channel
>>> May  7 22:11:34 ws1 [ 4442.546365] ath9k: timeout (100000 us) on reg 
0x9860: 0x0
>>> 0049d19 & 0x00000001 != 0x00000000

I can reproduce, and I tried without the idle patches but I still see
the issue. I see this issue only after suspend. Did you suspend and
get this as well? I see this using AR5416. If you are seeing this on
suspend can you try with the patch I posted to linux-wireless to see
if it helps a little?

  Luis

>>> i have tried different versions of the modules but since 
compat-wireless-2009-04-16 i get this errors.
>>>
>>> till that all works fine sometime the driver have little problems 
after not using the network. thanks for the drivers
>>
>> I track wireless-testing.git and I saw it in the last weeks.  I think 
it
>> happens after about 260 pings at the normal speed (i.e. not with flood
>> ping).  I was thinking about bisecting the problem, but I don't have
>> much time right now.
>>
>> Last time I saw it was on Monday.  There were some changes to ath9k
>> since then, so maybe it's fixed.
>
> This may have been caused by the idle patches for which Johannes has
> posted a fix. This should get merged soon so give it a few more days
> and try again.
>
> If you want something a little more stable you can go with the stable
> compat-wireless releases:
>
> http://wireless.kernel.org/en/users/Download/stable
>
>  Luis
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090512/59a16be9/attachment.htm 

Re: Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Mon, May 11, 2009 at 11:38 PM,  <alexander.bartha@drz-wien.at> wrote:
>
> Hello to linuxwireless
>
> thanks for response. The stabel compat-wireless-2.6.30-rc4.tar.bz2 release
> works well. The bleeding edge compat-wireless works to but only till the new
> submodule ath comes in live (compat-wireless-2009-04-12.tar.bz2 is the last
> version which i have tasted and which works well).

I've tested this and its not the "ath" module which introduces an
issue its a patch which enables PS by default. You can disable that by
recompiling with:

CONFIG_MAC80211_DEFAULT_PS_VALUE=0

If using compat-wireless just stuff it into config.mk.

  Luis

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Mon, May 11, 2009 at 11:38 PM,  <alexander.bartha@drz-wien.at> wrote:
>
> Hello to linuxwireless
>
> thanks for response. The stabel compat-wireless-2.6.30-rc4.tar.bz2 release
> works well. The bleeding edge compat-wireless works to but only till the new
> submodule ath comes in live (compat-wireless-2009-04-12.tar.bz2 is the last
> version which i have tasted and which works well).

I've tested this and its not the "ath" module which introduces an
issue its a patch which enables PS by default. You can disable that by
recompiling with:

CONFIG_MAC80211_DEFAULT_PS_VALUE=0

If using compat-wireless just stuff it into config.mk.

  Luis

Re: Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:

> I've tested this and its not the "ath" module which introduces an
> issue its a patch which enables PS by default. You can disable that by
> recompiling with:
> 
> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
> 
> If using compat-wireless just stuff it into config.mk.

I object to that assertion, or at least this way of putting it.

If powersave by default causes issues then it's not my patch that's
causing the problem, it's the fact that ath9k can't properly deal with
powersave in this case. Had the user enabled powersave manually they
would have run into the same issue. As such, I think ath9k should
probably simply stop claiming it can support PS.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Johannes Berg]

On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:

> I've tested this and its not the "ath" module which introduces an
> issue its a patch which enables PS by default. You can disable that by
> recompiling with:
> 
> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
> 
> If using compat-wireless just stuff it into config.mk.

I object to that assertion, or at least this way of putting it.

If powersave by default causes issues then it's not my patch that's
causing the problem, it's the fact that ath9k can't properly deal with
powersave in this case. Had the user enabled powersave manually they
would have run into the same issue. As such, I think ath9k should
probably simply stop claiming it can support PS.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090512/8d34fde5/attachment.pgp 

Re: Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Tue, May 12, 2009 at 12:11 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:
>
>> I've tested this and its not the "ath" module which introduces an
>> issue its a patch which enables PS by default. You can disable that by
>> recompiling with:
>>
>> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
>>
>> If using compat-wireless just stuff it into config.mk.
>
> I object to that assertion, or at least this way of putting it.
>
> If powersave by default causes issues then it's not my patch that's
> causing the problem, it's the fact that ath9k can't properly deal with
> powersave in this case. Had the user enabled powersave manually they
> would have run into the same issue. As such, I think ath9k should
> probably simply stop claiming it can support PS.

Heh yes, what I meant was ath9k's PS support has some issues which
still need to be resolved (at least as I've tested it).

  Luis

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Luis R. Rodriguez]

On Tue, May 12, 2009 at 12:11 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:
>
>> I've tested this and its not the "ath" module which introduces an
>> issue its a patch which enables PS by default. You can disable that by
>> recompiling with:
>>
>> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
>>
>> If using compat-wireless just stuff it into config.mk.
>
> I object to that assertion, or at least this way of putting it.
>
> If powersave by default causes issues then it's not my patch that's
> causing the problem, it's the fact that ath9k can't properly deal with
> powersave in this case. Had the user enabled powersave manually they
> would have run into the same issue. As such, I think ath9k should
> probably simply stop claiming it can support PS.

Heh yes, what I meant was ath9k's PS support has some issues which
still need to be resolved (at least as I've tested it).

  Luis

Re: Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Davide Pesavento]

Hi,

On Tue, May 12, 2009 at 09:14, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Tue, May 12, 2009 at 12:11 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:
>>
>>> I've tested this and its not the "ath" module which introduces an
>>> issue its a patch which enables PS by default. You can disable that by
>>> recompiling with:
>>>
>>> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
>>>
>>> If using compat-wireless just stuff it into config.mk.
>>
>> I object to that assertion, or at least this way of putting it.
>>
>> If powersave by default causes issues then it's not my patch that's
>> causing the problem, it's the fact that ath9k can't properly deal with
>> powersave in this case. Had the user enabled powersave manually they
>> would have run into the same issue. As such, I think ath9k should
>> probably simply stop claiming it can support PS.
>
> Heh yes, what I meant was ath9k's PS support has some issues which
> still need to be resolved (at least as I've tested it).
>

I've already reported ath9k's issues with PS multiple times [1] [2]
[3], but the driver hasn't been fixed yet. You can find a verbose
debugging output at [4], I hope that helps in fixing the problem (I
can provide even more info if needed and I'm willing to test patches).

Anyway, if the issue isn't going to be resolved quickly (e.g. before
Johannes' "enable PS by default" patch lands in mainline), I think
it's better to disable PS in ath9k as previously suggested.

Regards,
Davide

[1] http://marc.info/?l=linux-wireless&m=123816406913599&w=2
[2] http://marc.info/?l=linux-wireless&m=123999864507104&w=2
[3] http://marc.info/?l=linux-wireless&m=124025926613089&w=2
[4] http://marc.info/?l=linux-wireless&m=124026772102023&w=2

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Davide Pesavento]

Hi,

On Tue, May 12, 2009 at 09:14, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Tue, May 12, 2009 at 12:11 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> On Mon, 2009-05-11 at 23:55 -0700, Luis R. Rodriguez wrote:
>>
>>> I've tested this and its not the "ath" module which introduces an
>>> issue its a patch which enables PS by default. You can disable that by
>>> recompiling with:
>>>
>>> CONFIG_MAC80211_DEFAULT_PS_VALUE=0
>>>
>>> If using compat-wireless just stuff it into config.mk.
>>
>> I object to that assertion, or at least this way of putting it.
>>
>> If powersave by default causes issues then it's not my patch that's
>> causing the problem, it's the fact that ath9k can't properly deal with
>> powersave in this case. Had the user enabled powersave manually they
>> would have run into the same issue. As such, I think ath9k should
>> probably simply stop claiming it can support PS.
>
> Heh yes, what I meant was ath9k's PS support has some issues which
> still need to be resolved (at least as I've tested it).
>

I've already reported ath9k's issues with PS multiple times [1] [2]
[3], but the driver hasn't been fixed yet. You can find a verbose
debugging output at [4], I hope that helps in fixing the problem (I
can provide even more info if needed and I'm willing to test patches).

Anyway, if the issue isn't going to be resolved quickly (e.g. before
Johannes' "enable PS by default" patch lands in mainline), I think
it's better to disable PS in ath9k as previously suggested.

Regards,
Davide

[1] http://marc.info/?l=linux-wireless&m=123816406913599&w=2
[2] http://marc.info/?l=linux-wireless&m=123999864507104&w=2
[3] http://marc.info/?l=linux-wireless&m=124025926613089&w=2
[4] http://marc.info/?l=linux-wireless&m=124026772102023&w=2

[ath9k-devel] Where can I buy a wifi card supported by ath9k?

[hong zhang]

List,

I like to buy a wifi card supported by ath9k but do not know which card on market is good one.

Thanks for any help.

---henry


      

[ath9k-devel] Where can I buy a wifi card supported by ath9k?

[Luis R. Rodriguez]

On Tue, May 12, 2009 at 9:28 AM, hong zhang <henryzhang62@yahoo.com> wrote:
>
>
> List,
>
> I like to buy a wifi card supported by ath9k but do not know which card on market is good one.

http://wireless.kernel.org/en/users/Drivers/ath9k#ProductsintheretailmarketcontainingAtheros11nsolutions

  Luis

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Jouni Malinen]

On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
> I've already reported ath9k's issues with PS multiple times [1] [2]
> [3], but the driver hasn't been fixed yet. You can find a verbose
> debugging output at [4], I hope that helps in fixing the problem (I
> can provide even more info if needed and I'm willing to test patches).

I submitted a set of patches to resolve some of the PS issues in ath9k.
I would expect these to hit wireless-testing.git eventually, but if you
are willing to test the changes before that, you can find the patches
from http://w1.fi/p/ps/

One thing to note here is that there are still some issues with the
timeout=0 case (use of PS-Poll to fetch buffered frames) which is
enabled with "iwconfig wlan0 power on", so at this point, I would
recommend running the test either with the default wireless-testing.git
PS mode setting or by enabling power saving with "iwconfig wlan0 power
timeout 500ms" which should result in the same configuration.

I have not tested these on AR5418, but at least with AR9280, these
patches do improve stability and general functionality of the default PS
mode considerably. I have been able to run multi-hour tests without
losing connection.

- Jouni

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Jouni Malinen]

On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
> I've already reported ath9k's issues with PS multiple times [1] [2]
> [3], but the driver hasn't been fixed yet. You can find a verbose
> debugging output at [4], I hope that helps in fixing the problem (I
> can provide even more info if needed and I'm willing to test patches).

I submitted a set of patches to resolve some of the PS issues in ath9k.
I would expect these to hit wireless-testing.git eventually, but if you
are willing to test the changes before that, you can find the patches
from http://w1.fi/p/ps/

One thing to note here is that there are still some issues with the
timeout=0 case (use of PS-Poll to fetch buffered frames) which is
enabled with "iwconfig wlan0 power on", so at this point, I would
recommend running the test either with the default wireless-testing.git
PS mode setting or by enabling power saving with "iwconfig wlan0 power
timeout 500ms" which should result in the same configuration.

I have not tested these on AR5418, but at least with AR9280, these
patches do improve stability and general functionality of the default PS
mode considerably. I have been able to run multi-hour tests without
losing connection.

- Jouni

Re: [ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Kalle Valo]

Jouni Malinen <jouni.malinen@atheros.com> writes:

> On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
>> I've already reported ath9k's issues with PS multiple times [1] [2]
>> [3], but the driver hasn't been fixed yet. You can find a verbose
>> debugging output at [4], I hope that helps in fixing the problem (I
>> can provide even more info if needed and I'm willing to test patches).
>
> I submitted a set of patches to resolve some of the PS issues in ath9k.
> I would expect these to hit wireless-testing.git eventually, but if you
> are willing to test the changes before that, you can find the patches
> from http://w1.fi/p/ps/
>
> One thing to note here is that there are still some issues with the
> timeout=0 case (use of PS-Poll to fetch buffered frames) which is
> enabled with "iwconfig wlan0 power on", so at this point, I would
> recommend running the test either with the default wireless-testing.git
> PS mode setting or by enabling power saving with "iwconfig wlan0 power
> timeout 500ms" which should result in the same configuration.

Most probably that's because mac80211 does not disable power save mode
when sending PS-Poll frames. So stlc45xx does not require disable of PSM
but then again ath9k requires it, we need to solve this somehow.

I have been thinking about separating power save mode and firmware
wakeup/sleep modes from each other in mac80211 API. To me it looks like
ath9k does more like firmware wakeup/sleep when power save mode is
changing. But this is just a wild idea, I have no idea if it's practical
or not.

-- 
Kalle Valo

[ath9k-devel] ath9k module-Unable to set channel-since ath comes

[Kalle Valo]

Jouni Malinen <jouni.malinen@atheros.com> writes:

> On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
>> I've already reported ath9k's issues with PS multiple times [1] [2]
>> [3], but the driver hasn't been fixed yet. You can find a verbose
>> debugging output at [4], I hope that helps in fixing the problem (I
>> can provide even more info if needed and I'm willing to test patches).
>
> I submitted a set of patches to resolve some of the PS issues in ath9k.
> I would expect these to hit wireless-testing.git eventually, but if you
> are willing to test the changes before that, you can find the patches
> from http://w1.fi/p/ps/
>
> One thing to note here is that there are still some issues with the
> timeout=0 case (use of PS-Poll to fetch buffered frames) which is
> enabled with "iwconfig wlan0 power on", so at this point, I would
> recommend running the test either with the default wireless-testing.git
> PS mode setting or by enabling power saving with "iwconfig wlan0 power
> timeout 500ms" which should result in the same configuration.

Most probably that's because mac80211 does not disable power save mode
when sending PS-Poll frames. So stlc45xx does not require disable of PSM
but then again ath9k requires it, we need to solve this somehow.

I have been thinking about separating power save mode and firmware
wakeup/sleep modes from each other in mac80211 API. To me it looks like
ath9k does more like firmware wakeup/sleep when power save mode is
changing. But this is just a wild idea, I have no idea if it's practical
or not.

-- 
Kalle Valo

[ath9k-devel] Antwort: Re: ath9k module-Unable to set channel-since ath comes

[alexander.bartha at drz-wien.at]

Hello to Linuxwireless

at the last weekend i tried again with compat-wireless-2009-15-05 and i 
have disabled the PS (this value "CONFIG_MAC80211_DEFAULT_PS_VALUE=0" and 
"CONFIG_MAC80211_DEFAULT_PS=n") in config.mk but nothing changed.
After 2 or 3 minutes i sawed again the "unable to set channel" in 
/var/log/messages.

Well day from vienna

Alexander Bartha
Abteilungsleiter NOC (EDV) und OnlineVerkauf
Tel.: +43 1 982 16 48 304
Fax: +43 1 982 16 48 18
E-Mail: alexander.bartha at drz-wien.at

Die Wiener Volkshochschulen GmbH
Projekt DRZ-Wien
Vogtgasse 29
1140 Wien
UID - ATU 63945413
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090519/6ecba248/attachment.htm 

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

Hello to ath9k developers

i am using:

Distribution: gentoo
Kernel: 2.6.28-r1
Linux-Headers: 2.6.28-r1
Wireless Card: Linksys WMP300n v2 European
Router: Linksys WRT160n


i have tested wmp300nv2 European Version without any luck. I have tried to compile the kernel in that way you told on the the web site(ath9k howto).
At your howto is Networking  --->
  Wireless  --->
    <M> Improved wireless configuration API
    <M> Generic IEEE 802.11 Networking Stack (mac80211) both as Module
when i tried both as module i cant load mac80211 or cfg80211 so ath9k fails also. 
One time i get it to work (with kernel 2.6.27-r7) (cfg80211 and mac80211 directly in the kernel not as module) but with only 8MB/sec Bandwith and channel 12 and 13 was not able to access. I need channel 12 or 13 cause in the neibourhood are much wireless routers and none of this routers uses channel 12 or 13 so at these channels i get the stablest and speedest network.
Please can you help me with a working kernel config an tell me which packeges i have to install that my linksys wmp300nv2 card could work at 80211N 130MB/sec with support for all channel inkluding channel 12 and 13. 
Sorry for these ugly english. Sorry for these mail but i tried many times to build my kernel without any luck on the linksys card. I have attached my kernel config.
Thanks for helping.
-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-2.6.28-r1-6
Type: application/octet-stream
Size: 58194 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090124/e76cb864/attachment-0001.obj 

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Sujith]

Alexander Bartha wrote:
> Hello to ath9k developers
> 
> i am using:
> 
> Distribution: gentoo
> Kernel: 2.6.28-r1
> Linux-Headers: 2.6.28-r1
> Wireless Card: Linksys WMP300n v2 European
> Router: Linksys WRT160n

The easiest way is to just use compat-wireless.
See: http://wireless.kernel.org/en/users/Download

Sujith
-- 
http://sujith-m.blogspot.com

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Alexander Bartha]

-------- Original-Nachricht --------
> Datum: Sun, 25 Jan 2009 22:42:56 +0530
> Von: Sujith <m.sujith@gmail.com>
> An: "Alexander Bartha" <alexander.bartha.office.rusz@gmx.at>
> CC: ath9k-devel at lists.ath9k.org
> Betreff: [ath9k-devel] ath9k WMP300nv2 (AR5416)

> Alexander Bartha wrote:
> > Hello to ath9k developers
> > 
> > i am using:
> > 
> > Distribution: gentoo
> > Kernel: 2.6.28-r1
> > Linux-Headers: 2.6.28-r1
> > Wireless Card: Linksys WMP300n v2 European
> > Router: Linksys WRT160n
> 
> The easiest way is to just use compat-wireless.
> See: http://wireless.kernel.org/en/users/Download
> 
> Sujith
> -- 
> http://sujith-m.blogspot.com
After building my kernel with cfg80211 and mac80211 as modules it was posible to install the compat-wirless drivers. And for the first time the worked! ifconfig tells me that my bandwith is only 1MBS and the ip i get from my LinksysWRT160 is renewed every 6Minutes. Later in the evening i make package updates (crda 0.9.5 to 1.0.1) my linksysWMP300nv2 card wont worke. The last message i get was link is not ready.
/var/log/messages before update:
an 27 15:01:53 ws1 [  152.020563] cfg80211: Using static regulatory domain info
Jan 27 15:01:53 ws1 [  152.020568] cfg80211: Regulatory domain: US
Jan 27 15:01:53 ws1 [  152.020570] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 15:01:53 ws1 [  152.020575] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
Jan 27 15:01:53 ws1 [  152.020578] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 27 15:01:53 ws1 [  152.020581] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 27 15:01:53 ws1 [  152.020585] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 27 15:01:53 ws1 [  152.020588] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 27 15:01:53 ws1 [  152.020592] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
Jan 27 15:01:53 ws1 [  152.020595] cfg80211: Calling CRDA for country: US
Jan 27 15:01:53 ws1 [  152.040083] ath9k: 0.1
Jan 27 15:01:53 ws1 [  152.040164] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Jan 27 15:01:53 ws1 [  152.102946] cfg80211: Regulatory domain changed to country: US
Jan 27 15:01:53 ws1 [  152.102951] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 15:01:53 ws1 [  152.102956] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Jan 27 15:01:53 ws1 [  152.102959] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Jan 27 15:01:53 ws1 [  152.102963] 	(5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 15:01:53 ws1 [  152.102966] 	(5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 15:01:53 ws1 [  152.102969] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Jan 27 15:01:54 ws1 [  152.465925] phy0: Selected rate control algorithm 'ath9k_rate_control'
Jan 27 15:01:54 ws1 [  152.467143] cfg80211: Calling CRDA for country: AT
Jan 27 15:01:54 ws1 [  152.467188] Registered led device: ath9k-phy0:radio
Jan 27 15:01:54 ws1 [  152.467213] Registered led device: ath9k-phy0:assoc
Jan 27 15:01:54 ws1 [  152.467241] Registered led device: ath9k-phy0:tx
Jan 27 15:01:54 ws1 [  152.467266] Registered led device: ath9k-phy0:rx
Jan 27 15:01:54 ws1 [  152.467282] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9be0000, irq=20
Jan 27 15:01:54 ws1 [  152.475534] cfg80211: Regulatory domain changed to country: AT
Jan 27 15:01:54 ws1 [  152.475539] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 15:01:54 ws1 [  152.475543] 	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 15:01:54 ws1 [  152.475547] 	(5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 15:01:54 ws1 [  152.475550] 	(5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 15:01:54 ws1 [  152.475553] 	(5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Jan 27 15:01:55 ws1 [  153.371753] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 27 15:01:56 ws1 [  154.337141] wlan0: authenticate with AP f5da96a8
Jan 27 15:01:56 ws1 [  154.339093] wlan0: authenticated
Jan 27 15:01:56 ws1 [  154.339097] wlan0: associate with AP f5da96a8
Jan 27 15:01:56 ws1 [  154.344295] wlan0: RX AssocResp from f28f202a (capab=0x411 status=0 aid=1)
Jan 27 15:01:56 ws1 [  154.344300] wlan0: associated
Jan 27 15:01:56 ws1 [  154.352968] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 27 15:01:56 ws1 wpa_cli: interface wlan0 CONNECTED
Jan 27 15:01:57 ws1 dhcpcd[8802]: wlan0: dhcpcd 4.0.7 starting
Jan 27 15:01:57 ws1 dhcpcd[8802]: wlan0: broadcasting for a lease
Jan 27 15:01:58 ws1 dhcpcd[8802]: wlan0: offered 192.168.1.100 from 192.168.1.1
Jan 27 15:01:58 ws1 dhcpcd[8802]: wlan0: checking 192.168.1.100 is available on attached networks
Jan 27 15:02:04 ws1 dhcpcd[8802]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
Jan 27 15:02:04 ws1 dhcpcd[8802]: wlan0: leased 192.168.1.100 for 86400 seconds
Jan 27 15:02:06 ws1 [  164.757007] wlan0: no IPv6 routers present


/var/log/messages after crda update:
ws1 [  475.022872] ath9k 0000:04:00.0: PCI INT A disabled
Jan 28 13:11:59 ws1 [  475.022906] ath9k: Driver unloaded
Jan 28 13:12:34 ws1 rc-scripts: WARNING:  net.wlan0 has not yet been started.
Jan 28 13:12:45 ws1 [  520.974197] cfg80211: Using static regulatory domain info
Jan 28 13:12:45 ws1 [  520.974202] cfg80211: Regulatory domain: US
Jan 28 13:12:45 ws1 [  520.974205] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 28 13:12:45 ws1 [  520.974209] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
Jan 28 13:12:45 ws1 [  520.974213] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 28 13:12:45 ws1 [  520.974216] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 28 13:12:45 ws1 [  520.974219] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 28 13:12:45 ws1 [  520.974223] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 28 13:12:45 ws1 [  520.974226] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
Jan 28 13:12:45 ws1 [  520.974230] cfg80211: Calling CRDA for country: US
Jan 28 13:12:45 ws1 [  520.992789] ath9k: 0.1
Jan 28 13:12:45 ws1 [  520.992829] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Jan 28 13:12:46 ws1 [  521.420252] phy0: Selected rate control algorithm 'ath9k_rate_control'
Jan 28 13:12:46 ws1 [  521.421635] cfg80211: Calling CRDA for country: AT
Jan 28 13:12:46 ws1 [  521.421683] Registered led device: ath9k-phy0:radio
Jan 28 13:12:46 ws1 [  521.421708] Registered led device: ath9k-phy0:assoc
Jan 28 13:12:46 ws1 [  521.421732] Registered led device: ath9k-phy0:tx
Jan 28 13:12:46 ws1 [  521.421756] Registered led device: ath9k-phy0:rx
Jan 28 13:12:46 ws1 [  521.421773] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9520000, irq=20
Jan 28 13:12:47 ws1 [  522.336623] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Is the only way to use the old crda???
Please help
kind regards
Alexander Bartha
-- 
NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL 
f?r nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

On Wed, Jan 28, 2009 at 05:17:22AM -0800, Alexander Bartha wrote:
> 
> -------- Original-Nachricht --------
> > Datum: Sun, 25 Jan 2009 22:42:56 +0530
> > Von: Sujith <m.sujith@gmail.com>
> > An: "Alexander Bartha" <alexander.bartha.office.rusz@gmx.at>
> > CC: ath9k-devel at lists.ath9k.org
> > Betreff: [ath9k-devel] ath9k WMP300nv2 (AR5416)
> 
> > Alexander Bartha wrote:
> > > Hello to ath9k developers
> > >
> > > i am using:
> > >
> > > Distribution: gentoo
> > > Kernel: 2.6.28-r1
> > > Linux-Headers: 2.6.28-r1
> > > Wireless Card: Linksys WMP300n v2 European
> > > Router: Linksys WRT160n
> >
> > The easiest way is to just use compat-wireless.
> > See: http://wireless.kernel.org/en/users/Download
> >
> > Sujith
> > --
> > http://sujith-m.blogspot.com
> After building my kernel with cfg80211 and mac80211 as modules it was posible to install the compat-wirless drivers. And for the first time the worked!

Great to hear!

> ifconfig tells me that my bandwith is only 1MBS and 

Do you mean iwconfig? iwconfig does not tell you MCS (HT or 802.11n rates)
and you will see 1 Mbps rate when that is used. To get more accurate MCS rate stats
you now have to use iw:

http://wireless.kernel.org/en/users/Documentation/iw#Gettingstationstatistics

sudo iw dev wlan1 station dump

This is still being worked on by mac80211 drivers, so you won't see the last TX rate yet
but hopefully soon.

> the ip i get from my LinksysWRT160 is renewed every 6Minutes. Later in the evening i make package updates (crda 0.9.5 to 1.0.1) my linksysWMP300nv2 card wont worke. The last message i get was link is not ready.

"link not ready" just means that you haven't associated yet. I know -- this is a bit cryptic,
but in a way its right, and its certainly correct for ethernet.

> /var/log/messages before update:
> an 27 15:01:53 ws1 [  152.020563] cfg80211: Using static regulatory domain info
> Jan 27 15:01:53 ws1 [  152.020568] cfg80211: Regulatory domain: US
> Jan 27 15:01:53 ws1 [  152.020570]      (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jan 27 15:01:53 ws1 [  152.020575]      (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> Jan 27 15:01:53 ws1 [  152.020578]      (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 27 15:01:53 ws1 [  152.020581]      (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 27 15:01:53 ws1 [  152.020585]      (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 27 15:01:53 ws1 [  152.020588]      (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 27 15:01:53 ws1 [  152.020592]      (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> Jan 27 15:01:53 ws1 [  152.020595] cfg80211: Calling CRDA for country: US
> Jan 27 15:01:53 ws1 [  152.040083] ath9k: 0.1
> Jan 27 15:01:53 ws1 [  152.040164] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> Jan 27 15:01:53 ws1 [  152.102946] cfg80211: Regulatory domain changed to country: US
> Jan 27 15:01:53 ws1 [  152.102951]      (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jan 27 15:01:53 ws1 [  152.102956]      (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
> Jan 27 15:01:53 ws1 [  152.102959]      (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
> Jan 27 15:01:53 ws1 [  152.102963]      (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Jan 27 15:01:53 ws1 [  152.102966]      (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Jan 27 15:01:53 ws1 [  152.102969]      (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
> Jan 27 15:01:54 ws1 [  152.465925] phy0: Selected rate control algorithm 'ath9k_rate_control'
> Jan 27 15:01:54 ws1 [  152.467143] cfg80211: Calling CRDA for country: AT
> Jan 27 15:01:54 ws1 [  152.467188] Registered led device: ath9k-phy0:radio
> Jan 27 15:01:54 ws1 [  152.467213] Registered led device: ath9k-phy0:assoc
> Jan 27 15:01:54 ws1 [  152.467241] Registered led device: ath9k-phy0:tx
> Jan 27 15:01:54 ws1 [  152.467266] Registered led device: ath9k-phy0:rx
> Jan 27 15:01:54 ws1 [  152.467282] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9be0000, irq=20
> Jan 27 15:01:54 ws1 [  152.475534] cfg80211: Regulatory domain changed to country: AT
> Jan 27 15:01:54 ws1 [  152.475539]      (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jan 27 15:01:54 ws1 [  152.475543]      (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Jan 27 15:01:54 ws1 [  152.475547]      (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Jan 27 15:01:54 ws1 [  152.475550]      (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Jan 27 15:01:54 ws1 [  152.475553]      (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
> Jan 27 15:01:55 ws1 [  153.371753] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> Jan 27 15:01:56 ws1 [  154.337141] wlan0: authenticate with AP f5da96a8
> Jan 27 15:01:56 ws1 [  154.339093] wlan0: authenticated
> Jan 27 15:01:56 ws1 [  154.339097] wlan0: associate with AP f5da96a8
> Jan 27 15:01:56 ws1 [  154.344295] wlan0: RX AssocResp from f28f202a (capab=0x411 status=0 aid=1)
> Jan 27 15:01:56 ws1 [  154.344300] wlan0: associated
> Jan 27 15:01:56 ws1 [  154.352968] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> Jan 27 15:01:56 ws1 wpa_cli: interface wlan0 CONNECTED
> Jan 27 15:01:57 ws1 dhcpcd[8802]: wlan0: dhcpcd 4.0.7 starting
> Jan 27 15:01:57 ws1 dhcpcd[8802]: wlan0: broadcasting for a lease
> Jan 27 15:01:58 ws1 dhcpcd[8802]: wlan0: offered 192.168.1.100 from 192.168.1.1
> Jan 27 15:01:58 ws1 dhcpcd[8802]: wlan0: checking 192.168.1.100 is available on attached networks
> Jan 27 15:02:04 ws1 dhcpcd[8802]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
> Jan 27 15:02:04 ws1 dhcpcd[8802]: wlan0: leased 192.168.1.100 for 86400 seconds
> Jan 27 15:02:06 ws1 [  164.757007] wlan0: no IPv6 routers present

Looks good.

> /var/log/messages after crda update:
> ws1 [  475.022872] ath9k 0000:04:00.0: PCI INT A disabled
> Jan 28 13:11:59 ws1 [  475.022906] ath9k: Driver unloaded
> Jan 28 13:12:34 ws1 rc-scripts: WARNING:  net.wlan0 has not yet been started.
> Jan 28 13:12:45 ws1 [  520.974197] cfg80211: Using static regulatory domain info
> Jan 28 13:12:45 ws1 [  520.974202] cfg80211: Regulatory domain: US
> Jan 28 13:12:45 ws1 [  520.974205]      (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jan 28 13:12:45 ws1 [  520.974209]      (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> Jan 28 13:12:45 ws1 [  520.974213]      (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 28 13:12:45 ws1 [  520.974216]      (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 28 13:12:45 ws1 [  520.974219]      (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 28 13:12:45 ws1 [  520.974223]      (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Jan 28 13:12:45 ws1 [  520.974226]      (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> Jan 28 13:12:45 ws1 [  520.974230] cfg80211: Calling CRDA for country: US
> Jan 28 13:12:45 ws1 [  520.992789] ath9k: 0.1
> Jan 28 13:12:45 ws1 [  520.992829] ath9k 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> Jan 28 13:12:46 ws1 [  521.420252] phy0: Selected rate control algorithm 'ath9k_rate_control'
> Jan 28 13:12:46 ws1 [  521.421635] cfg80211: Calling CRDA for country: AT
> Jan 28 13:12:46 ws1 [  521.421683] Registered led device: ath9k-phy0:radio
> Jan 28 13:12:46 ws1 [  521.421708] Registered led device: ath9k-phy0:assoc
> Jan 28 13:12:46 ws1 [  521.421732] Registered led device: ath9k-phy0:tx
> Jan 28 13:12:46 ws1 [  521.421756] Registered led device: ath9k-phy0:rx
> Jan 28 13:12:46 ws1 [  521.421773] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf9520000, irq=20
> Jan 28 13:12:47 ws1 [  522.336623] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 
> Is the only way to use the old crda???

Nope, what is happening here is the kernel is not getting the regulatory domain. Please
show me the log of you compiling and installing CRDA (make clean; make; sudo make install).
Then, as per CRDA debugging page [1] you can debug commmunication between the kernel and
crda by running:

sudo udevadm monitor --environment kernel

But I want you to do this by first doing this:

sudo rmmod ath9k mac80211 cfg80211
sudo dmesg -c > /dev/null

Then on one terminal have open 'sudo udevadm monitor --environment kernel' and in another
run:

sudo modprobe cfg80211
sudo dmesg -c > log

Send me that log, and also the output from the terminal with the udevadm running.

[1] http://wireless.kernel.org/en/developers/Regulatory/CRDA#DebuggingkerneltoCRDAcommunication

  Luis

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

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

[ath9k-devel] ath9k WMP300nv2 (AR5416)

[Luis R. Rodriguez]

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: