<div dir="ltr">On Wed, Oct 1, 2008 at 6:05 AM, Sarton O'Brien <span dir="ltr"><<a href="mailto:roguemoko@roguewrt.org">roguemoko@roguewrt.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I use testing and have varied success with wifi. I don't bother with trying to<br>
identify what going on by what's being reported. It has been stated on here<br>
that the issues with the driver are great enough that statistics may be<br>
skewed.<br>
<br>
What I have witnessed is that sometimes it appears the wireless hardware is<br>
next to useless ... but then under a different update or on another day it<br>
functions flawlessly even in a problematic area of the house. When I was<br>
running stable with no real updates coming down, I couldn't even be bothered<br>
with wireless.<br>
<br>
At the moment, I am having issues. Selecting wireless 'on' results in nothing<br>
being displayed. I have to push all my scripts back across so I haven't tested<br>
manually yet.<br>
<br>
So in summary, I don't think it's worth attempting to figure this out as an<br>
end user as yet. I believe it's driver/kernel related. The hardware itself is<br>
quite new so it doesn't really surprise me. I'd wait for a statement as<br>
_everybody_ has this problem. I can't imagine the devs are sitting there with<br>
freerunners and working wireless ;)<br>
<br></blockquote><div><br>All this discussion does not help if you realize that even after placing the FR *next* to the blooming router, you get reported a signal strength of 65%. What does the hardware expect, building the router *inside* the FR?<br>
</div></div></div>