Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
> > as Fall semester finishes) but I have a XS-on-XO1 running at home and when a > > XO1 associates with it, the XO1 gets a 172.18.xxx.xxx address (school mesh > > portal). When the XO1.5 associates with school-mesh-0 (I have to click on it > > in the Neighborhood view) the association happens, but the XO1.5 gets > > 169.254.xxx.xxx address, and beyond that the network is unusable. > > that's expected, unfortunately. The XS-on-XO runs an "active antenna" > / "mesh gateway" in the sense of 802.11s. As the current XO-1.5 > drivers/firmware don't talk 802.11s, it won't work. In that sense, the > XO-1.5 is the same as any other 802.11a/b/g device. > > There are two paths to address this > > - get the hostap / thinfirm driver+firmware combo working again. It > was last seen working on a 2.6.17 i think. > > - get 802.11s on XO-1.5 going. this is not trivial... The least common denominator in the XO-1 and XO-2 clients is a connection to an access point. So making the XS (on any hardware) provide a standard 802.11 access point would probably be the easiest path forward. As I recall there was some step in the XO-specific school "provisioning" (antitheft DRM?) that only works over the mesh. So if that hasn't been fixed, either deployments would have to turn off the DRM, or OLPC would need to revise the firmware and/or initrd to handle this interaction via ordinary 802.11 access. Or they could just throw away their DRM-choked devices, as many others have had to do when the big DRM server in the sky went away, and take a lesson from that. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B2 WLAN ECO questions
On Dec 19, 2009, at 10:45 AM, Tiago Marques wrote: > Hi all, > > In an effort to migrate testing to a machine that resembles something > like the C1, I would like to perform the WLAN ECO(s) on the B2 1.5. > However, I found one for the B2 models and another for the B3: > > http://wiki.laptop.org/go/XO1.5_WLAN_SR_ECO > http://wiki.laptop.org/go/XO1.5_WLAN_power_ECO > > Do I only need to do the XO1.5_WLAN_power_ECO, or does the SR ECO also > apply to the B2? From the wiki page it seems a B3 problem only but > AFAIK the B3 is B2+ ECOs, so it would need it too. What am I missing? Each motherboard version has unique issues :-) You will need the WLAN power ECO, which should keep the WLAN powered even though it isn't supported by software. The first and third parts of the WLAN SR ECO are unique to B3s, but you might need to add the pullup on WLAN_RESET. Let us know how it works, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
On Sat, Dec 19, 2009 at 6:29 AM, Martin Langhoff wrote: > Hi Sameer, > > that's expected, unfortunately. The XS-on-XO runs an "active antenna" > / "mesh gateway" in the sense of 802.11s. As the current XO-1.5 > drivers/firmware don't talk 802.11s, it won't work. In that sense, the > XO-1.5 is the same as any other 802.11a/b/g device. > > There are two paths to address this > > - get the hostap / thinfirm driver+firmware combo working again. It > was last seen working on a 2.6.17 i think. > > - get 802.11s on XO-1.5 going. this is not trivial... > > cheers, > > m > > So, what are the chances of a XO 1.5 running as XS? Is this on the books? The hardware is apt for a small school server. Sameer > > On Sat, Dec 19, 2009 at 12:00 AM, Sameer Verma wrote: > > I haven't had much time to look into XS-on-XO1.5 (will look into it as > soon > > as Fall semester finishes) but I have a XS-on-XO1 running at home and > when a > > XO1 associates with it, the XO1 gets a 172.18.xxx.xxx address (school > mesh > > portal). When the XO1.5 associates with school-mesh-0 (I have to click on > it > > in the Neighborhood view) the association happens, but the XO1.5 gets > > 169.254.xxx.xxx address, and beyond that the network is unusable. > > > > Thought I'd pass that along. > > > > Sameer > > -- > > Dr. Sameer Verma, Ph.D. > > Associate Professor, Information Systems > > Director, Center for Business Solutions > > San Francisco State University > > http://verma.sfsu.edu/ > > http://cbs.sfsu.edu/ > > http://is.sfsu.edu/ > > > > ___ > > Server-devel mailing list > > server-de...@lists.laptop.org > > http://lists.laptop.org/listinfo/server-devel > > > > > > > > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
B2 WLAN ECO questions
Hi all, In an effort to migrate testing to a machine that resembles something like the C1, I would like to perform the WLAN ECO(s) on the B2 1.5. However, I found one for the B2 models and another for the B3: http://wiki.laptop.org/go/XO1.5_WLAN_SR_ECO http://wiki.laptop.org/go/XO1.5_WLAN_power_ECO Do I only need to do the XO1.5_WLAN_power_ECO, or does the SR ECO also apply to the B2? From the wiki page it seems a B3 problem only but AFAIK the B3 is B2+ ECOs, so it would need it too. What am I missing? Best regards, Tiago ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XO 1.5 to XS-onXO1 behavior
Hi Sameer, that's expected, unfortunately. The XS-on-XO runs an "active antenna" / "mesh gateway" in the sense of 802.11s. As the current XO-1.5 drivers/firmware don't talk 802.11s, it won't work. In that sense, the XO-1.5 is the same as any other 802.11a/b/g device. There are two paths to address this - get the hostap / thinfirm driver+firmware combo working again. It was last seen working on a 2.6.17 i think. - get 802.11s on XO-1.5 going. this is not trivial... cheers, m On Sat, Dec 19, 2009 at 12:00 AM, Sameer Verma wrote: > I haven't had much time to look into XS-on-XO1.5 (will look into it as soon > as Fall semester finishes) but I have a XS-on-XO1 running at home and when a > XO1 associates with it, the XO1 gets a 172.18.xxx.xxx address (school mesh > portal). When the XO1.5 associates with school-mesh-0 (I have to click on it > in the Neighborhood view) the association happens, but the XO1.5 gets > 169.254.xxx.xxx address, and beyond that the network is unusable. > > Thought I'd pass that along. > > Sameer > -- > Dr. Sameer Verma, Ph.D. > Associate Professor, Information Systems > Director, Center for Business Solutions > San Francisco State University > http://verma.sfsu.edu/ > http://cbs.sfsu.edu/ > http://is.sfsu.edu/ > > ___ > Server-devel mailing list > server-de...@lists.laptop.org > http://lists.laptop.org/listinfo/server-devel > > -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: possible progress on XO-1 camera issues
On Sat, Dec 19, 2009 at 07:00, John Gilmore wrote:
>> #10 0xb67fae59 in gst_xvimagesink_xvimage_put (xvimagesink=0x8364160)
>> at xvimagesink.c:864
>> src = {x = 134867456, y = 140758336, w = -1259457208, h = 1}
>> dst = {x = 137730309, y = 3, w = 0, h = 137691184}
>> result = {x = 0, y = 0, w = 322, h = 241}
>> draw_border = 322
>> __PRETTY_FUNCTION__ = "gst_xvimagesink_xvimage_put"
>>
>> The src.w value is in the same range as the Xlib function addresses;
>> -1259457208 is 0x4B11CAB8 and as can be seen from the call frame #9
>> the XSync function is at 0x4b0eccf7. The other values seem
>> irrational. This may be evidence that the stack has been corrupted
>> somewhere else, or the values not initialised.
>
> Just to rule out going too far down a blind alley...
>
> Try adding a printf of these values to the code there, rather than or
> in addition to using GDB. GDB may not be 100% reliable when accessing
> variables from optimized code. (I used to maintain GDB, and I worked
> very hard to make it never lie to you, but that precept hasn't always
> been followed in the intervening decade, and optimizations have also
> gotten a lot more complicated.)
>
> Or try compiling that code without -O and see if that changes either
> its behavior, or what the debugger reports.
At this point is when I would run totem in valgrind, I can help
interpreting the output if it's not clear.
# yum install valgrind
$ valgrind totem
Regards,
Tomeu
--
«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David
Farning
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Announcing the OLPC OS 10.1.0 final release!
On Sat, Dec 19, 2009 at 07:47, Sameer Verma wrote: > > > On Fri, Dec 18, 2009 at 10:48 PM, Chris Ball wrote: >> >> Hi, >> >> I'm very pleased to announce build os64 as the final 10.1.0 release >> build for XO-1.5 laptops. Here are its release notes: >> >> http://wiki.laptop.org/go/Release_notes/10.1.0 >> >> Instructions for installing the release on an XO-1.5 can be found at: >> >> http://wiki.laptop.org/go/Release_notes/10.1.0#Installation >> >> Many thanks to everyone who contributed to this release! >> >> - Chris. >> -- >> Chris Ball >> One Laptop Per Child >> >> ___ >> Fedora-olpc-list mailing list >> fedora-olpc-l...@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-olpc-list > > > Hearty congratulations!!! Congratulations not only on the result but also on the process, which, at least from where I sit, has been seen as disciplined, realist and without drama. Cheers, Tomeu > Sameer > -- > Dr. Sameer Verma, Ph.D. > Associate Professor, Information Systems > Director, Center for Business Solutions > San Francisco State University > http://verma.sfsu.edu/ > http://cbs.sfsu.edu/ > http://is.sfsu.edu/ > > ___ > Fedora-olpc-list mailing list > fedora-olpc-l...@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-olpc-list > -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
