Date: Wed, 13 May 2009 10:48:36 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com>, Sevan / Venture37 <venture37@gmail.com>, Andrew Thompson <thompsa@freebsd.org>, freebsd-current@freebsd.org Subject: Re: rum(4) not working on 8-CURRENT Message-ID: <200905131048.37146.hselasky@c2i.net> In-Reply-To: <200905130922.52887.Thomas.Sparrevohn@btinternet.com> References: <200905130922.52887.Thomas.Sparrevohn@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 13 May 2009, Thomas Sparrevohn wrote: > Hans Petter > > I don't see this one came through - but I am having real pains with rum(4) > - the weird thing it that it seems to work with HTTP etc but not with fetch > - no panics - it just drops all connections and routing information - It am > still getting the "kernel: rum0: need multicast update callback" error but > I cannot see that it has anything to do with the issue In my experience it's not the driver that is flaky, but the firmware in the hardware. I've seen several times that if certain commands are intermixed, the firmware will completely stop responding. Has the rum driver ever worked with USB2 and -current? Recently there has been several changes in the WLAN layer and some minor changes in if_rum. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905131048.37146.hselasky>