arm December 2020

arm@lists.fedoraproject.org

23 participants
17 discussions

f33 support for odroid N2+ (Amlogic S922X)
by Adrian Sevcenco 10 Aug '21

10 Aug '21

Hi! While theoretically should be possible, i would like to hear some confirmation that f33 can work on odroid N2 ... Moreover, if it can work, all i have to do is to write the image on eMMC, isn't it? Disclaimer: it's my first time playing in arm world, so many things are strange to me.. Thanks a lot!! Adrian

2 2

Enabled some openQA desktop tests on aarch64
by Adam Williamson 20 Jan '21

20 Jan '21

Hey folks! Just a heads up that I merged a branch I've had lying around for weeks that enables *some* of the openQA desktop tests on the aarch64 Workstation image. I left out some with known issues. desktop_notifications_postinstall needs to boot to runlevel 3, which is actually a bit tricky because of UEFI - we don't get the boot menu with a usable timeout and the trick we use to work around that on x86_64 (where we run the tests on BIOS) doesn't work on UEFI because the setting is in the UEFI vars which are not part of the main disk image. To fix this I think I need to have the 'image deploy' test upload its UEFI vars disk image and have the desktop_notifications_postinstall test attach that as well as the main disk image, but I need to look into the ins and outs of that a bit and this is my last work day of the year, so I'll do it next year. The desktop_login test is generally fragile (things tending to get stuck or time out), but if it gets that far, it *always* fails when it tests locking the screen; on aarch64 this seems to cause the VM to permanently stop updating the display, or something. Again I haven't had time to look into this, and I want to enable the other tests without waiting for it. The desktop_browser test is also failing, but I left that in because it's not a test bug, it's a distro bug. Firefox builds have just been disabled on aarch64 since 2020-11-20, so current composes don't have Firefox in them on aarch64 at all. There's a bug related to this: https://bugzilla.redhat.com/show_bug.cgi?id=1897675 which I just gave a bit of a bump, because it shouldn't really be acceptable to just turn off our default browser's build on one of our primary arches for weeks at a time :( This also breaks several of the other tests which use Firefox, like the Cockpit and FreeIPA browser tests. The tests should run on openQA prod from the next compose. The branch has been deployed on openQA lab (staging) for weeks (including the broken tests), so you can see how it's been behaving there. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 2

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

27 Dec '20

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2020-12-29 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/9880/

2 1

Help with Jetson Nano
by Richard Shaw 23 Dec '20

23 Dec '20

I was recently gifted a new Nvidia Jetson Nano in order to troubleshoot some aarch64 specific build problems as the test instances have not made it back online since the infra move. I used the following as a guide to update the firmware and install various Fedora images: https://nullr0ute.com/2020/11/installing-fedora-on-the-nvidia-jetson-nano/ I've run into a few problems: 1. Non-GUI flavors don't "boot". I never get a console. I thought something was wrong with the computer. 2. After giving up and trying the Fedora Workstation image I get the Welcome to Fedora 33! screen but none of my USB devices appear to work. I have a Logitech unifying receiver and even tried a hardwired bog-standard HP USB keyboard but nothing... At this point I'm stuck. Any suggestions? Thanks, Richard

3 7

Logging in after an install
by Sam Varshavchik 22 Dec '20

22 Dec '20

I put it aside for a few months, but I picked up my attempt to get Fedora up and running on a PI 3B. I used arm-image-installer to install the F32 image I prepared: fedora-arm-image-installer --image=Fedora-Workstation-32-1.6.aarch64.raw.xz --media=/dev/sdc --target=rpi3 --resizefs --norootpass The PI boots up until the message, this is the last message that appears on the console: fb0: switching to vc4drmfb from EFI VGA No more messages appear, no console login. But there is apparently a new DHCP assignment on my network. However ssh-ing to that IP address prompts for the root password, and it does not accept an empty password. I suppose I could pull the SD card out, mount it, and copy over an ssh into /root, but what exactly did --norootpass do, and what about not being able to log in through the console? I didn't have a keyboard attached yet, I would think I'd get at least a prompt.

3 4

NanoPC-T4 from FriendlyARM
by Andreas Reschke 22 Dec '20

22 Dec '20

Hello together, I've found small information about running Fedora 29 on a NanoPC-T4, nothing more up2date. It's possibel to install actual Fedora 33 on this SBC? The NanoPC-T4 does fit all my request. Thanks Andreas

1 0

gfx/2d/BlurNEON.cpp error when build IceCat on ARM
by Antonio T. sagitter 20 Dec '20

20 Dec '20

Hi all. I can't compile IceCat on ARM-Rawhide branch (it's an issue related to GCC-11?) because of this error: 167:32.34 /usr/lib/gcc/armv7hl-redhat-linux-gnueabi/11/include/arm_neon.h: In function ‘poly64x1_t vcreate_p64(uint64_t)’: 167:32.34 /usr/lib/gcc/armv7hl-redhat-linux-gnueabi/11/include/arm_neon.h:6534:22: error: ‘__builtin_neon_vcreatedi’ was not declared in this scope; did you mean ‘__builtin_neon_vextdi’? 167:32.34 6534 | return (poly64x1_t)__builtin_neon_vcreatedi ((__builtin_neon_di) __a); I don't know if it's caused by a compiler flag (-mfpu=neon) conflicts. Build log: https://kojipkgs.fedoraproject.org//work/tasks/3471/57863471/build.log -- --- Antonio Trande Fedora Project mailto: sagitter(a)fedoraproject.org GPG key: 0x29FBC85D7A51CC2F GPG key server: https://keys.gnupg.net/

2 1

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

20 Dec '20

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2020-12-22 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/9880/

2 1

Support for Raspberry PI 4
by Rafael Leiva-Ochoa 18 Dec '20

18 Dec '20

Hi Everyone, I have been testing F33 on Raspberry Pi 4 8GB and seems to be booting fine, but it is still very unstable. I have been reading the Fedora Meetbot meeting notes, and monitoring the Wiki for updates, but still no updates on the Wiki since Oct of this year. On which Fedora version will Raspberry PI 4 be officially supported? I think the last thing I read on the Fedora Meetbot was kernal updates were holding it back. Any updates on this? Thanks, Rafael

8 10

Fedora ARM and AArch64 Status Meeting Minutes 2020-12-15
by Paul Whalen 15 Dec '20

15 Dec '20

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2020-12-15/fedora_arm_an… . Meeting summary --------------- * roll call (pwhalen, 15:00:38) * 1) ==== Userspace Status ==== (pwhalen, 15:03:48) * No new issues reported. (pwhalen, 15:06:01) * 2) ==== Kernel Status ==== (pwhalen, 15:06:10) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1907945 is the bug, and yes, I verified the same srpm for 5.10 does build in koji against f33 (jforbes, 15:10:41) * Issues building the latest 5.10 kernel with GCC11 - https://bugzilla.redhat.com/show_bug.cgi?id=1907945 (pwhalen, 15:12:29) * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=57446012 is the scratch build I did yesterday for aarch64 on f33, if anyone needs it (jforbes, 15:14:22) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:16:42) * 3) ==== Bootloader Status ==== (pwhalen, 15:17:04) * 4) ==== Fedora 34 ==== (pwhalen, 15:20:31) * OpenQA Testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhi… (pwhalen, 15:20:41) * 5) == Open Floor == (pwhalen, 15:26:37) * Fedora ARM meetings to resume in 2021 - next meeting scheduled for January 5th, 2021. (pwhalen, 15:29:11) (meeting date corrected) Meeting ended at 15:33:30 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (39) * jforbes (16) * pbrobinson (14) * defolos (12) * jlinton (10) * zodbot (6) * coremodule (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm December 2020