I’ve recently been trying to get Fedora working with the RPi’s sense expansion hat but have run into some issues. My first instinct was to play around with device tree overlays using /boot/efi/config.txt but have had no luck. I was wondering if anyone here has any insights into device tree overlays for the RPi that could help me out.
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(a)gmail.com> wrote:
>> Adding back Arm list.
>> On Wed, Oct 16, 2019 at 8:01 PM Garry Wakely <bristolgarry(a)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/Pre...
>> > 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?
I hope I wrote in the right place.
I've see that Fedora 31 now supports Rock64 sbc.
I've not found any guide to setup a sd card or any how-to boot Fedora 31 with it.
In addition, Hdmi does not works form me, nor serial console.
Any guide or how-to to follow?
If I look at Rock64 wiki page, i found images for Debian/Ubuntu/others, with a simple "dd image to your sd". And it works (serial console & hdmi too)!
Any way to do the same with Fedora? Really, i don't like too mutch @deb distros .
Hope someone can help me.
Does anyone have any suggestions on a dual ethernet SoC known to work with Fedora? I'm trying to throw a lab together on setting up a fedora router(already have a proof of concept running on an x86_64 tower) and I'd like to find an SoC to use that has dual ethernet. I found a few banana pi boards that appear nice but I'm not sure how suitable they'd be in terms of hardware compatibility:
Jaipur Car Rental offer excellent car hire service with low price. We have experienced and courteous drivers, along with new & clean fleets are the key aspects of Jaipur Car Rental Service. https://www.jaipurcarrental.org
We assure you that you are with the best car rental company in Jaipur, and we have achieved this title after providing great services to our guests. We personally invite you to visit our office and discuss about your requirements. It will be a pleasure of us delivering the best journey solutions for you. After all, what matters for us the most is your pleasant experience and sweet memories that you carry back home.
---------- Forwarded message ---------
From: Petr Pisar <ppisar(a)redhat.com>
Date: Mon, Nov 11, 2019 at 4:16 PM
Subject: pcre2-10.34-RC2 with AArch64 SIMD JIT
I've just pushed pcre2-10.34-RC2 into Fedora 32. Among some boring
featuring like Unicode 12.1.0 and matching in invalid UTF strings, now
the AArch64 JIT compiler uses NEON instructions for better performance.
It's a quite fresh new code and there were some issues with it that
I believe are resolved now.
If you find some strange behavior of PCRE2 on AArch64, let me know.
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
I'm currently in the process of trying to generate a new image with some
custom kickstarts for the raspberry pi. I'm basing these off of the
fedora-arm-minimal kickstart and I've sunk a bunch of time chasing anaconda
errors, I'm wondering if anyone has any insight into what I might be doing
wrong? Here's the output from livemedia-creator:
<mock-chroot> sh-5.0# . ./generate_raw_xz.sh flat-fedora.ks 30
2019-11-01 10:45:51,965: livemedia-creator v30.19-1
2019-11-01 10:45:51,967: selinux is Disabled
2019-11-01 10:45:52,642: disk_img = /var/lmc/lmc-disk-_fnubs4g.img
2019-11-01 10:45:52,643: Using disk size of 1994MiB
2019-11-01 10:45:52,648: Running anaconda.
2019-11-01 10:46:06,824: Starting installer, one moment...
2019-11-01 10:46:06,826: terminal size detection failed, using default width
2019-11-01 10:46:06,827: anaconda 30.25.6-4.fc30 for Linux 29 (pre-release)
2019-11-01 10:46:06,828: /var/run/anaconda.pid already exists, exiting
2019-11-01 10:46:07,324: Running anaconda failed: process '['unshare',
'--pid', '--kill-child', '--mount', '--propagation', 'unchanged',
'anaconda', '--kickstart', '/home/rpi/fedora-kickstarts/flat-fedora.ks',
'--cmdline', '--loglevel', 'debug', '--image',
'/var/lmc/lmc-disk-_fnubs4g.img', '--remotelog', '127.0.0.1:58155']' exited
with status 1
2019-11-01 10:46:52,779: Install failed: novirt_install failed
2019-11-01 10:46:52,781: ERROR: Image creation failed: novirt_install failed
2019-11-01 10:46:52,782: Image creation failed: novirt_install failed
I've also looked at other ways of going about this process including:
Which produced an image, but I wasn't able to get it to boot.