9 messages in org.freebsd.freebsd-currentRe: rum(4) not working on 8-CURRENT| From | Sent On | Attachments |
|---|---|---|
| Sevan / Venture37 | May 10, 2009 12:28 pm | |
| Hans Petter Selasky | May 10, 2009 1:17 pm | |
| Andrew Thompson | May 10, 2009 1:47 pm | |
| Sevan / Venture37 | May 10, 2009 3:24 pm | |
| Thomas Sparrevohn | May 11, 2009 6:32 am | |
| Hans Petter Selasky | May 13, 2009 1:45 am | |
| Thomas Sparrevohn | May 13, 2009 3:05 am | |
| Thomas Sparrevohn | May 13, 2009 3:07 am | |
| Sam Leffler | May 13, 2009 7:57 am |
| Subject: | Re: rum(4) not working on 8-CURRENT | |
|---|---|---|
| From: | Hans Petter Selasky (hsel...@c2i.net) | |
| Date: | May 13, 2009 1:45:32 am | |
| List: | org.freebsd.freebsd-current | |
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
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"