Line 77: |
Line 77: |
| ImportError: could not import gobject (error was:ImportError ('When using gi.repository you must not import static modules like "gobject". Please change all occurences of "import gobject" to "from gi.repository import GObject".',)) | | ImportError: could not import gobject (error was:ImportError ('When using gi.repository you must not import static modules like "gobject". Please change all occurences of "import gobject" to "from gi.repository import GObject".',)) |
| | | |
− | == Help with install on IRC == | + | == Help, 1st install, IRC == |
− | *from IRC with permission--[[User:Satellit|Satellit]] 08:01, 22 June 2012 (EDT)
| + | With thanks --[[User:Inkyfingers|Inkyfingers]] 18:18, 27 June 2012 (EDT) |
− | *Based on these instructions: http://wiki.sugarlabs.org/go/Platform_Team/Guide/Sugar_via_Sweets
| + | |
− | <inkyfingers> Image from: http://www.raspbian.org/ | + | <inkyfingers> Image from: http://www.raspbian.org/ is Debian Hard Float (armhf) for RPi |
− | <inkyfingers> is Debian Hard Float (armhf) for RPi
| |
| <inkyfingers> Is armhf likely to be a problem for <sweets>? | | <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 | | <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. | + | <inkyfingers> #644010 is now marked fixed, wheezy seems fine to me with python 2.7 - I believe eliminated. |
| <alsroot> btw, whats exact sugar version you are running on Raspberry? | | <alsroot> btw, whats exact sugar version you are running on Raspberry? |
| <inkyfingers> Ok tried sdk/sugar and dextrose/ | | <inkyfingers> Ok tried sdk/sugar and dextrose/ |
− | <inkyfingers> dextrose marginally more success. | + | <inkyfingers> dextrose marginally more success.[Edit ... at first] |
− | <inkyfingers> * Booting Rpi ... will try to ssh for notes . I tested Sugar 0.88 and 0.94 | + | <inkyfingers> I will try to write only about sweets dextrose/sugar:emulator |
− | ... | |
| <inkyfingers> raspbian@pisces:~$ sweets dextrose/sugar:emulator | | <inkyfingers> raspbian@pisces:~$ sweets dextrose/sugar:emulator |
| <inkyfingers> Xephyr on :30.0 | | <inkyfingers> Xephyr on :30.0 |
Line 96: |
Line 94: |
| <inkyfingers> Sugar: 0.88.1 | | <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> raspbian@pisces:~$ sweets sdk/sugar:emulator |
| <inkyfingers> -- Solve sdk/sugar-artwork for building | | <inkyfingers> -- Solve sdk/sugar-artwork for building |
Line 122: |
Line 108: |
| <inkyfingers> -- Build sdk/sugar (0.94.1) | | <inkyfingers> -- Build sdk/sugar (0.94.1) |
| <inkyfingers> this made me think Activities should be on-board? | | <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> So that trace was just my first successful launch |
| <inkyfingers> df -h (before that command) | | <inkyfingers> df -h (before that command) |
| <inkyfingers> Filesystem Size Used Avail Use% Mounted on | | <inkyfingers> Filesystem Size Used Avail Use% Mounted on |
| <inkyfingers> rootfs 3.3G 2.1G 1.1G 68% / | | <inkyfingers> rootfs 3.3G 2.1G 1.1G 68% / |
− | <inkyfingers> now | + | <inkyfingers> df -h (now) |
| <inkyfingers> rootfs 3.3G 2.2G 985M 69% / | | <inkyfingers> rootfs 3.3G 2.2G 985M 69% / |
| + | <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: nope, this way you can't install activities |
| + | <alsroot> inkyfingers: btw, how long it took to build sugar via "sweets" command? |
| + | <inkyfingers> Over 8 or 9 mins of 100% CPU |