Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Hi James,
Thanks a ton for the detailed response.
I will keep working on it and try to implement the fixes suggested by you.
Best Regards
Smrann Arora
On Sun, Apr 2, 2023 at 3:57 PM James Cameron wrote:
> G'day Simrann,
>
> I'll reply in context below, please scroll down.
>
> You wrote:
> > While performing the testing on Sugar platform, almost all the
> > activities 'failed to load' and were having erratic
> > behavior. However, when I restarted Sugar, some of them started
> > working fine, but after sometime again that erratic behavior showed
> > up.
>
> Yes, you may wish to investigate this.
>
> When the shell starts an activity, a timer is initiated. If the
> activity has not started when the timer expires, the shell declares
> "failed to start". An activity that is slow to start may yet appear
> after this message.
>
> Raspberry Pi can be very slow, depending on the performance
> (i.e. price) of the microSD or SD card being used. You can measure
> performance using "sudo apt install pv" and "sudo pv /dev/mmcblk0 >
> /dev/null". My test system, a Raspberry Pi Model B+ with an old 32GB
> SD card, shows 20 MiB/s.
>
> On first start, GStreamer populates a
> .cache/gstreamer-1.0/registry.armv7l.bin file, Python must load all
> modules, and Calculate import of matplotlib iterates over the
> available styles. All this takes time, and may cause the shell to
> timeout and report "failed to start".
>
> Graphics updates can also be very slow. During activity launch a
> pulsing icon in the shell process competes with the starting of the
> activity. Simultaneous processes making demands of the operating
> system and hardware cause mutual slowdown. You can see this using
> top(1) over ssh(1).
>
> sugar:src/jarabe/view/launcher.py sets a default launcher interval of
> 100 milliseconds. On particularly slow systems we have set this to
> 500 milliseconds using gsettings. You might try that, and if it fixes
> the problem then you know it is the pulsing icon to blame.
>
> ```
> gsettings set org.sugarlabs.desktop launcher-interval 1000
> ```
>
> The pulsing icon should look much slower. Perhaps Sugar should detect
> Raspberry Pi and set it lower by default.
>
> You can look through .sugar/default/logs for previous sessions, using
> stat(1) to compare file birth (activity start), modify (last output),
> and change (activity stop). This may show you that some activities
> did actually start later, but were not visible because you had gone on
> to start something else.
>
> > Also, I did try installing other activities by using the following
> > command and had also listed the error in my testing report shared
> > earlier with you:
> >
> > sudo apt install sugar-{abacus,
> > [...]
>
> That command has been removed from my instructions. It was out of
> date. Therefore the error is of no concern.
>
> > As far as your second point is concerned, by Browse -> Activities
> > (the library) you mean that installing activities via the Sugar
> > Store ([1] https://activities.sugarlabs.org/en-US/sugar/) right? I
> > will try that as well going further.
>
> No, that's for Python 2 activities. Debian, Ubuntu, Fedora, and
> Raspberry Pi OS no longer provide Python 2.
>
> For Python 3 activities the library is linked from Browse default page
> to https://v4.activities.sugarlabs.org
>
> The library is much smaller, because many activities have not been
> released since the library was opened.
>
> > I have also shared my GSoC proposal on mail and sugar-devel mailing
> > list, I would request your suggestions and valuable feedback for
> > improving the same.
>
> That's really up to your mentors.
>
> > Thanks a lot
> > Simrann Arora
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
G'day Simrann,
I'll reply in context below, please scroll down.
You wrote:
> While performing the testing on Sugar platform, almost all the
> activities 'failed to load' and were having erratic
> behavior. However, when I restarted Sugar, some of them started
> working fine, but after sometime again that erratic behavior showed
> up.
Yes, you may wish to investigate this.
When the shell starts an activity, a timer is initiated. If the
activity has not started when the timer expires, the shell declares
"failed to start". An activity that is slow to start may yet appear
after this message.
Raspberry Pi can be very slow, depending on the performance
(i.e. price) of the microSD or SD card being used. You can measure
performance using "sudo apt install pv" and "sudo pv /dev/mmcblk0 >
/dev/null". My test system, a Raspberry Pi Model B+ with an old 32GB
SD card, shows 20 MiB/s.
On first start, GStreamer populates a
.cache/gstreamer-1.0/registry.armv7l.bin file, Python must load all
modules, and Calculate import of matplotlib iterates over the
available styles. All this takes time, and may cause the shell to
timeout and report "failed to start".
Graphics updates can also be very slow. During activity launch a
pulsing icon in the shell process competes with the starting of the
activity. Simultaneous processes making demands of the operating
system and hardware cause mutual slowdown. You can see this using
top(1) over ssh(1).
sugar:src/jarabe/view/launcher.py sets a default launcher interval of
100 milliseconds. On particularly slow systems we have set this to
500 milliseconds using gsettings. You might try that, and if it fixes
the problem then you know it is the pulsing icon to blame.
```
gsettings set org.sugarlabs.desktop launcher-interval 1000
```
The pulsing icon should look much slower. Perhaps Sugar should detect
Raspberry Pi and set it lower by default.
You can look through .sugar/default/logs for previous sessions, using
stat(1) to compare file birth (activity start), modify (last output),
and change (activity stop). This may show you that some activities
did actually start later, but were not visible because you had gone on
to start something else.
> Also, I did try installing other activities by using the following
> command and had also listed the error in my testing report shared
> earlier with you:
>
> sudo apt install sugar-{abacus,
> [...]
That command has been removed from my instructions. It was out of
date. Therefore the error is of no concern.
> As far as your second point is concerned, by Browse -> Activities
> (the library) you mean that installing activities via the Sugar
> Store ([1] https://activities.sugarlabs.org/en-US/sugar/) right? I
> will try that as well going further.
No, that's for Python 2 activities. Debian, Ubuntu, Fedora, and
Raspberry Pi OS no longer provide Python 2.
For Python 3 activities the library is linked from Browse default page
to https://v4.activities.sugarlabs.org
The library is much smaller, because many activities have not been
released since the library was opened.
> I have also shared my GSoC proposal on mail and sugar-devel mailing
> list, I would request your suggestions and valuable feedback for
> improving the same.
That's really up to your mentors.
> Thanks a lot
> Simrann Arora
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Hi James,
Thanks for your email.
While performing the testing on Sugar platform, almost all the activities
'failed to load' and were having erratic behavior. However, when I
restarted Sugar, some of them started working fine, but after sometime
again that erratic behavior showed up.
Also, I did try installing other activities by using the following command
and had also listed the error in my testing report shared earlier with you:
`
sudo apt install sugar-{abacus,browse,calculate,chart,chat,clock,\
develop,finance,findwords,fototoon,fractionbounce,gears,\
imageviewer,implode,jukebox,letters,log,maze,measure,memorize,\
moon,music-keyboard,paint,physics,pippy,poll,portfolio,read,\
Record,speak,stopwatch,story,terminal,words,write}-activity ` This was
the error that came up after running the above command : ` E: Unable to
locate package sugar-{abacus,browse,calculate,chart,chat,clock
E: Unable to locate
package develop,finance,findwords,fototoon,fractionbounce,gears,
E: Unable to locate package
imageviewer,implode,jukebox,letters,log,maze,measure,memorize,
E: Unable to locate package
moon,music-keyboard,paint,physics,pippy,poll,portfolio,read,
E: Unable to locate package
record,speak,stopwatch,story,terminal,words,write}-activity
` As far as your second point is concerned, by Browse -> Activities (the
library) you mean that installing activities via the Sugar Store (
https://activities.sugarlabs.org/en-US/sugar/) right? I will try that as
well going further.
I have also shared my GSoC proposal on mail and sugar-devel mailing list, I
would request your suggestions and valuable feedback for improving the same.
Thanks a lot
Simrann Arora
On Sat, Apr 1, 2023 at 3:15 AM James Cameron wrote:
> Thanks for that. You found what I found, that most of Sugar is
> working fine in Raspberry Pi OS. In your logs, only the Write
> activity tracebacks are concerning, the rest seems normal. There may
> be ways to solve the rest, but if I discovered them I would fix them
> rather than consume time in explaining them.
>
> You may widen your tests by installing any additional activities
> using;
>
> 1. sudo apt install sugar-*-activity
>
> 2. Browse -> Activities (the library)
>
> The activities installed on Fedora SoaS are more extensive, may not be
> available in Browse -> Activities, and may not be packaged for Debian.
>
> The first step is easily in our control, the second step requires
> support from the Debian Project.
>
> Modifying and releasing activities is described in our guide to
> contributing, with the release to the library described in the last
> item of the list;
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>
> For most activities, the role of activity maintainer is flexibly
> assigned; i.e. developers now tend to take the role for a few days and
> then release.
>
> On Sat, Apr 01, 2023 at 02:48:13AM +0530, Simrann Arora wrote:
> > Hello James,
> >
> > Thanks a lot for the detailed response.
> >
> > I have gone through the logs and prepared a log report of the bugs and
> broken
> > activities that I encountered. I will be trying to find fixes and
> > continue working on them during the GSoC period.
> >
> > I would request you to review this and give your suggestions on how to
> fix
> > these errors further.
> >
> > Thanks and Best Regards
> > Simrann Arora
> > GitHub Handle: @simrann20
> >
> > *
> > On Fri, Mar 31, 2023 at 4:10 AM James Cameron <[1]qu...@laptop.org>
> wrote:
> >
> > Thanks for testing.
> >
> > Some of the information we gave was out of date, please see the
> > changes in [2]https://github.com/sugarlabs/sugar/commit/cc22632
> >
> > The missing icon for the description is a known issue being tracked
> as
> > [3]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but
> nobody
> > seems to be working on it.
> >
> > Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy,
> > Write and Log may be found in .sugar/default/logs
> >
> > Please use copy and paste of terminal text rather than photographs or
> > screenshots. We cannot search them.
> >
> > On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote:
> > > Hi Mentors,
> > >
> > > Hope you all are doing great!
> > >
> > > I have tested Sugar on Raspberry Pi and I have prepared a report
> based on
> > my
> > > findings. I am attaching the same for your reference. I am trying
> to fix
> > these
> > > bugs and would request you all to review and give your
> suggestions on
> > how to
> > > fix these issues going forward.
> > >
> > > Thanks and Best Regards
> > > Simrann Arora
> > > GitHub Handle: @simrann20
> > > *
> > > On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1][4]
> qu...@laptop.org>
> > wrote:
> > >
> > > G'day Simrann,
> > >
> > > Running Sugar on Raspberry Pi OS to identify what
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Thanks for that. You found what I found, that most of Sugar is working fine in Raspberry Pi OS. In your logs, only the Write activity tracebacks are concerning, the rest seems normal. There may be ways to solve the rest, but if I discovered them I would fix them rather than consume time in explaining them. You may widen your tests by installing any additional activities using; 1. sudo apt install sugar-*-activity 2. Browse -> Activities (the library) The activities installed on Fedora SoaS are more extensive, may not be available in Browse -> Activities, and may not be packaged for Debian. The first step is easily in our control, the second step requires support from the Debian Project. Modifying and releasing activities is described in our guide to contributing, with the release to the library described in the last item of the list; https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer For most activities, the role of activity maintainer is flexibly assigned; i.e. developers now tend to take the role for a few days and then release. On Sat, Apr 01, 2023 at 02:48:13AM +0530, Simrann Arora wrote: > Hello James, > > Thanks a lot for the detailed response. > > I have gone through the logs and prepared a log report of the bugs and broken > activities that I encountered. I will be trying to find fixes and > continue working on them during the GSoC period. > > I would request you to review this and give your suggestions on how to fix > these errors further. > > Thanks and Best Regards > Simrann Arora > GitHub Handle: @simrann20 > > * > On Fri, Mar 31, 2023 at 4:10 AM James Cameron <[1]qu...@laptop.org> wrote: > > Thanks for testing. > > Some of the information we gave was out of date, please see the > changes in [2]https://github.com/sugarlabs/sugar/commit/cc22632 > > The missing icon for the description is a known issue being tracked as > [3]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but nobody > seems to be working on it. > > Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy, > Write and Log may be found in .sugar/default/logs > > Please use copy and paste of terminal text rather than photographs or > screenshots. We cannot search them. > > On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote: > > Hi Mentors, > > > > Hope you all are doing great! > > > > I have tested Sugar on Raspberry Pi and I have prepared a report based > on > my > > findings. I am attaching the same for your reference. I am trying to > fix > these > > bugs and would request you all to review and give your suggestions on > how to > > fix these issues going forward. > > > > Thanks and Best Regards > > Simrann Arora > > GitHub Handle: @simrann20 > > * > > On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1][4]qu...@laptop.org> > wrote: > > > > G'day Simrann, > > > > Running Sugar on Raspberry Pi OS to identify what needs fixing will > be > > a good thing for Sugar Labs. It will also feed into and affect the > > other proposals and ideas. There is an opportunity to collaborate > > with many others. > > > > Your proposal could include a list of Raspberry Pi focused Linux > > distributions you have tested Sugar on, along with the broad > outcomes. > > > > On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote: > > > Hello James, > > > > > > Thanks for your quick response. > > > > > > From what I understand, `rpi23-gen-image` repository is old so it > cannot > > be > > > used for this project. > > > I think I should run Sugar on Raspberry Pi OS and identify what is > broken > > /bugs, > > > so I can work on fixing them during my GSoC period. > > > > > > I will also check out other debian image builders for Raspberry Pi > > which can be > > > leveraged to create Sugar OS images. > > > > > > I would also request my mentors @walterbender and @alexperez to > see if > > my > > > understanding is correct and also discuss the hardware > requirements > to > > extend > > > the functionalities of existing activities like Turtle Blocks, > Measure, > > and > > > Pippy. > > > > > > Thanks and Best Regards > > > Simrann Arora > > > GitHub Handle: @simrann20 > > > * > > > On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1][2][5] > qu...@laptop.org> > > wrote: > > > > > > Hello Simrann, > > > > > > I've just now tested [2][3][6]https://github.com/drtyhlpr/ > > rpi23-gen-image on a > > > Debian 10 Buster 64-bit system, and it got
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Hello James, Thanks a lot for the detailed response. I have gone through the logs and prepared a log report of the bugs and broken activities that I encountered. I will be trying to find fixes and continue working on them during the GSoC period. I would request you to review this and give your suggestions on how to fix these errors further. Thanks and Best Regards Simrann Arora GitHub Handle: @simrann20 On Fri, Mar 31, 2023 at 4:10 AM James Cameron wrote: > Thanks for testing. > > Some of the information we gave was out of date, please see the > changes in https://github.com/sugarlabs/sugar/commit/cc22632 > > The missing icon for the description is a known issue being tracked as > https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but nobody > seems to be working on it. > > Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy, > Write and Log may be found in .sugar/default/logs > > Please use copy and paste of terminal text rather than photographs or > screenshots. We cannot search them. > > On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote: > > Hi Mentors, > > > > Hope you all are doing great! > > > > I have tested Sugar on Raspberry Pi and I have prepared a report based > on my > > findings. I am attaching the same for your reference. I am trying to > fix these > > bugs and would request you all to review and give your suggestions on > how to > > fix these issues going forward. > > > > Thanks and Best Regards > > Simrann Arora > > GitHub Handle: @simrann20 > > * > > On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1]qu...@laptop.org> > wrote: > > > > G'day Simrann, > > > > Running Sugar on Raspberry Pi OS to identify what needs fixing will > be > > a good thing for Sugar Labs. It will also feed into and affect the > > other proposals and ideas. There is an opportunity to collaborate > > with many others. > > > > Your proposal could include a list of Raspberry Pi focused Linux > > distributions you have tested Sugar on, along with the broad > outcomes. > > > > On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote: > > > Hello James, > > > > > > Thanks for your quick response. > > > > > > From what I understand, `rpi23-gen-image` repository is old so it > cannot > > be > > > used for this project. > > > I think I should run Sugar on Raspberry Pi OS and identify what is > broken > > /bugs, > > > so I can work on fixing them during my GSoC period. > > > > > > I will also check out other debian image builders for Raspberry Pi > > which can be > > > leveraged to create Sugar OS images. > > > > > > I would also request my mentors @walterbender and @alexperez to > see if > > my > > > understanding is correct and also discuss the hardware > requirements to > > extend > > > the functionalities of existing activities like Turtle Blocks, > Measure, > > and > > > Pippy. > > > > > > Thanks and Best Regards > > > Simrann Arora > > > GitHub Handle: @simrann20 > > > * > > > On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1][2] > qu...@laptop.org> > > wrote: > > > > > > Hello Simrann, > > > > > > I've just now tested [2][3]https://github.com/drtyhlpr/ > > rpi23-gen-image on a > > > Debian 10 Buster 64-bit system, and it got past the debootstrap > > stage, > > > compiled a kernel, generated an image, but failed with > "losetup: > > > cannot find an unused loop device". I did not see an exec > format > > > error. The method was; > > > > > > ``` > > > apt install -y git debootstrap debian-archive-keyring > > qemu-user-static > > > binfmt-support dosfstools rsync bmap-tools whois git bc psmisc > dbus > > sudo > > > crossbuild-essential-armhf crossbuild-essential-armel bison > flex > > libssl-dev > > > git clone [3][4] > https://github.com/drtyhlpr/rpi23-gen-image.git > > > cd rpi23-gen-image > > > ./rpi23-gen-image.sh > > > ``` > > > > > > I suggest making sure you are using the operating system > versions > > > described in the README.md file, and the HEAD of the master > branch. > > > > > > Do not use the Sugar Labs fork of the repository, as it is > very old. > > > > > > Do engage with the rpi23-gen-image project; it is not part of > Sugar > > > Labs, and we have not used it for a while. Your problem with > > > debootstrap is best answered there, or by reading the > debootstrap > > > or Linux source code. > > > > > > I'm not a mentor for Google Summer of Code this year, but I've > a few > > > things to say. > > > > > > I doubt that rpi23-gen-image is suitable for your project. It > is for > > > making images. It is an external tool, and not part of the > workflow > >
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Thanks for testing. Some of the information we gave was out of date, please see the changes in https://github.com/sugarlabs/sugar/commit/cc22632 The missing icon for the description is a known issue being tracked as https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/465 but nobody seems to be working on it. Reasons for fail to start of Calculator, Image Viewer, Chat, Pippy, Write and Log may be found in .sugar/default/logs Please use copy and paste of terminal text rather than photographs or screenshots. We cannot search them. On Fri, Mar 31, 2023 at 03:14:12AM +0530, Simrann Arora wrote: > Hi Mentors, > > Hope you all are doing great! > > I have tested Sugar on Raspberry Pi and I have prepared a report based on my > findings. I am attaching the same for your reference. I am trying to fix > these > bugs and would request you all to review and give your suggestions on how to > fix these issues going forward. > > Thanks and Best Regards > Simrann Arora > GitHub Handle: @simrann20 > * > On Wed, Mar 29, 2023 at 2:10 AM James Cameron <[1]qu...@laptop.org> wrote: > > G'day Simrann, > > Running Sugar on Raspberry Pi OS to identify what needs fixing will be > a good thing for Sugar Labs. It will also feed into and affect the > other proposals and ideas. There is an opportunity to collaborate > with many others. > > Your proposal could include a list of Raspberry Pi focused Linux > distributions you have tested Sugar on, along with the broad outcomes. > > On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote: > > Hello James, > > > > Thanks for your quick response. > > > > From what I understand, `rpi23-gen-image` repository is old so it cannot > be > > used for this project. > > I think I should run Sugar on Raspberry Pi OS and identify what is > broken > /bugs, > > so I can work on fixing them during my GSoC period. > > > > I will also check out other debian image builders for Raspberry Pi > which can be > > leveraged to create Sugar OS images. > > > > I would also request my mentors @walterbender and @alexperez to see if > my > > understanding is correct and also discuss the hardware requirements to > extend > > the functionalities of existing activities like Turtle Blocks, Measure, > and > > Pippy. > > > > Thanks and Best Regards > > Simrann Arora > > GitHub Handle: @simrann20 > > * > > On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1][2]qu...@laptop.org> > wrote: > > > > Hello Simrann, > > > > I've just now tested [2][3]https://github.com/drtyhlpr/ > rpi23-gen-image on a > > Debian 10 Buster 64-bit system, and it got past the debootstrap > stage, > > compiled a kernel, generated an image, but failed with "losetup: > > cannot find an unused loop device". I did not see an exec format > > error. The method was; > > > > ``` > > apt install -y git debootstrap debian-archive-keyring > qemu-user-static > > binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus > sudo > > crossbuild-essential-armhf crossbuild-essential-armel bison flex > libssl-dev > > git clone [3][4]https://github.com/drtyhlpr/rpi23-gen-image.git > > cd rpi23-gen-image > > ./rpi23-gen-image.sh > > ``` > > > > I suggest making sure you are using the operating system versions > > described in the README.md file, and the HEAD of the master branch. > > > > Do not use the Sugar Labs fork of the repository, as it is very old. > > > > Do engage with the rpi23-gen-image project; it is not part of Sugar > > Labs, and we have not used it for a while. Your problem with > > debootstrap is best answered there, or by reading the debootstrap > > or Linux source code. > > > > I'm not a mentor for Google Summer of Code this year, but I've a few > > things to say. > > > > I doubt that rpi23-gen-image is suitable for your project. It is > for > > making images. It is an external tool, and not part of the workflow > > of either the Raspberry Pi Foundation, Debian Project, or Fedora > > Project. These projects use other tools to prepare their images, > > based on their package archives. > > > > Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry > > Pi OS already. > > > > Raspberry Pi OS does not include Sugar in the images, but it can be > > installed. This is because Raspberry Pi OS is based on Debian. > > > > The Fedora Sugar on a Stick images are available for Raspberry Pi. > > > > The number of organisations involved that are not Sugar Labs makes > > your project a challenge. Mentors working for Sugar Labs
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
G'day Simrann, Running Sugar on Raspberry Pi OS to identify what needs fixing will be a good thing for Sugar Labs. It will also feed into and affect the other proposals and ideas. There is an opportunity to collaborate with many others. Your proposal could include a list of Raspberry Pi focused Linux distributions you have tested Sugar on, along with the broad outcomes. On Wed, Mar 29, 2023 at 01:43:04AM +0530, Simrann Arora wrote: > Hello James, > > Thanks for your quick response. > > From what I understand, `rpi23-gen-image` repository is old so it cannot be > used for this project. > I think I should run Sugar on Raspberry Pi OS and identify what is > broken/bugs, > so I can work on fixing them during my GSoC period. > > I will also check out other debian image builders for Raspberry Pi which can > be > leveraged to create Sugar OS images. > > I would also request my mentors @walterbender and @alexperez to see if my > understanding is correct and also discuss the hardware requirements to extend > the functionalities of existing activities like Turtle Blocks, Measure, and > Pippy. > > Thanks and Best Regards > Simrann Arora > GitHub Handle: @simrann20 > * > On Tue, Mar 28, 2023 at 5:39 AM James Cameron <[1]qu...@laptop.org> wrote: > > Hello Simrann, > > I've just now tested [2]https://github.com/drtyhlpr/rpi23-gen-image on a > Debian 10 Buster 64-bit system, and it got past the debootstrap stage, > compiled a kernel, generated an image, but failed with "losetup: > cannot find an unused loop device". I did not see an exec format > error. The method was; > > ``` > apt install -y git debootstrap debian-archive-keyring qemu-user-static > binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus sudo > crossbuild-essential-armhf crossbuild-essential-armel bison flex > libssl-dev > git clone [3]https://github.com/drtyhlpr/rpi23-gen-image.git > cd rpi23-gen-image > ./rpi23-gen-image.sh > ``` > > I suggest making sure you are using the operating system versions > described in the README.md file, and the HEAD of the master branch. > > Do not use the Sugar Labs fork of the repository, as it is very old. > > Do engage with the rpi23-gen-image project; it is not part of Sugar > Labs, and we have not used it for a while. Your problem with > debootstrap is best answered there, or by reading the debootstrap > or Linux source code. > > I'm not a mentor for Google Summer of Code this year, but I've a few > things to say. > > I doubt that rpi23-gen-image is suitable for your project. It is for > making images. It is an external tool, and not part of the workflow > of either the Raspberry Pi Foundation, Debian Project, or Fedora > Project. These projects use other tools to prepare their images, > based on their package archives. > > Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry > Pi OS already. > > Raspberry Pi OS does not include Sugar in the images, but it can be > installed. This is because Raspberry Pi OS is based on Debian. > > The Fedora Sugar on a Stick images are available for Raspberry Pi. > > The number of organisations involved that are not Sugar Labs makes > your project a challenge. Mentors working for Sugar Labs can't easily > affect the other projects or make resources available for you. You > should ask your mentors to better define the scope, without creating > work dependencies on other organisations. > > Sugar on Raspberry Pi does have several bugs, and does not have > Raspberry Pi specific extensions. > > Fixing those bugs is a matter of either (a) fixing our software in a > Sugar Labs repository, (b) fixing packaging in the Fedora or Debian > Projects, and (c) waiting for the fixes to reach the released images. > That wait always exceeds the time available for Google Summer of Code. > > Adding features specific to the Raspberry Pi is important. For that, > you will need a Raspberry Pi, and electronics components and tools. > If you've worked on Arduino previously, this will be easy. You will > write software in Sugar Labs repositories, such as Turtle Blocks, > Measure, and Pippy. > > References: > > [4]https://arm.fedoraproject.org/ > [5]https://spins.fedoraproject.org/en/soas/ > [6]https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi > [7]https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md > [8]https://github.com/sugarlabs/sugar/blob/master/docs/rpi.md > [9]https://github.com/sugarlabs/sugar/blob/master/docs/debian.md > [10]https://wiki.sugarlabs.org/go/Raspberry_Pi > > On Tue, Mar 28, 2023 at 03:09:48AM +0530, Simrann Arora wrote: > > Hi Mentors, > > > > Hope you all are doing well! > > > > My name is Simrann Arora and I am an aspiring GSoC 2023
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Hello James, Thanks for your quick response. >From what I understand, `rpi23-gen-image` repository is old so it cannot be used for this project. I think I should run Sugar on Raspberry Pi OS and identify what is broken/bugs, so I can work on fixing them during my GSoC period. I will also check out other debian image builders for Raspberry Pi which can be leveraged to create Sugar OS images. I would also request my mentors @walterbender and @alexperez to see if my understanding is correct and also discuss the hardware requirements to extend the functionalities of existing activities like Turtle Blocks, Measure, and Pippy. Thanks and Best Regards Simrann Arora GitHub Handle: @simrann20 On Tue, Mar 28, 2023 at 5:39 AM James Cameron wrote: > Hello Simrann, > > I've just now tested https://github.com/drtyhlpr/rpi23-gen-image on a > Debian 10 Buster 64-bit system, and it got past the debootstrap stage, > compiled a kernel, generated an image, but failed with "losetup: > cannot find an unused loop device". I did not see an exec format > error. The method was; > > ``` > apt install -y git debootstrap debian-archive-keyring qemu-user-static > binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus sudo > crossbuild-essential-armhf crossbuild-essential-armel bison flex libssl-dev > git clone https://github.com/drtyhlpr/rpi23-gen-image.git > cd rpi23-gen-image > ./rpi23-gen-image.sh > ``` > > I suggest making sure you are using the operating system versions > described in the README.md file, and the HEAD of the master branch. > > Do not use the Sugar Labs fork of the repository, as it is very old. > > Do engage with the rpi23-gen-image project; it is not part of Sugar > Labs, and we have not used it for a while. Your problem with > debootstrap is best answered there, or by reading the debootstrap > or Linux source code. > > I'm not a mentor for Google Summer of Code this year, but I've a few > things to say. > > I doubt that rpi23-gen-image is suitable for your project. It is for > making images. It is an external tool, and not part of the workflow > of either the Raspberry Pi Foundation, Debian Project, or Fedora > Project. These projects use other tools to prepare their images, > based on their package archives. > > Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry > Pi OS already. > > Raspberry Pi OS does not include Sugar in the images, but it can be > installed. This is because Raspberry Pi OS is based on Debian. > > The Fedora Sugar on a Stick images are available for Raspberry Pi. > > The number of organisations involved that are not Sugar Labs makes > your project a challenge. Mentors working for Sugar Labs can't easily > affect the other projects or make resources available for you. You > should ask your mentors to better define the scope, without creating > work dependencies on other organisations. > > Sugar on Raspberry Pi does have several bugs, and does not have > Raspberry Pi specific extensions. > > Fixing those bugs is a matter of either (a) fixing our software in a > Sugar Labs repository, (b) fixing packaging in the Fedora or Debian > Projects, and (c) waiting for the fixes to reach the released images. > That wait always exceeds the time available for Google Summer of Code. > > Adding features specific to the Raspberry Pi is important. For that, > you will need a Raspberry Pi, and electronics components and tools. > If you've worked on Arduino previously, this will be easy. You will > write software in Sugar Labs repositories, such as Turtle Blocks, > Measure, and Pippy. > > References: > > https://arm.fedoraproject.org/ > https://spins.fedoraproject.org/en/soas/ > https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi > https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md > https://github.com/sugarlabs/sugar/blob/master/docs/rpi.md > https://github.com/sugarlabs/sugar/blob/master/docs/debian.md > https://wiki.sugarlabs.org/go/Raspberry_Pi > > On Tue, Mar 28, 2023 at 03:09:48AM +0530, Simrann Arora wrote: > > Hi Mentors, > > > > Hope you all are doing well! > > > > My name is Simrann Arora and I am an aspiring GSoC 2023 contributor. I > have > > been actively trying to contribute to the 'Sugar on Raspberry Pi' > project that > > has been selected for GSoC this year. As far as my progress is > concerned, till > > now I have completed the following tasks: > > - Setting up Debian version 11(bullseye) VM on my mac using Parallels > Desktop, > > earlier I had installed Ubuntu 23.04 using VMware Fusion > > - Cloning the rpi23-gen-image repo for building Sugar OS image. > > - I tried running the rpi23-gen-image builder script but I am getting > this > > error: > > ``` > > chroot: failed to run command '/debootstrap/debootstrap': Exec format > error. > > ``` > > > > I did some research to fix this, and found out that it might have > occured due > > to the architecture mismatch of the chroot environment and the command > that I > > am
Re: [Sugar-devel] Regarding the Sugar on Raspberry Pi project
Hello Simrann, I've just now tested https://github.com/drtyhlpr/rpi23-gen-image on a Debian 10 Buster 64-bit system, and it got past the debootstrap stage, compiled a kernel, generated an image, but failed with "losetup: cannot find an unused loop device". I did not see an exec format error. The method was; ``` apt install -y git debootstrap debian-archive-keyring qemu-user-static binfmt-support dosfstools rsync bmap-tools whois git bc psmisc dbus sudo crossbuild-essential-armhf crossbuild-essential-armel bison flex libssl-dev git clone https://github.com/drtyhlpr/rpi23-gen-image.git cd rpi23-gen-image ./rpi23-gen-image.sh ``` I suggest making sure you are using the operating system versions described in the README.md file, and the HEAD of the master branch. Do not use the Sugar Labs fork of the repository, as it is very old. Do engage with the rpi23-gen-image project; it is not part of Sugar Labs, and we have not used it for a while. Your problem with debootstrap is best answered there, or by reading the debootstrap or Linux source code. I'm not a mentor for Google Summer of Code this year, but I've a few things to say. I doubt that rpi23-gen-image is suitable for your project. It is for making images. It is an external tool, and not part of the workflow of either the Raspberry Pi Foundation, Debian Project, or Fedora Project. These projects use other tools to prepare their images, based on their package archives. Sugar is available for Raspberry Pi on Debian, Fedora, and Raspberry Pi OS already. Raspberry Pi OS does not include Sugar in the images, but it can be installed. This is because Raspberry Pi OS is based on Debian. The Fedora Sugar on a Stick images are available for Raspberry Pi. The number of organisations involved that are not Sugar Labs makes your project a challenge. Mentors working for Sugar Labs can't easily affect the other projects or make resources available for you. You should ask your mentors to better define the scope, without creating work dependencies on other organisations. Sugar on Raspberry Pi does have several bugs, and does not have Raspberry Pi specific extensions. Fixing those bugs is a matter of either (a) fixing our software in a Sugar Labs repository, (b) fixing packaging in the Fedora or Debian Projects, and (c) waiting for the fixes to reach the released images. That wait always exceeds the time available for Google Summer of Code. Adding features specific to the Raspberry Pi is important. For that, you will need a Raspberry Pi, and electronics components and tools. If you've worked on Arduino previously, this will be easy. You will write software in Sugar Labs repositories, such as Turtle Blocks, Measure, and Pippy. References: https://arm.fedoraproject.org/ https://spins.fedoraproject.org/en/soas/ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md https://github.com/sugarlabs/sugar/blob/master/docs/rpi.md https://github.com/sugarlabs/sugar/blob/master/docs/debian.md https://wiki.sugarlabs.org/go/Raspberry_Pi On Tue, Mar 28, 2023 at 03:09:48AM +0530, Simrann Arora wrote: > Hi Mentors, > > Hope you all are doing well! > > My name is Simrann Arora and I am an aspiring GSoC 2023 contributor. I have > been actively trying to contribute to the 'Sugar on Raspberry Pi' project that > has been selected for GSoC this year. As far as my progress is concerned, till > now I have completed the following tasks: > - Setting up Debian version 11(bullseye) VM on my mac using Parallels Desktop, > earlier I had installed Ubuntu 23.04 using VMware Fusion > - Cloning the rpi23-gen-image repo for building Sugar OS image. > - I tried running the rpi23-gen-image builder script but I am getting this > error: > ``` > chroot: failed to run command '/debootstrap/debootstrap': Exec format error. > ``` > > I did some research to fix this, and found out that it might have occured due > to the architecture mismatch of the chroot environment and the command that I > am using to run the script, like suppose the chroot environment is 64-bit and > the executable is 32-bit. Another reason could be that the executable is not > compatible with the OS or the linux distro within the chroot environment. > > - To fix this, I created a chroot environment of Debian version 9 (stretch) > within my Debian 11 distro to make it compatible with the `rpi3stretch-sugar` > template as given in the `rpi23-gen-image` repository and cloned it. > However, when I ran the script, I encountered the same error: > ``` > chroot: failed to run command '/debootstrap/debootstrap': Exec format error. > ``` > > To further troubleshoot this, I tried installing the `binfmts support` and > enabling qemu-arm within the chroot. > Again I got an error: `update-binfmts: warning: qemu-arm not in database of > installed binary formats. ` > > Now to fix this one I tried reinstalling qemu-user-static and enabling it but > it
