Max Laier wrote:
> This is partly fixed in CURRENT already, but needs more work to be MFCed. Is
> there any chance that you can test CURRENT plus this patch as well?
Not in the near future, I'm sorry. But I'll watch the cvs-logs and
report back to you, as soon as I tried CURRENT on this laptop.
On Saturday 08 April 2006 13:49, Ulrich Spoerlein wrote:
> Max Laier wrote:
> > Could you try the attached patch, please? This is something I did for
> > iwi and just moved the general idea over without testing or close
> > evaluation. So be aware and let me know either way. Thanks.
>
> Great, T
Max Laier wrote:
> Could you try the attached patch, please? This is something I did for
> iwi and just moved the general idea over without testing or close
> evaluation. So be aware and let me know either way. Thanks.
Great, Thanks!
I ran with this patch and loaded different fimwares, upped a
On Thursday 06 April 2006 14:14, Ulrich Spoerlein wrote:
> Hello,
>
> I almost always get a panic when running kismet on my ipw-Interface
> under 6.1-PRERELEASE. This has been the case ever since ipw hit the
> tree. Sometimes kismet works, sometimes it doesn't. A sure way to
> trigger the panic is
Hello,
I almost always get a panic when running kismet on my ipw-Interface
under 6.1-PRERELEASE. This has been the case ever since ipw hit the
tree. Sometimes kismet works, sometimes it doesn't. A sure way to
trigger the panic is to switch between bss/ibss/monitor mode prior to
running kismet. Per
