On 9/27/06, Reyk Floeter <[EMAIL PROTECTED]> wrote:
On Sun, Sep 24, 2006 at 02:58:34PM +0200, Pierre Riteau wrote:
> On 9/19/06, Reyk Floeter <[EMAIL PROTECTED]> wrote:
> >hi,
> >
> >i recently enabled support for some newer wireless chipsets from
> >atheros, like the AR2413, AR5413, and AR5424 single chip solutions.
> >
> >please also test it if you have an intel-based mac - the integrated
> >wireless NIC is based on the pci express AR5424 chipset.
> >
>
> I just tested it with a snapshot from the 23th, on a 2Ghz Macbook (non Pro).
> Here is my dmesg :
>
please retry with the attached diff from kettenis. you may see some
11b aps but it doesn't seem to work, yet (the channels are wrong).
> ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
> ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
> ath0: unable to attach hardware; HAL status 22
reyk
Index: ar5212.c
===================================================================
RCS file: /cvs/src/sys/dev/ic/ar5212.c,v
retrieving revision 1.33
diff -u -p -r1.33 ar5212.c
--- ar5212.c 19 Sep 2006 17:49:13 -0000 1.33
+++ ar5212.c 24 Sep 2006 18:22:33 -0000
@@ -304,6 +304,7 @@ ar5k_ar5212_nic_wakeup(struct ath_hal *h
* Reset and wakeup the device
*/
+#if 0
/* ...reset chipset and PCI device */
if (hal->ah_single_chip == AH_FALSE &&
ar5k_ar5212_nic_reset(hal,
@@ -311,6 +312,7 @@ ar5k_ar5212_nic_wakeup(struct ath_hal *h
AR5K_PRINT("failed to reset the AR5212 + PCI chipset\n");
return (AH_FALSE);
}
+#endif
/* ...wakeup */
if (ar5k_ar5212_set_power(hal,
I patched my kernel, here are the results.
- the chip gets recognized.
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
ath0: AR5424 10.3 phy 6.1 rf 10.2, WORAW, address 00:16:cb:bd:08:f4
- My AP is 11b, it's a ral(4) (RT2560) on OpenBSD 4.0, sometimes I see one
from one of my neighbours, both don't show the SSID in ifconfig.
ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:16:cb:bd:08:f4
media: IEEE802.11 autoselect (OFDM6)
status: no network
ieee80211: nwid ""
nwid "" chan 2 bssid 00:13:d3:00:43:fc 20% 11M
inet6 fe80::216:cbff:febd:8f4%ath0 prefixlen 64 scopeid 0x2
- When I first start the ath0 interface, I can see probe requests.
Then I found that doing `ifconfig ath0 mediaopt hostap` and then
`ifconfig ath0 -mediaopt hostap` makes the probe run again.
# tcpdump -y ieee802_11_radio -eni ath0
tcpdump: WARNING: ath0: no IPv4 address assigned
tcpdump: listening on ath0, link-type IEEE802_11_RADIO
23:38:43.383940 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request, <radiotap v0, chan 40, 11a,
txpower 30dBm>
23:38:43.584264 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request, <radiotap v0, chan 44, 11a,
txpower 30dBm>
23:38:43.784279 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request, <radiotap v0, chan 48, 11a,
txpower 30dBm>
23:38:43.984357 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request, <radiotap v0, chan 1, 11b,
txpower 30dBm>
(51 requests each time).
- I also see my AP "beacons".
21:37:18.686664 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
<radiotap v0, chan 8, 11b, rssi 12/64>
21:37:18.789530 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
<radiotap v0, chan 8, 11b, rssi 12/64>
21:37:23.397563 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
<radiotap v0, chan 8, 11b, rssi 11/64>
21:37:58.417322 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
<radiotap v0, chan 8, 11b, rssi 12/64>
21:37:58.519206 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
<radiotap v0, chan 8, 11b, rssi 12/64>
And it goes on at the same rate.
I hope it will be useful. Keep up the good work.
Pierre Riteau
