Re: ifcfg-rh and wpa_supplicant

[Oncaphillis <oncaphillis snafu de>]

On 05/21/2012 07:02 PM, Dan Williams wrote:
> Right, so we need to figure out why wifi isn't working on F16.  It
> should work, and it should work well with nl80211.  WEXT is deprecated
> and will be removed from upstream kernels in the future.  ath9k is
> actively developed upstream and any issues are usually fixed pretty
> quickly.
>
> Are there any interesting messages in 'dmesg' output for your wifi card?
> Is your access point 802.11n-enabled?  Is it using 40MHz wide channels?
>
> Dan

Don't know how to figure out the 40MHz issue.

(A) Here comes the dmesg part around ath9k initialization in
    Fedora12/Linux 3.2.13

<snip>
ath9k 0000:04:00.0: PCI INT A -> Link[LN3A] -> GSI 18 (level, low) -> IRQ 18
ath9k 0000:04:00.0: setting latency timer to 64
...
...
ath: EEPROM regdomain: 0x60
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x60
...
...
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xff560000, irq=18
</snip>

and the iwconfig stuff:

<snip>
wlan0     IEEE 802.11bgn  ESSID:"oncaphillis"
          Mode:Managed  Frequency:2.442 GHz  Access Point: 
00:25:9C:D0:04:FB
          Bit Rate=54 Mb/s   Tx-Power=16 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=45/70  Signal level=-65 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:90   Missed beacon:0
</snip>


(B) The same stuff for Fedora16/Linux 3.3.6
<snip>
[    8.398499] ath: EEPROM regdomain: 0x60
[    8.398507] ath: EEPROM indicates we should expect a direct regpair map
[    8.398517] ath: Country alpha2 being used: 00
[    8.398523] ath: Regpair used: 0x60
[    8.422729] ieee80211 phy0: Selected rate control algorithm 
'ath9k_rate_control'
[    8.423924] Registered led device: ath9k-phy0

[   12.209542] wlan0: authenticate with 00:25:9c:d0:04:fb (try 1)
[   12.211621] wlan0: authenticated
[   12.211720] wlan0: associate with 00:25:9c:d0:04:fb (try 1)
[   12.214487] wlan0: RX AssocResp from 00:25:9c:d0:04:fb (capab=0x411 
status=0 aid=2)
[   12.214500] wlan0: associated
[   12.214512] wlan0: moving STA 00:25:9c:d0:04:fb to state 1
[   12.214520] wlan0: moving STA 00:25:9c:d0:04:fb to state 2
[   12.214529] wlan0: moving STA 00:25:9c:d0:04:fb to state 3
[   12.215576] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

</snip>

<snip>
wlan0     IEEE 802.11bgn  ESSID:"oncaphillis"
          Mode:Managed  Frequency:2.442 GHz  Access Point: 
00:25:9C:D0:04:FB
          Bit Rate=54 Mb/s   Tx-Power=16 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=57/70  Signal level=-53 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:54   Missed beacon:0


</snip>


This however after I switched back to the old network/wpa_supplicant
scripts.

O.