I am running Fedora 31, aarch64 release on many Raspberry PI 3B+.
I have exactly the same behaviour with all the RPIs.
When trying to access a NFS server ( perfectly working with my laptops
running fedora X86) with a ls command when a huge transfer is on going,
I have a lot of "NFS server not responding" in journal and ls is hanged.
I tried to replace the onboard ethernet card with a USB 1GB ethernet and
I don't have this issue at all.
I also tried to change port on the switch with the same result ( not
working with on board card, working with USB one)
I also had such network issue with Fedora 30.
Are you aware of such a behavior, if not I will open an issue.
I have been trying to boot Fedora on a Khadas VIM3 Pro board. It is now booting Fedora 31 with version 5.4.2 kernel.
To make it run the following changes was needed:
1. Mainline u-boot compiled after the recipe at https://gitlab.denx.de/u-boot/u-boot/blob/master/board/amlogic/w400/READM... - whether the fedora provided one also works I do not know. The recipe says that some firmwares are needed for the board.
Beyond the recipe, I have added a couple of patches from the fedora u-boot, to find the right file to boot.
2. The U-boot is too large (1.1M) to fit in before the first FAT partition starts. So I added some more space before to not destroy the beginning of the FAT partition.
3. The fedora kernel has CONFIG_PWM_MESON=m instead of CONFIG_PWM_MESON=y. This causes an other clock setup than intended, so a needed clock is stopped, unless clk_ignore_unused is added as kernel boot parameter. Using clk_ignore_unused it boots, but cpufreq and others are not setup correct. CONFIG_PWM_MESON=y is the preferred fix for now.
I would like some input on how to include this in Fedora?
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?