Re: wireless support broken on current?

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 9/19/07, Oliver Herold <oliver_at_akephalos.de> wrote:
> Maybe rum per se is broken. I remember some problems with rum and kernel
> panics
> in current. I'm using ral at the moment together with a pc-card without any
> problems. Current is from today.
>
> Cheers, Oliver
>
> On Wed, Sep 19, 2007 at 12:14:48PM +0000, PBM . wrote:
> > With both ndis0 and rum0 drivers for two diferent WLAN card I could
> > not connect to AP.
> >
> > # ifconfig ndis0/rum0 scan doesnt give any results, ifconfig stays in
> > sbwait state forever.
> >
> > on 6.2 STABLE ndis0 works fine but there is no rum0 - which is only
> > available in CURRENT so it is reason I prefer current.
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
> --
> Physically there is nothing to distinguish human society from the
> farm-yard except that children are more troublesome and costly than
> chickens and women are not so completely enslaved as farm stock.
> 		-- George Bernard Shaw, "Getting Married"
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>