[Voyage-linux] ath5k 0.7 troubles

[Gustin Johnson]

My test Alix board has both a madwifi and an ath9k device in it.  The
ath9k is a microtik r52n and the madwifi one is an Engenius abg card
of some sort.  I'll check the PCI IDs when I am next in the office.

You can rmmod the ath5k device and then modprobe the ath9k one to see
if that one works.

On Thu, Mar 10, 2011 at 2:30 PM, mgsb <mgsb81 at gmail.com> wrote:
> Hi list
>
> I have one miniPCI wlan card and need two virtual interfaces that I can
> point two instances of hostapd at to make access points.
>
> I have tried the following in /etc/network/interfaces
>
> auto wlan0
> iface wlan0 inet static
> address 10.0.0.1
> netmask 255.0.0.0
> pre-up ifconfig wlan0 hw ether 00:88:88:88:00:2A
> post-up iw dev wlan0 interface add vap0 type __ap
> post-up ifconfig vap0 172.16.0.1 netmask 255.240.0.0
> post-up ifconfig vap0 up
>
> This produces a stack trace like so:
>
> [   15.838763] ------------[ cut here ]------------
> [   15.841489] WARNING: at drivers/net/wireless/ath/ath5k/base.c:3245
> ath5k_bss_info_changed+0x45/0x163 [ath5k])
> [   15.845442] Modules linked in: ledtrig_netdev ledtrig_timer
> ledtrig_heartbeat leds_alix2 geodewdt scx200_acb]
> [   15.976013] Pid: 1527, comm: ifconfig Not tainted 2.6.32-voyage #1
> [   15.978687] Call Trace:
> [   15.982503]  [<d0ac47b2>] ? ath5k_bss_info_changed+0x45/0x163 [ath5k]
> [   15.986476]  [<c1016e53>] warn_slowpath_common+0x60/0x90
> [   15.990475]  [<c1016e90>] warn_slowpath_null+0xd/0x10
> [   15.993496]  [<d0ac47b2>] ath5k_bss_info_changed+0x45/0x163 [ath5k]
> [   15.996488]  [<d0ac476d>] ? ath5k_bss_info_changed+0x0/0x163 [ath5k]
> [   15.999507]  [<d0a6bec8>] ieee80211_bss_info_change_notify+0x13d/0x146
> [mac80211]
> [   16.002512]  [<d0a7527b>] ieee80211_open+0x3e5/0x583 [mac80211]
> [   16.005468]  [<c11e5115>] dev_open+0x92/0xcc
> [   16.008460]  [<c11e484e>] dev_change_flags+0xa4/0x157
> [   16.011462]  [<c121fc98>] devinet_ioctl+0x21a/0x50e
> [   16.014466]  [<c1220e5f>] inet_ioctl+0x8e/0xa7
> [   16.017457]  [<c11d76d5>] sock_ioctl+0x1c0/0x1e4
> [   16.020458]  [<c11d7515>] ? sock_ioctl+0x0/0x1e4
> [   16.023460]  [<c106b7e1>] vfs_ioctl+0x22/0x67
> [   16.026461]  [<c106bd7e>] do_vfs_ioctl+0x4aa/0x4e9
> [   16.029458]  [<c1051578>] ? handle_mm_fault+0x2c0/0x595
> [   16.032463]  [<c103e49d>] ? call_rcu_sched+0xd/0xf
> [   16.035465]  [<c102a68c>] ? __put_cred+0x3b/0x3d
> [   16.038574]  [<c106bde9>] sys_ioctl+0x2c/0x45
> [   16.041463]  [<c10029b5>] syscall_call+0x7/0xb
> [   16.044454] ---[ end trace 8e76113107bc4064 ]---
> [   16.269237] NET: Registered protocol family 10
>
> I guess I have two questions, the first is for help getting a
> /etc/network/interfaces working for this setup, and the second being I
> though 0.7 had ath9k support, why is ath5k being used?
>
> My wlan card is:
>
> ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
> ath5k phy0: RF5112B multiband radio found (0x36)
>
> Many thanks, grateful for any help
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>