On Wed, Mar 31, 2010 at 4:59 PM, Pavel Roskin wrote:
> You can patch MadWifi to only accept the older card. Then load ath_pci
> first, ath5k second.
That's a very good idea. I had pondered that, but I wasn't sure if it
was possible.
I assume the easiest way to do it would be to neuter the PCI I
I did some testing last night on a spare box I made up. A mini-PCI in PCI card
holder in this PC locks it right up when trying to start Kismet.
That's a bit worse
than the 'just not working' failure from before.
It looks like it might be time to retire this chipset. I'm half
tempted to try MadWi
On Fri, Mar 26, 2010 at 6:04 PM, Pavel Roskin wrote:
> I have a card, the issue is with time, not with access to the hardware.
I understand that, Pavel. Thank you for your time. I just offered the card
to cover all bases. There seems to be little good I can do to resolve
this, so I wanted to m
On Wed, Mar 24, 2010 at 12:22 AM, Pavel Roskin wrote:
> On Wed, 2010-03-24 at 13:12 +0900, Bruno Randolf wrote:
>> On Wednesday 24 March 2010 13:01:15 Pavel Roskin wrote:
>> > AR5210 doesn't seem to send or receive any packets with the current
>> > ath5k. Yet it works (somewhat) with MadWifi. Pe
On Thu, Mar 18, 2010 at 11:51 AM, David Willmore
wrote:
>> 5210 is not well supported, we have various things to fix. Is it
>> usable without wpa ?
>
> That's a good question. I'll give it a shot. Would it become better
> supported if you
> had a cart to play w
Hello, everyone.
Are there any known issues with older Atheros cards trying to
authenticate with wpa_supplicant?
I have a Cisco/Linksys WRT320N that goes 802.11 abgn and is dual band. With
wpa_supplicant configured for that AP, it authenticates fine with the
newer Atheros
radio in my laptop whic
