March 2021 - arm - Fedora Mailing-Lists

f33 support for odroid N2+ (Amlogic S922X)

by Adrian Sevcenco

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 years, 1 month

2
2
0 / 0

Fedora on Librem 5: is it possible?

by Massi Ergosum

Hello folks! I just got my Librem 5, after a long time. I know that is not a priority (from [1]): "We don't directly support devices such as phones and tablets but it's not to say that without the required kernel/bootloader know how that they don't work, it's just not our primary focus." But, do you think is it possible to get a working Fedora on this device? Cheers Massimiliano [1] https://fedoraproject.org/wiki/Architectures/ARM

2 years, 5 months

4
10
0 / 0

Problem booting Pine A64+

by Gerhard Wiesinger

Hello, I tried to move from Ubuntu to Fedora (33 and 34 Beta 1) but Linux doesn't boot: Installer commands for F33 oder F34Beta1:: fedora-arm-image-installer --image=Fedora-Server-33-1.3.aarch64.raw.xz --target pine64_plus --media=/dev/sdb --addkey ~/.ssh/authorized_keys --norootpass --relabel --resizefs -y fedora-arm-image-installer --image=Fedora-Server-34_Beta-1.3.aarch64.raw.xz --target pine64_plus --media=/dev/sdd --addkey ~/.ssh/authorized_keys --norootpass --relabel --resizefs -y Error messages are the same on F33 and F34Breta1. Any ideas? Thnx. Ciao, Gerhard U-Boot SPL 2021.04-rc2 (Feb 16 2021 - 00:00:00 +0000) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.4(release): NOTICE: BL31: Built : 20:42:48, Nov 17 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x4095f18, model: Pine64+ NOTICE: PSCI: System suspend is unavailable U-Boot 2021.04-rc2 (Feb 16 2021 - 00:00:00 +0000) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: Pine64+ DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface10 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found EFI removable media binary efi/fedora/grubaa64.efi ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** 2680304 bytes read in 119 ms (21.5 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@1c0f000.blk... ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** Found 4 disks No EFI system partition Booting /efi\fedora\grubaa64.efi ethernet@1c30000 Waiting for PHY auto negotiation to complete....... done Fedora (5.11.3-300.fc34.aarch64) 34 (Server Edition Prerelease) System setup Use the and keys to change the selection. Press 'e' to edit the selected item, or 'c' for a command prompt. Press Escape to return to the previous menu. The selected entry will be started automatically in 0s. EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EHCI failed to shut down host controller.

2 years, 5 months

3
3
0 / 0

Nvidia Jetson Nano GPIO?

by Richard Shaw

I have a Jetso Nano running Fedora 33 following this guide: I want to use it to play with home automation and I have node-red installed and have hacked together a node based on the Rpi GPIO node for the Jetson. I have copied the udev rules into /etc/udev/rules.d but I don't see the devices, there is no /sys/class/gpio. I changed the udev loglevel to info and see: Mar 30 07:21:29 pulseaudio[1243]: Failed to find a working profile. Mar 30 07:21:29 pulseaudio[1243]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-70030000.hda" card_name="alsa_card.platform-70030000.hda" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=n> Mar 30 07:21:29 upowerd[698]: treating change event as add on /sys/devices/platform/70030000.hda/sound/card0/input1 Mar 30 07:21:29 pulseaudio[1243]: Failed to find a working profile. Mar 30 07:21:30 pulseaudio[1243]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-70030000.hda" card_name="alsa_card.platform-70030000.hda" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=n> Mar 30 07:21:30 pulseaudio[1243]: Failed to find a working profile. Mar 30 07:21:30 pulseaudio[1243]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-70030000.hda" card_name="alsa_card.platform-70030000.hda" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=n> Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb1 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb2 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb1/1-0:1.0 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb1/1-2 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb2/2-1 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb1/1-2/1-2:1.0 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb2/2-0:1.0 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70090000.usb/usb2/2-1/2-1:1.0 Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) config/udev: Adding input device jetson-nano-hda HDMI/DP,pcm=3 (/dev/input/event1) Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) No input driver specified, ignoring this device. Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) This device may have been added with another device file. Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/70030000.hda/sound/card0/input1/event1 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/gpio-keys/input/input0 Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/virtual/input/mice Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) config/udev: removing device gpio-keys Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) Option "fd" "35" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: device removed Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) UnloadModule: "libinput" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) systemd-logind: releasing fd for 13:64 Mar 30 07:21:30 systemd-udevd[3107]: Using default interface naming scheme 'v245'. Mar 30 07:21:30 systemd-logind[749]: Watching system buttons on /dev/input/event0 (gpio-keys) Mar 30 07:21:30 upowerd[698]: treating change event as add on /sys/devices/platform/gpio-keys/input/input0/event0 Mar 30 07:21:30 systemd-udevd[3116]: Using default interface naming scheme 'v245'. Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) config/udev: Adding input device gpio-keys (/dev/input/event0) Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) gpio-keys: Applying InputClass "evdev keyboard catchall" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) gpio-keys: Applying InputClass "libinput keyboard catchall" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) gpio-keys: Applying InputClass "system-keyboard" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) Using input driver 'libinput' for 'gpio-keys' Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 35 paused 0 Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) gpio-keys: always reports core events Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) Option "Device" "/dev/input/event0" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) Option "_source" "server/udev" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: is tagged by udev as: Keyboard Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: device is a keyboard Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: device removed Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys/input/input0/event0" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) XINPUT: Adding extended input device "gpio-keys" (type: KEYBOARD, id 6) Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (**) Option "xkb_layout" "us" Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: is tagged by udev as: Keyboard Mar 30 07:21:30 /usr/libexec/gdm-x-session[1077]: (II) event0 - gpio-keys: device is a keyboard Mar 30 07:21:30 /usr/libexec/gdm-x-session[3157]: The XKEYBOARD keymap compiler (xkbcomp) reports: Mar 30 07:21:30 /usr/libexec/gdm-x-session[3157]: > Internal error: Could not resolve keysym XF86FullScreen Mar 30 07:21:30 /usr/libexec/gdm-x-session[3157]: Errors from xkbcomp are not fatal to the X server Mar 30 07:21:30 pulseaudio[1243]: Failed to find a working profile. Mar 30 07:21:30 pulseaudio[1243]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-70030000.hda" card_name="alsa_card.platform-70030000.hda" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB= Any tips? Or am I stuck running Nvidia's linux for it to work? Thanks, Richard

2 years, 5 months

3
5
0 / 0

Where can I find tests to run for F34 Server on Aarch 64?

by Zach Villers

Apologies if I've been lazy at googling, but are there tests that can be run for F34 aarch 64?

2 years, 5 months

3
2
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by pwhalen＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2021-03-30 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.o... Source: https://apps.fedoraproject.org/calendar/meeting/9910/

2 years, 5 months

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by pwhalen＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2021-03-23 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.o... Source: https://apps.fedoraproject.org/calendar/meeting/9910/

2 years, 6 months

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by pwhalen＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2021-03-16 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.o... Source: https://apps.fedoraproject.org/calendar/meeting/9910/

2 years, 6 months

1
0
0 / 0

Fedora ARM & AArch64 Status Meeting Minutes 2020-03-09

by Paul Whalen

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:54 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2021-03-09/fedora_arm_... . Meeting summary --------------- * roll call (pwhalen, 15:00:54) * 1) ==== Userspace Status ==== (pwhalen, 15:04:50) * No reported issues. (pwhalen, 15:06:18) * 2) ==== Kernel Status ==== (pwhalen, 15:06:32) * LINK: https://communityblog.fedoraproject.org/contribute-to-fedora-kernel-5-11-... (jlinton, 15:07:26) * Kernel Test week - https://fedoraproject.org/wiki/Test_Day:2021-03-08_Kernel_5.11_Test_Week (pwhalen, 15:07:37) * kernel-5.11.4-300.fc34 (pwhalen, 15:11:14) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1720360 (pwhalen, 15:11:14) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:13:50) * 3) ==== Bootloader Status ==== (pwhalen, 15:13:57) * uboot-tools-2021.04-0.3.rc2.fc34 (pwhalen, 15:14:06) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1711269 (pwhalen, 15:14:06) * grub2-2.04-38.fc34 (pwhalen, 15:16:41) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1719496 (pwhalen, 15:16:41) * uboot-tools-2021.04-0.4.rc3.fc35 (pwhalen, 15:20:38) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1720629 (pwhalen, 15:20:47) * 4) ==== Fedora 34 ==== (pwhalen, 15:21:25) * Latest nominated compose (pwhalen, 15:21:36) * LINK: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test (pwhalen, 15:21:36) * Raspberry Pi 3B+ boots incredibly slow after CPU failed to come online errors (pwhalen, 15:22:36) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1921924 (pwhalen, 15:22:36) * [abrt] gnome-shell: nouveau_fence_signalled(): gnome-shell killed by SIGSEGV (pwhalen, 15:23:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1930977 (pwhalen, 15:23:41) * Accepted F34 Beta Blocker (pwhalen, 15:23:41) * F34 Beta Blockers and Freeze Exceptions - https://qa.fedoraproject.org/blockerbugs/milestone/34/beta/buglist (pwhalen, 15:25:38) * Latest Raspberry Pi Firmware (bcm283x-firmware-20210225-1.5985247.fc34) fixes sound on the Raspberry Pi 4, but need the UART line uncommented to boot. (pwhalen, 15:28:15) * Beta Release (Preferred Target) - 2021-03-16 (pwhalen, 15:30:10) * 5) == Open Floor == (pwhalen, 15:35:17) Meeting ended at 15:38:00 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (52) * pbrobinson (10) * jlinton (9) * zodbot (6) * rcbaus_ (1) * coremodule (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

2 years, 6 months

1
0
1 / 0

Raspberry Pi 4 support

by Ondřej Budai

Hello guys, is Raspberry Pi 4 officially supported by Fedora? Both docs[1] and wiki[2] don't mention Pi 4 as supported. The wiki even says that "We do not (as of 30th October 2019) support the Raspberry Pi 4 in any Fedora release."[3] On the other hand, I tried writing a Fedora image onto an SD card and booting an RPI 4 from it and it worked flawlessly. So maybe the docs and wiki are just outdated? Cheers, Ondřej [1]: https://docs.fedoraproject.org/en-US/quick-docs/raspberry-pi/ [2]: https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Prerequisites [3]: https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4

2 years, 6 months

3
3
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2021