wow, wireless go BOOM!

[Ricardo Carrano]

Elijah,

I would start recommending that you update the libertas firmware in your B2.

Then if the problem manifests again, I would ask you to check if you can issue a scan
command (iwlist scan) three consecutive times and check if it returns anything. And
please register the libertas error.

To our best knowledge, the wds issue will not manifest in 20p42firmware. And when it did
you needed to reboot the AP (turning off the XO wouldn't suffice).

Up to the present moment, there is no other known scenario where a group of XOs could
disturb a network. So, if you update the firmware and still get general problems in the
network, we are really interested in repeating this.

Um abraço,
Ricardo Carrano


---------- Original Message -----------
From: "Kim Quirk" <kim at laptop.org>
To: elw at stderr.org, "Ricardo Carrano" <carrano at ricardocarrano.com>
Cc: devel at laptop.org
Sent: Mon, 10 Dec 2007 21:35:21 -0500
Subject: Re: wow, wireless go BOOM!

> Elijah,
> Thanks for this information. It would be great if you can start a bug with
> all this info and then we can follow the suggested steps and results.
> 
> Ricardo - can you add suggested tests for Elijah since this is an area you
> have spent a lot of your time recently :-)
> 
> Thanks,
> Kim
> 
> On Dec 10, 2007 7:39 PM, <elw at stderr.org> wrote:
> 
> >
> > today i updated my b4 to the latest firmware, then installed ship-2 via
> > usb, then olpc-updated to the latest joyride build that i could find.
> >
> > [the impetus for the updates, today, beyond the RTC bug, was that the
> > wireless on the B4 didn't seem to want to come on.  Empty neighborhood
> > screen, etc.  There were some libertas error messages in the dmesg output,
> > which were initially somewhat concerning.  Now, I wish that I'd written
> > them down.  Oops.]
> >
> > a minute ago my ubuntu laptop (an aging dell inspiron 8200, with 802.11b
> > truemobile mini-pci card, running 2.6.22...) started spewing error
> > messages and the card began frequently resetting itself.  LOTS of spewage.
> >
> > turning the b4 off seems to have eliminated the issue.  huh.  :-)
> >
> >
> > possible complicating factors:
> >
> > My local network has a BUNCH of 802.11g devices on it.  A d-link pci card,
> > several different belkin and linksys usb dongles, etc.  All talking to the
> > one AP.  And there are several, several, several APs RF-visible from here
> > - typically 20-30, depending on which window of the house you happen to be
> > closest to.
> >
> > There's also a B2-1 here, running 406.15, with very non-current-ish
> > firmware on it.
> >
> > the AP to which the laptop and the B4 were both connected is a Netgear
> > WGR614v6, running firmware V2.0.13_1.0.13NA.  The B2-1 was disconnected
> > and at a point where it would have liked for me to type in a WEP key.
> >
> > The AP is WEP, as there are several devices that don't do WPA and still
> > need to work.
> >
> > This sounds a little bit like the reported WDS/frame/mesh scenarios that
> > I've seen mentioned on a couple of occasions recently... but not exactly.
> >
> > I am happy to do further testing - and endure further possible crashes of
> > my non-XO laptop - to help get this stable again.  :-)
> >
> > --elijah
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
------- End of Original Message -------