Hello,
I just compiled kernel 2.6.24-mm1. Can't get ath5k to work properly.
Worked fine under kernel 2.6.24 with the latest madwifi-snapshot.
Using the following card:
-==Device Information==-
MAC Version: 5212 (0x50)
MAC Revision: 5213A (0x59)
PHY Revision: 5110 (0x00)
PHY Revision: 5110 (0x00)
-==EEPROM Information==-
EEPROM Version: 4.8
EEPROM Size: 16K
Regulatory Domain: 0x64
-==== Capabilities ====-
| 802.11a Support: no |
| 802.11b Support: yes |
| 802.11g Support: yes |
| RFKill Support: yes |
| 32KHz Crystal: yes |
========================
GPIO registers: CR 00000000 DO 00000000 DI 00000007
dmesg output:
ath5k_pci 0000:02:02.0: registered as 'phy0'
phy0: Selected rate control algorithm 'pid'
ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
ath5k phy0: RF2112A 2GHz radio found (0x46)
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 (17-Aug-2007)
wlan0 renamed to ath0
udev: renamed network interface wlan0 to ath0
I can associate to networks:
ath0 IEEE 802.11g ESSID:"92"
Mode:Managed Frequency:2.447 GHz Access Point:
00:1B:2F:7A:AB:A6
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Link Quality=106/100 Signal level=-25 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
dmesg output:
ath0: Initial auth_alg=0
ath0: authenticate with AP 00:1b:2f:7a:ab:a6
ath0: RX authentication from 00:1b:2f:7a:ab:a6 (alg=0 transaction=2
status=0)
ath0: authenticated
ath0: associate with AP 00:1b:2f:7a:ab:a6
ath0: RX AssocResp from 00:1b:2f:7a:ab:a6 (capab=0x411 status=0 aid=1)
ath0: associated
ath0: CTS protection enabled (BSSID=00:1b:2f:7a:ab:a6)
ath0: switched to long barker preamble (BSSID=00:1b:2f:7a:ab:a6)
But that's basically what i can do. I can't ping anything, don't get any
response to DHCP-requests/discovers. Can't reach the default Gateway of
the Netgear wireless-router (essid 92). The same setup works great with
kernel 2.6.24 and the latest madwifi-snapshot.
I don't see any errors in dmesg, 'ping' doesn't output any errors, there
are just no replies. If i scan the whole network range with nmap, nmap
finishes very quick and states all hosts (except the local) as down. I
ran a wireshark session and saw some Samba-broadcasts, but can't ping
or scan the source IP.
Any suggestions?
Greetings,
M. Kramer
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
