Hi Peter - My apologies about getting your name wrong.  :/

Thank you very much for your help - this project is for the Bristol Public library, so you are not just helping me, you are helping the community of Bristol TN/VA.  :)

Thanks again,

Garry Wakely

On Fri, Oct 18, 2019 at 5:17 AM Peter Robinson <pbrobinson@gmail.com> wrote:
Please leave the Arm list on the replies.

My name is Peter.

I've emailed the sugar list to see if they're aware of the F-31
problem and asked them to resolve it if so.


> Hi Paul - Thank you very much for the suggestion to move to the 31 pre-release.  It is getting us much closer, but not all the way there yet.
> With the 31 pre-release, installed following the same directions as earlier in this thread, the system boots up, asks for an Admin name and password, user name and password, finishes configuration, then goes to the login page.  Upon entering the login information, the system reboots itself.  :/  So close!
> Does there happen to be a stable 29 release for the Pi 3b+ ?  I could not find it in numerous searches today.
> Thanks again,
> Garry Wakely
> On Wed, Oct 16, 2019 at 5:48 PM Peter Robinson <pbrobinson@gmail.com> wrote:
>> Adding back Arm list.
>> On Wed, Oct 16, 2019 at 8:01 PM Garry Wakely <bristolgarry@gmail.com> wrote:
>> >
>> > Hi Peter - It is the Fedora-SoaS-armhfp-30-1.2-sda version downloaded this morning from here: https://arm.fedoraproject.org/
>> > It was installed according to the directions here: https://docs.fedoraproject.org/en-US/fedora/f30/install-guide/install/Preparing_for_Installation/#sect-preparing-boot-media
>> > and installed using the Fedora Media Writer.
>> There was a known issue with the F-30 release. I would give one of the
>> F-31 pre-releases out as I believe they should be much better.
>> >>
>> >> > Hi Folks - I am trying to set up Sugar On A Stick for Raspberry Pi 3+, but am running into a boot issue.  The boot process runs properly until it gets to "Reached Target Basic System", and then it hangs at
>> >> > "A start job is running for dev/dis...1fe03C48" at which point there is no further progress.  Has anyone else had a problem like this, and if so, what is your workaround/solution?
>> >>
>> >> What release?