arm May 2024

arm@lists.fedoraproject.org

7 participants
9 discussions

Raspberry Pi 4 issues with Fedora Rawhide
by Lukas Brabec 24 Jun '24

24 Jun '24

Hi all, I am writing this email to raise awareness well ahead of the F41 branching on August 6 about the bugs I found while running Fedora Rawhide on the RPi 4. I have proposed these bugs as blockers for the F41 release: * gnome-initial-setup: Choosing avatar results in SetIconFile call failed for unknown reason [0] I proposed this as F41 Final blocker, but this is fairly minor bug and I can imagine that we would waive it if not fixed and create a common issue. * gsk: vulkan renderer breaks gtk4 apps on Raspberry Pi 4 and 400 [1] GSK now defaults to vulkan and it causes problems on RPi, I initially encountered crashing gnome-initial-setup (and later that all GTK4 apps are crashing upon startup). Thus I proposed it as a F41 Beta blocker. This crashing on app startup will be resolved in the next GTK release, the fix is already merged. However, there are still issues with GTK4 apps [2], all related to vulkan renderer [3] [4] [5]. It is not yet clear if the problems are bugs in GTK or mesa. In the end, if proven difficult to fix, we could always switch back to older renderer as suggested by Adam during F40 cycle [6]. * Raspberry Pi 4 won't wake up from suspend [7] Although we don't have a criterion for suspend, I proposed this as a blocker bug. I cannot login every time I keep Raspberry Pi idling for 15 minutes and I have to restart it, this could also lead to loss of data. This is something different compared to the x86_64 situation. On x86_64 we probably wouldn't block on suspend on some particular hardware configuration, but I think we should block here since we support only a handful of ARM boards. Also, suspend on Raspberry Pi OS is disabled, so I'm not sure if suspend on Raspberry Pi is something we even want in Fedora. [0] https://bugzilla.redhat.com/show_bug.cgi?id=2278845 [1] https://bugzilla.redhat.com/show_bug.cgi?id=2282171 [2] https://gitlab.gnome.org/GNOME/gtk/-/issues/6726#note_2121079 [3] https://gitlab.gnome.org/GNOME/gtk/-/issues/6743 [4] https://gitlab.gnome.org/GNOME/gtk/-/issues/6744 [5] https://gitlab.gnome.org/GNOME/gtk/-/issues/6745 [6] https://gitlab.gnome.org/GNOME/gtk/-/issues/6498#note_2063629 [7] https://bugzilla.redhat.com/show_bug.cgi?id=2283978 --- L.

4 6

Fedora on Rock 5B
by Andreas Reschke 11 Jun '24

11 Jun '24

Hi there, I've tried to install Fedora on my Rock 5 without success. Booting with https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5… on SD-Card and source from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everythin…. Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # # Full log file: see rock.txt Has anybody more succcess ? Greetings Andreas

3 10

Fedora ARM Weekly Meeting Cancelled - 28 May 2024
by Geoffrey Marr 28 May '24

28 May '24

Hi all, I have a conflict this morning and am cancelling the ARM meeting. If someone would like to run the meeting, feel free. Otherwise we will plan on meeting next week. Geoff Marr IRC: coremodule

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 27 May '24

27 May '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-05-28 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 20 May '24

20 May '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-05-21 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 13 May '24

13 May '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-05-14 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

Fedora 40 and Helios64 => success
by Dan Horák 10 May '24

10 May '24

Hi all, after couple years of sitting under the desk I have thought it's time to try Fedora on Helios64. There was progress in mainline kernel regarding the hardware support in the past year or two, so why not to give it a try. There is no mainline u-boot support for Helios64, thus the idea was to use Armbian's u-boot, which should support EFI boot, combined with Fedora minimal disk image. After some head scratching and resolving 2 issues I got the login prompt. First issue is that Armbian's u-boot is bigger than 1 MB, thus our disk layout, where the first partition (EFI) starts at 9 MB, means it gets overwritten a bit. Solution was to shift all partitions 1 MB further. Perhaps we should default to the 10 MB in the official images too. Second issue was a crash quite late in the boot in cpu_idle() for CPU #5, which seems to be the low-power core. Workaround was to limit the number of cpus to 4 using kernel's maxcpus= parameter. The result is [dan@helios64 ~]$ sudo dmesg | head [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.8.5-301.fc40.aarch64 (mockbuild@5efd934e27f44ed09084502b9de5d773) (gcc (GCC) 14.0.1 20240328 (Red Hat 14.0.1-0), GNU ld version 2.41-34.fc40) #1 SMP PREEMPT_DYNAMIC Thu Apr 11 20:30:05 UTC 2024 [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: Helios64 [ 0.000000] efi: EFI v2.9 by Das U-Boot [ 0.000000] efi: RTPROP=0xf4ece040 SMBIOS=0xf4ecd000 MOKvar=0xf4da0000 MEMRESERVE=0xf4d97040 [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000f7ffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xf755c2c0-0xf7572fff] [ 0.000000] Zone ranges: With regards, Dan

1 0

RPi Kernel memory leak leads to OOM killer running on idle system.
by Barry Scott 09 May '24

09 May '24

A number of us are seeing a reproducible kernel memory leak on RPi. There is a bug https://bugzilla.redhat.com/show_bug.cgi?id=2279327 and a thread in discuss about it with additional details: https://discussion.fedoraproject.org/t/high-memory-usage-in-f40-on-rpi-4-un… Kernel 6.5.6 does not have a leak, but current kernels do. Anyone know if this is being looked at? Barry

2 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 06 May '24

06 May '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-05-07 from 15:00:00 to 16:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm May 2024