arm

arm@lists.fedoraproject.org

6644 discussions

Start a nNew thread

CPU temperature
by David Legg 21 Jan '26

21 Jan '26

Is there a way of monitoring CPU temperature for Fedora aarch64 RPI 5 yet, please?

2 1

RPI5 headless Fedora 43 build updates etc.
by David Legg 14 Jan '26

14 Jan '26

So, thanks to Peter Robinson for providing this FC43 image: https://discussion.fedoraproject.org/t/initial-minimal-fedora-image-for-ras… I installed it on my 2022 RPI5 and dropped in a copy of the missing |/etc/sysconfig/kernel file as per Simon de Vlieger's comment lower down on the same page:| |<code>| |# UPDATEDEFAULT specifies if kernel-install should make # new kernels the default UPDATEDEFAULT=yes # DEFAULTKERNEL specifies the default kernel package type DEFAULTKERNEL=kernel-core </code>| |I updated the FC43 with a dnf update to the latest Fedora 43 - aarch64 and Copr repo for a64-kernel (owned by pbrobinson).| |The RPI5 now boot with an updated kernel by default:| |<code>| |Linux nas5 6.18.3-200.fc43.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Jan 2 20:14:24 UTC 2026 aarch64 GNU/Linux </code> which is great.| |I was able to turn my 5V fan on using:| |gpioset -z -c gpiochip4 17=1| |So, things are looking pretty positive for building a headless NAS with a couple of RAIDed SATA disks. I have a few questions, though.| |1. Doing init 0 or init 6 does nothing except cause the message 'Excess arguments.' to appear in the debug/UART console. systemctl reboot works fine, but should I be worried about that error message?| |2. The command gpioinfo shows that all the 400 pin header signals have moved to:| |gpiochip4 - 54 lines: line 0: unnamed input line 1: unnamed input line 2: unnamed input line 3: unnamed input line 4: unnamed input line 5: unnamed input line 6: unnamed input line 7: unnamed input line 8: unnamed input line 9: unnamed input line 10: unnamed input line 11: unnamed input line 12: unnamed input line 13: unnamed input line 14: unnamed input line 15: unnamed input line 16: unnamed input line 17: unnamed output consumer="gpioset"| |etc.| |The naming of GPIOs seems to be broken. I'm nto sure if this matters at all. Obviously, my previous commands like this no longer work:| |gpioset -z -c gpiochip4 GPIO17=1| |And gpiochip0 has changed to gpiochip4, of course. But the functionality seems ok.| |Is the user interface to libgpiod stable, or is it likely to change in the near future?| |3. Is booting from an NVMe on the PCIe interface likely to work in the near future? This would be a great improvement on having to use uSD cards.| |Anyway, many thanks to those who have worked so hard to get FC43 aarch64 on RPI5 this far.| |:D| | |

1 1

Call for Fedora 44 Test Days
by awilliam＠redhat.com 06 Jan '26

06 Jan '26

The Fedora 44 schedule [1] is winding up, and it's time we started thinking about what we'd want to have test days for. There are several changes accepted already for F44, and the window for proposals is still open so more may come. You can find the list of accepted Changes here: http://fedoraproject.org/wiki/Releases/44/ChangeSet Please take some time and look through the list and see if there's anything you'd be interested in testing - or if there's something you think should get some testing that isn't in the ChangeSet! For those of you not familiar with them, test days are online events aimed at testing a specific feature of an upcoming Fedora release. We organize the event in a ticket, provide a Wiki page with instructions, and have a page on the testdays webapp [2] for reporting results. During the event, folks can compare notes and ask for help in the Matrix chat room [3]. Anyone can request to host test days or request that the QA team help you out with organizing. Test days can be run for any feature or area of a distribution that focused testing would be useful for. We use the name "test days" as it's been around for a while, but many events run for more than a single day, now, to allow more time for folks to test. More information on test days can be found in the wiki [4]. To propose a test day, file a ticket on Pagure (for now): https://pagure.io/fedora-qa/new_issue You can look at existing issues with the test day tag [5] to get an idea how the ticket can look; please include details on what topic you want to cover, and an idea of what dates you would like to hold it. You can also look at the SOP for hosting a test day [6]. If you have any questions about test days or the process, please don't hesitate to contact me or any other Quality team member on Matrix [3] or respond on the test list. Thanks and happy testing! [1] https://fedorapeople.org/groups/schedule/f-44/f-44-key-tasks.html [2] https://testdays.fedoraproject.org/ [3] https://matrix.to/#/%23test-day%3Afedoraproject.org?via=fedoraproject.org&v… [4] https://fedoraproject.org/wiki/QA/Test_Days [5] https://pagure.io/fedora-qa/issues?tags=test+days [6] https://fedoraproject.org/wiki/QA/SOP_Test_Day_management -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Thunderbird on Fedora aarch64 doesn't start anymore
by Andreas Reschke 02 Jan '26

02 Jan '26

Hi there, Thunderbird didn't start anymore. Same problem on both systems: Rock5b and Orion O6, both Fedora 43 up2date Failure: andreas@rock5b:~$ thunderbird Crash Annotation GraphicsCriticalError: |[0][GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03185) [GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) Crash Annotation GraphicsCriticalError: |[0][GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03185) |[1][GFX1-]: Failed to start v4l2test process (t=1.03185) [GFX1-]: Failed to start v4l2test process Crash Annotation GraphicsCriticalError: |[0][GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03185) |[1][GFX1-]: Failed to start v4l2test process (t=1.03185) |[2][GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03185) [GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03285) |[8][GFX1-]: FireTestProcess failed: Failed to spawn child process “/usr/lib64/thunderbird/v4l2test” (No such file or directory) (t=1.03385) |[9][GFX1-]: Failed to start v4l2test process (t=1.03385) [GFX1-]: Failed to start v4l2test process Segmentation fault (core dumped) thunderbird Can't find any package contains "/usr/lib64/thunderbird/v4l2test" How to fix this ?

3 2

Re: [Test-Announce]Fedora Linux 43 Final is GO
by Adam Williamson 23 Oct '25

23 Oct '25

On Thu, 2025-10-23 at 20:01 +0100, Aoife Moloney via test-announce wrote: > The Fedora Linux 43 Final RC 1.6 compose is GO and will be shipped > live on Tuesday, 28 October 2025. > > For more information please check the Go/No-Go meeting minutes[1] or > log[2], and our schedule[3]. > > > Thank you everyone for contributing to another great Fedora Linux release! I want to say a huge thanks to everyone who helped knock out the testing for RC-1.6 in the handful of hours it was available. Great effort everybody! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Fedora 43 RC-1.6 coming with minimal changes
by Adam Williamson 23 Oct '25

23 Oct '25

Hi folks! Just wanted to give a heads up that a late RC is coming. It has only one change, a single somewhat hacky fix to anaconda-webui: https://github.com/AdamWill/anaconda-webui/commit/00cddf567f50a98f019f78316… that *should* only change behavior on the KDE (and other non-GNOME) live image(s). It is intended to fix https://bugzilla.redhat.com/show_bug.cgi?id=2405872 , which it seems to do in my limited testing. It should not affect Workstation, but it's probably a good idea to test a few different language/layout installs to confirm, and try various ones on KDE to make sure it didn't break anything worse than it was before. Nothing else changed, so tests of desktop and server functionality, ARM tests etc. from RC-1.5 should carry over for RC-1.6 without needing to be re-run. Please continue testing RC-1.5 for now and switch over to RC-1.6 when it is finished. I'll transfer appropriate RC-1.5 results to RC-1.6 in the morning. Thanks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-10-20 @ 16:00 UTC - Fedora 43 Blocker Review Meeting
by Adam Williamson 19 Oct '25

19 Oct '25

# F43 Blocker Review meeting # Date: 2025-10-20 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 43 blocker review meeting! We have 3 proposed blockers and 7 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+43+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F43 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-10-13 @ 16:00 UTC - Fedora 43 Blocker Review Meeting
by Adam Williamson 11 Oct '25

11 Oct '25

# F43 Blocker Review meeting # Date: 2025-10-13 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 43 blocker review meeting! We have 10 proposed blockers and 8 proposed freeze exceptions (zoiks!) for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+43+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F43 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-10-06 @ 16:00 UTC - Fedora 43 Blocker Review Meeting
by Adam Williamson 04 Oct '25

04 Oct '25

# F43 Blocker Review meeting # Date: 2025-10-06 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 43 blocker review meeting! We have 2 proposed blockers and 2 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+43+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F43 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2025-09-29 @ 16:00 UTC - Fedora 43 Blocker Review Meeting
by Adam Williamson 29 Sep '25

29 Sep '25

# F43 Blocker Review meeting # Date: 2025-09-29 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 43 blocker review meeting! We have 2 proposed blockers and 2 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F43 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm