On 10/30/08, Sam Leffler <sam_at_freebsd.org> wrote: > Paul B. Mahol wrote: >> On 10/29/08, Paul B. Mahol <onemda_at_gmail.com> wrote: >> >>> On 10/29/08, Paul B. Mahol <onemda_at_gmail.com> wrote: >>> >>>> On 10/29/08, Sam Leffler <sam_at_freebsd.org> wrote: >>>> >>>>> Maybe you can file a PR or at least provide some details? >>>>> >>>> First I need to test my rum(4) cards, maybe it is only ndis problem. >>>> >>> rum driver still works. >>> >> >> reverting 184271 (and only 184271), fixed ndis problem. >> >> > > Then ndis is busted. This means it didn't setup an association id. I noticed several times that ndis always do something like this without real reason: associate->disassociate and than associate again. (in very short interval) dunno if this have anything to do with association id. It will take me some time to explore this ndis bug.Received on Thu Oct 30 2008 - 23:19:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:36 UTC