[Sugar-devel] F30 ARM (Raspberry Pi) SoaS not working, but a fix exists..

Alex Perez aperez at alexperez.com
Mon May 20 16:16:03 EDT 2019

James Cameron wrote on 5/19/19 3:50 PM:
> That's unfortunate.
Agreed, but it was due to a lack of testing.
> Were the Fedora 30 ARM builds being tested before release?
They were, but only in QEMU, it would seem. The temporary workaround is 
to fetch the initramfs referenced below, and then, after imaging the 
image to an SD card using $preferredImagingMethod (Fedora Image Writer, 
for most folks, would be their best bet), just copy the downloaded 
initrd over to the boot partition on the SD card.
> Are the Fedora 31 ARM builds being tested?
I am informed by pwhalen that, as of today, the image is still broken in 
rawhide (which will become F31) but that it will be fixed in the coming 
days/weeks, now that there's a bug for the issue:


> On Sun, May 19, 2019 at 09:01:25AM -0700, Thomas Gilliard wrote:
>> Current f30 soas release for a Rpi3B+ (arm) do not boot [1]
>> There is a solution:
>>   "if you replace the initramfs with this one - [1]https://fedorapeople.org/
>> ~pwhalen/soas/initramfs-5.0.9-301.fc30.armv7hl.img ...it will boot." <pwhalen>
>> on #fedora-arm
>> Hopefully this can be fixed in a rebuild for f30 arm
>> Tom Gilliard
>> satellit on freenode #fedora-qa
>> [1] [2]https://wiki.sugarlabs.org/go/Fedora_30#not_working
>> References:
>> [1] https://fedorapeople.org/~pwhalen/soas/initramfs-5.0.9-301.fc30.armv7hl.img
>> [2] https://wiki.sugarlabs.org/go/Fedora_30#not_working
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the Sugar-devel mailing list