Modifying 353 (xo-1) to apply the dev.laptop.org/ticket/10195 fix
tiagomnm at gmail.com
Sat Dec 4 16:07:27 EST 2010
I've constantly experienced the same issues. The XO-1 can't sometimes
connect to my AP and the signal is always very weak compared to all other
wireless devices I have - the XO 1.5 has a much stronger signal, for
It has always been this way and I have it almost for two years now,
independent if I have Gentoo or XO OS installed, for all versions.
On Mon, Nov 29, 2010 at 12:42 PM, Mikus Grinbergs <mikus at bga.com> wrote:
> >> Bernie - you closed this ticket with "I disabled the mesh on boot and no
> >> further incidents of this type were reported".
> >> Please - how did you disable the mesh on boot ?
> > Like so:
> > # enable debug for pgf
> > # also disable mesh to see if this makes the bug go away
> > cat >>"$INSTALL_ROOT/etc/rc.local" <<__EOF__
> > echo 0x26187 > /sys/module/libertas/parameters/libertas_debug
> > echo 0 > /sys/class/net/eth0/lbs_mesh
> > __EOF__
> I was troubleshooting a situation where at least two XO-1 systems would
> only rarely associate with an AP (and often had no 'eth0'). Despite
> trying everything under the sun, I could never determine the cause.
> From my experimenting, whether I had mesh enabled or not did not make a
> difference in this. I have since reflashed those systems with newer
> builds - and am no longer seeing the "missing 'eth0'" situation.
> Perhaps the software in the problem systems had gotten corrupted.
> What I __still__ cannot depend upon is for every XO-1 to reliably
> associate with an AP. A symptom that I frequently observe is that
> 'iwlist eth0 scan' (as root) does not show the radio signals that other
> XO_1s do show. [Wireless debug trace shows the scan is being invoked.]
> Looks to me that I will be spending lots more time pursuing "how come".
> Bernie, thank you for your help, mikus
> Devel mailing list
> Devel at lists.laptop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel