arm August 2020

arm@lists.fedoraproject.org

10 participants
15 discussions

The server images are not working with Fedora 31
by Peter Hjalmarsson 04 Aug '20

04 Aug '20

Hi, Just wanted to point out that due to U-Boot not supporting XFS, and Fedora Server has moved to a XFS /boot, the current images as https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Server/aarch64/im… does not boot on any system using U-Boot, like for example the raspberry pi. Best Regards, Peter Hjalmarsson

3 5

CMA on raspberry pi 4
by Thomas H.P. Andersen 04 Aug '20

04 Aug '20

Hi, I have looked into the CMA setting issue a bit. This is what I have found so far. The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is the only area that the peripherals on the rpi4 can address. The DT sets the allowed range to allocate the CMA from ( arch/arm/boot/dts/bcm2711.dtsi#L869 <https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/bcm2711.dts…>), but it seems to not work here. What does work is instead to set the offset manually. I replaced "cma=256MB" with "cma=256M@704M" and then it boots. Note that it has to be 256M instead of 256MB. Removing the cma option on the command line was known as a workaround. Without that we would fall back to the build config of 64MB cma which was located at offset 0x38000000. This left 64MB at the end of ZONE_DMA, and I chose offset 704M so that those 64MB would still be free. Not sure if that is needed or not. The crashkernel needs to be in ZONE_DMA as well but it seems to be set to 0 size. I have tested on 5.7 rc2 from rawhide. This probably belongs in a bug report. What would be the correct place to file that? From what I can tell upstream has been tested with cma settings without problems (as long as the requested CMA size can fit in ZONE_DMA). From that it seems like fedora-specific issue. Not sure though. Cheers, Thomas

4 17

aarch64 mock gcc/annobin errors
by Sam Varshavchik 03 Aug '20

03 Aug '20

I'm running an F32 aarch64 guest qemu VM on an x86_64 F32 host, and, in that VM, I attempted to build something fairly simple via mock. This is my reward: configure:3590: gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,- D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector- strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 - specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables - fstack-clash-protection -Wl,-z,relro -Wl,--as-needed -Wl,-z,now - specs=/usr/lib/rpm/redhat/redhat-hardened-ld conftest.c >&5 annobin: conftest.c: AArch64: The annobin plugin is out of date with respect to gcc *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event | Plugins PLUGIN_FINISH_UNIT | annobin: Generate final annotations PLUGIN_START_UNIT | annobin: Generate global annotations PLUGIN_ALL_PASSES_START | annobin: Generate per-function annotations PLUGIN_ALL_PASSES_END | annobin: Register per-function end symbol conftest.c:1: internal compiler error: Segmentation fault First time I've seen something like that, any idea what to do here, for this? This if from a first build in mock, which presumably pulled in the most recent versions of all rpms into the chroot.

2 1

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 02 Aug '20

02 Aug '20

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2020-08-04 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9431/

1 0

Fedora 32 Raspberry pi 4 status
by pvlcek 01 Aug '20

01 Aug '20

Hi, my name is Pavel, I am blind so I use screen reader and I work in redhat 4 years as intern software engineer. I am interested in accessibility for blind and visually impaired users. I get Raspberry 4 as a present and I want to know, if I can install Fedora 32 Workstation or Fedora 32 Mate into it? One wiki web says no (https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Supported_Har…) second yes or maybe (https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms) so could you tell me please, which information is correct? If beta testers needed, I can do it in my free time. Thanks, Pavel

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm August 2020