Re: XO-1 Mesh support in F11, testing request

2009-09-19 Thread Mikus Grinbergs

Anyone interested in helping the last few steps in getting XO-1 mesh
support running again?


Sorry - but my news (testing mesh support in F11) is not good.

Could not run a Chat session using any F11-on-XO1 systems.  Don't 
know if it is a problem with Chat-65 itself, or with the interface. 
 I start Chat somewhere, and tell it to share with Neighborhood. 
All systems (802, os6) see that Chat icon on their own Neighborhood 
Views - and if in any system I click that icon, Chat launches.  But 
on (os6) systems, the Share with text in the activity header never 
gets greyed out - in other words, the Chat activity never goes 
on-line.  [Using only (802) systems, Chat works fine on those.]


Was able to get 'rsync' to transfer directories between (os6) 
systems, using the local mesh connection (IP address 169...). 
[Also was able to get 'rsync' to transfer directories between (os6) 
systems, using the local wireless connection (IP address 10...).]




But my overall impression of mesh support in F11 is that currently 
it is flaky.  One system ended up showing a blank screen whenever 
F1 (for Neighborhood View) was pressed (went back to normal after 
being rebooted).  Neighborhood view often showed invitations to 
chat even half an hour after the inviting system had been shut 
down.  Some systems connected quickly to the local mesh - others 
took many minutes of pulsing to do so.  Sometimes not all on-line 
systems showed in Neighborhood.  It was unpleasant whenever the mesh 
icons in Neighborhood stopped accepting clicks - all I could do was 
to reboot the system this happened on.  [IIRC, one of the ways to 
trigger this was to click on the (mesh) Frame icon's 'Disconnect' - 
there seemed to be no way to 'Connect' again.]




My personal desire is to *control* what is happening.  I realize 
that for kids (the primary user target), the more things get done 
hands off, the easier to use the product.  But that means that 
when things do not go as expected, users can be left helpless.  It 
was frustrating to see Chat launch but fail to show messages from 
others on its screen;  it was frustrating to see Neighborhood View 
showing the same information as before, when I knew things had 
changed;  it was frustrating to not be able to turn mesh back on, 
when it appeared to have given up.



mikus


p.s.  attachment shows some meshbox messages

1253325333.007362 DEBUG sugar.presence.presenceservice: Created proxy Buddy 
object at 0x95282d4 (sugar+presence+buddy+Buddy at 0x90ff160)
** (sugar-session:1959): DEBUG: starting phase 1

** (sugar-session:1959): DEBUG: ending phase 1

** (sugar-session:1959): DEBUG: starting phase 2

** (sugar-session:1959): DEBUG: ending phase 2

** (sugar-session:1959): DEBUG: starting phase 3

** (sugar-session:1959): DEBUG: ending phase 3

** (sugar-session:1959): DEBUG: starting phase 4

** (sugar-session:1959): DEBUG: ending phase 4

** (sugar-session:1959): DEBUG: starting phase 5

** (sugar-session:1959): DEBUG: ending phase 5

1253325333.503768 DEBUG root: STARTUP: Loading the desktop window
1253325333.628769 DEBUG root: STARTUP: Loading the home view
1253325333.631072 DEBUG root: STARTUP: Loading the favorites view
1253325339.292493 DEBUG root: FavoritesSetting layout 'spiral-layout'
1253325339.296294 DEBUG root: Icon without fixed_position: _MyIcon object at 
0x95285a4 (SugarFavoritesMyIcon at 0x94b2c90)
1253325339.298559 DEBUG root: Icon without fixed_position: CurrentActivityIcon 
object at 0x9528874 (CanvasIcon at 0x94b2d08)
1253325339.300673 DEBUG root: STARTUP: Loading the activities list
1253325339.696847 DEBUG root: ('Setup widget', gtk.RadioButton object at 
0x9528f54 (GtkRadioButton at 0x922a940))
1253325339.704580 WARNING root: No gtk.AccelGroup in the top level window.
1253325339.744635 DEBUG root: ('Setup widget', gtk.RadioButton object at 
0x95319b4 (GtkRadioButton at 0x922ac40))
1253325339.751851 WARNING root: No gtk.AccelGroup in the top level window.
1253325339.757904 DEBUG root: STARTUP: Loading the group view
1253325339.770991 DEBUG sugar.presence.presenceservice: Reused proxy Buddy 
object at 0x95282d4 (sugar+presence+buddy+Buddy at 0x90ff160)
1253325339.906036 DEBUG root: STARTUP: Loading the mesh view
1253325340.229738 DEBUG root: Not an activity icon _MyIcon object at 0x95285a4 
(SugarFavoritesMyIcon at 0x94b2c90)
1253325340.232643 DEBUG root: Not an activity icon CurrentActivityIcon object 
at 0x9528874 (CanvasIcon at 0x94b2d08)
1253325340.368353 DEBUG root: activate channel 1 anycast \xc0'\xc0'\xc0\x00
1253325341.537885 DEBUG root: Connection activated: 
/org/freedesktop/NetworkManager/ActiveConnection/1
1253325341.583291 DEBUG sugar.presence.presenceservice: Reused proxy Buddy 
object at 0x95282d4 (sugar+presence+buddy+Buddy at 0x90ff160)
Traceback (most recent call last):
  File /usr/lib/python2.6/site-packages/dbus/connection.py, line 586, in 
msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
  File 

Re: XO-1 Mesh support in F11, testing request

2009-09-19 Thread Daniel Drake
2009/9/19 Mikus Grinbergs mi...@bga.com:
 Anyone interested in helping the last few steps in getting XO-1 mesh
 support running again?

 Sorry - but my news (testing mesh support in F11) is not good.

Thanks for the feedback. I think we can summarize the problems into a
few groups:

 - activity/presence/telepathy level problems (e.g. your inability to
chat successfully) that are on a different level of the stack from the
work I've been doing
 - a Sugar bug where the neighborhood view becomes partially or wholly
unresponsive to clicks (I saw this twice, even before modifying to add
mesh support)
 - some mesh connectivity issues related to
http://thread.gmane.org/gmane.linux.network.networkmanager.devel/13607
(related to my work, but to be tackled separately)

I'll move forward on getting my work into NM-0.7 and F11, which will
then enable more people to help fix the other issues you have found.

Thanks,
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: XO-1 Mesh support in F11, testing request

2009-09-18 Thread Daniel Drake
All fixed and tested!

new RPMs at http://dev.laptop.org/~dsd/20090918/

patches submitted to NetworkManager-0.7
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: XO-1 Mesh support in F11, testing request

2009-09-17 Thread Daniel Drake
2009/9/16 Daniel Drake d...@laptop.org:
 all rpms at
 http://dev.laptop.org/~dsd/20090916/

found a few minutes to find a few problems:

forgot to install the fdi file
olpcmesh.py is not being installed from the sugar package
shortened dhcpcd timeout not working
Sugar never seems to give up trying school mesh (or never falls back
to link local)

no time to investigate further now

Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: XO-1 Mesh support in F11, testing request

2009-09-17 Thread James Cameron
Haven't had a chance to try this yet, been busy with assessment tasks
... but what particular F11 for XO-1 build are you testing with?

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


XO-1 Mesh support in F11, testing request

2009-09-16 Thread Daniel Drake
Hi,

Anyone interested in helping the last few steps in getting XO-1 mesh
support running again?

Recently, OLPC mesh support was committed to NetworkManager-0.8 git
master. I've now backported this to 0.7 and packaged it up, and
packaged sugar to readd OLPC mesh support there too. Completely
untested as I don't have an XO to hand. There are probably a couple of
trivial mistakes so testing plus logs/technical investigation/patches
would be really helpful

all rpms at
http://dev.laptop.org/~dsd/20090916/

cheers
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel