Difference between revisions of "Talk:Sugar Creation Kit/sck/Advanced Topics"

From Sugar Labs
Jump to navigation Jump to search
(Test report-sugar on RPi)
 
m (→‎Test report: more details)
Line 1: Line 1:
 
==Test report==
 
==Test report==
 
*from IRC with permission--[[User:Satellit|Satellit]] 08:01, 22 June 2012 (EDT)
 
*from IRC with permission--[[User:Satellit|Satellit]] 08:01, 22 June 2012 (EDT)
 +
<inkyfingers> Image from: http://www.raspbian.org/
 +
<inkyfingers> is Debian Hard Float (armhf) for RPi
 +
<inkyfingers> Is armhf likely to be a problem for <sweets>?
 +
<alsroot> inkyfingers: I didn't try to run sugar on arm. OLPC people support it but I dunno do they use sugar directly from upstream brunches (what was used for sweets (not SD)) or not
 +
<inkyfingers> #644010 is now marked fixed - so wheezy seems fine to me with python 2.7 - I believe eliminated.
 +
<alsroot> btw, whats exact sugar version you are running on Raspberry?
 +
<inkyfingers> Ok tried sdk/sugar and dextrose/
 +
<inkyfingers> dextrose marginally more success.
 +
<inkyfingers> * Booting Rpi ... will try to ssh for notes . I tested Sugar 0.88 and 0.94
 +
...
 +
<inkyfingers>  raspbian@pisces:~$ sweets  dextrose/sugar:emulator
 +
<inkyfingers> Xephyr on :30.0
 +
<inkyfingers> About my computer:
 +
<inkyfingers> Build: Debian GNU/Linux testing/unstable
 +
<inkyfingers> Sugar: 0.88.1
 +
...
 +
<inkyfingers> I will try to write only about sweets  dextrose/sugar:emulator ...
 +
<inkyfingers> F1 to F6 all fine ok
 +
<alsroot> thats fine..
 +
<alsroot> though, in my mind SD, finally, is more useful way to start sugar itself. but unfortunately, it does not [yet]support arm
 +
<inkyfingers> I could see no avatars in F1 in dextrose <seen fine in sdk, 0.94>
 +
<inkyfingers> I have no Activities in F3
 +
<alsroot> for activities, you can unzip some of them (that are pure python) to ~/Activities
 +
<inkyfingers> That would be a good next step.
 +
<inkyfingers> Two usb ports are used by mouse and kbd. I will prepare a USB stick next and try that out.
 +
<alsroot> inkyfingers: btw, how long it took to build sugar via "sweets" command?
 +
<inkyfingers> Over 8 or 9 mins of 100% CPU
 +
<inkyfingers> sorry ssh into my rubbish notes is hard !! I keep not finding what I want!
 +
<inkyfingers> raspbian@pisces:~$ sweets  sdk/sugar:emulator
 +
<inkyfingers> -- Solve sdk/sugar-artwork for building
 +
<inkyfingers> -- Solve sdk/sugar-base for building
 +
<inkyfingers> -- Solve sdk/sugar-toolkit for building
 +
<inkyfingers> -- Solve sdk/sugar-datastore for building
 +
<inkyfingers> -- Solve sdk/telepathy-mission-control for building
 +
<inkyfingers> -- Solve sdk/sugar for building
 +
<inkyfingers> -- Build sdk/sugar-artwork (0.94.0)
 +
<inkyfingers> -- Build sdk/sugar-base (0.94.0)
 +
<inkyfingers> -- Build sdk/sugar-toolkit (0.94.0)
 +
<inkyfingers> -- Build sdk/sugar-datastore (0.94.0)
 +
<inkyfingers> -- Build sdk/telepathy-mission-control (5.7.1)
 +
<inkyfingers> -- Build sdk/sugar (0.94.1)
 +
<inkyfingers> this made me think Activities should be on-board?
 +
<alsroot> inkyfingers: nope, this way you can't install activities
 +
<alsroot> dunno will Browse work on or not (to open ASLO), but just download .xo files to unzip them to ~/Activities
 +
<inkyfingers> So that trace was just my first successful launch
 +
<inkyfingers> df -h (before that command)
 +
<inkyfingers> rootfs          3.3G  2.1G  1.1G  68% /
 +
<inkyfingers> now
 +
<inkyfingers> rootfs          3.3G  2.2G  985M  69% /
 +
<inkyfingers> Filesystem      Size  Used Avail Use% Mounted on
 +
 
  <inkyfingers> Test report:
 
  <inkyfingers> Test report:
 
  <inkyfingers> Product of :sweets  sdk/sugar:emulator
 
  <inkyfingers> Product of :sweets  sdk/sugar:emulator

Revision as of 07:11, 22 June 2012

Test report

  • from IRC with permission--Satellit 08:01, 22 June 2012 (EDT)
<inkyfingers> Image from: http://www.raspbian.org/
<inkyfingers> is Debian Hard Float (armhf) for RPi
<inkyfingers> Is armhf likely to be a problem for <sweets>?
<alsroot> inkyfingers: I didn't try to run sugar on arm. OLPC people support it but I dunno do they use sugar directly from upstream brunches (what was used for sweets (not SD)) or not
<inkyfingers> #644010 is now marked fixed - so wheezy seems fine to me with python 2.7 - I believe eliminated.
<alsroot> btw, whats exact sugar version you are running on Raspberry?
<inkyfingers> Ok tried sdk/sugar and dextrose/
<inkyfingers> dextrose marginally more success.
<inkyfingers> * Booting Rpi ... will try to ssh for notes . I tested Sugar 0.88 and 0.94
...
<inkyfingers>  raspbian@pisces:~$ sweets  dextrose/sugar:emulator
<inkyfingers> Xephyr on :30.0
<inkyfingers> About my computer:
<inkyfingers> Build: Debian GNU/Linux testing/unstable
<inkyfingers> Sugar: 0.88.1
...
<inkyfingers> I will try to write only about sweets  dextrose/sugar:emulator ...
<inkyfingers> F1 to F6 all fine ok
<alsroot> thats fine..
<alsroot> though, in my mind SD, finally, is more useful way to start sugar itself. but unfortunately, it does not [yet]support arm
<inkyfingers> I could see no avatars in F1 in dextrose <seen fine in sdk, 0.94>
<inkyfingers> I have no Activities in F3
<alsroot> for activities, you can unzip some of them (that are pure python) to ~/Activities
<inkyfingers> That would be a good next step.
<inkyfingers> Two usb ports are used by mouse and kbd. I will prepare a USB stick next and try that out.
<alsroot> inkyfingers: btw, how long it took to build sugar via "sweets" command?
<inkyfingers> Over 8 or 9 mins of 100% CPU
<inkyfingers> sorry ssh into my rubbish notes is hard !! I keep not finding what I want!
<inkyfingers> raspbian@pisces:~$ sweets  sdk/sugar:emulator
<inkyfingers> -- Solve sdk/sugar-artwork for building
<inkyfingers> -- Solve sdk/sugar-base for building
<inkyfingers> -- Solve sdk/sugar-toolkit for building
<inkyfingers> -- Solve sdk/sugar-datastore for building
<inkyfingers> -- Solve sdk/telepathy-mission-control for building
<inkyfingers> -- Solve sdk/sugar for building
<inkyfingers> -- Build sdk/sugar-artwork (0.94.0)
<inkyfingers> -- Build sdk/sugar-base (0.94.0)
<inkyfingers> -- Build sdk/sugar-toolkit (0.94.0)
<inkyfingers> -- Build sdk/sugar-datastore (0.94.0)
<inkyfingers> -- Build sdk/telepathy-mission-control (5.7.1)
<inkyfingers> -- Build sdk/sugar (0.94.1)
<inkyfingers> this made me think Activities should be on-board?
<alsroot> inkyfingers: nope, this way you can't install activities
<alsroot> dunno will Browse work on or not (to open ASLO), but just download .xo files to unzip them to ~/Activities
<inkyfingers> So that trace was just my first successful launch
<inkyfingers> df -h (before that command)
<inkyfingers> rootfs          3.3G  2.1G  1.1G  68% /
<inkyfingers> now
<inkyfingers> rootfs          3.3G  2.2G  985M  69% /
<inkyfingers> Filesystem      Size  Used Avail Use% Mounted on
<inkyfingers> Test report:
<inkyfingers> Product of :sweets  sdk/sugar:emulator
<inkyfingers> on Raspberry pi, running OS from www.raspbian.org
<inkyfingers> Build: Debian GNU/Linux testing/unstable
<inkyfingers> Sugar: 0.94.1
<inkyfingers> All Function keys, F1 to 6, work ok
<inkyfingers> Avatars seen ok in F1 and F2,
<inkyfingers> F3 I have 2 working activities
<inkyfingers> Full control to "spare partition"
<inkyfingers> Journal is probably being slow to update - not correct/full, partial record.
<inkyfingers> No connection to ASLO,
<inkyfingers> 8 Activities, downloaded to pc, and transferred to spare partition.
<inkyfingers> irc-10.xo starts and tested ok
<inkyfingers> chat-77.xo starts and works, test tx ok
<inkyfingers> browse-129.xo, Reports, failed to start
<inkyfingers> surf-115.xo Reports, failed to start
<inkyfingers> terminal-39.xo Reports, failed to start
...
<inkyfingers> speak-41.xo  Reports, failed to start
<inkyfingers> physics-10.xo Reports, failed to start
<inkyfingers> sugar_commander Reports, failed to start