Date: Thu, 20 Sep 2007 01:58:16 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "PBM ." <onemda@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: wireless support broken on current? Message-ID: <790a9fff0709192358kdafac61i7a8c705f776a22b@mail.gmail.com> In-Reply-To: <3a142e750709191048m66283f3fu947af91cf4b68e9e@mail.gmail.com> References: <3a142e750709190514j61d094bbu68f50d683cd316bd@mail.gmail.com> <20070919131007.GA21833@olymp.home> <3a142e750709191048m66283f3fu947af91cf4b68e9e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/19/07, PBM . <onemda@gmail.com> wrote: > If rum is somehow broken, system should panic, but is just locks in > sbwait state the same thing is with ndis on current > > for example > > #ifconfig rum0/ndis0 up > #ifconfig rum0/ndis0 scan <- never returns > > on STABLE it doesnt happen. > > so if somebody have ndis or rum cards on current I would like to know > if it actually works. On -CURRENT (FreeBSD/amd64) that was updated about an hour ago, I have no major problem using ifconfig ndis0 scan. The first time it is used it will return with a lock order reversal error, but it will show the list of APs. I am able to run the scan a second time with out getting this error. Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0709192358kdafac61i7a8c705f776a22b>