arm February 2025

arm@lists.fedoraproject.org

4 participants
4 discussions

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 17 Feb '25

17 Feb '25

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2025-02-18 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 10 Feb '25

10 Feb '25

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2025-02-11 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

Update to kernel 6.12.10 left my Rock Pi 4 not bootable
by Peter Boy Uni 03 Feb '25

03 Feb '25

Among others I use a Radxa Rock Pi 4a with nvme disk. The latest update to kernel 6.12.10 ended with a not bootable system. With the release kernel and the update kernel 6.8.10 everything worked flawlessly I get: [ OK ] Reached target bsasic.target - Basic System. rk3399-dmc-freq ffa80000.dmc: Invalid operating-points in device tree. rk3399-dmc-freq ffa80000.dmc: probe with driver rk3399-dmc-freq failed with error -22 [ OK ] Stopped systemd-vconsole-setup.service - Virtual Console Setup. . . . [ ...... ] dracut-initqueue[557]: Volume group "fedora" not foumd [ ...... ] dracut-initqueue[557]: Cannot process volume group fedora That cannot work, indeed, because the VG on this system was renamed due to LVM naming conflicts. Additionally, the directory /etc/lvm/devices is empty, but it should contain a valid device file. I can mount the EFI and the boot partitions of the nvme disk and access all files therein. I would like to switch back to the previous kernel 6.8.10 and wondering how to do that in the dracut shell. If I remember correctly there is a tool available, but I don’t remember the details and my internet research didn't come up with anything useful. I would greatly appreciate any advice on how to revert to the previous kernel. Thanks Peter — Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

3 5

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 03 Feb '25

03 Feb '25

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2025-02-04 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm February 2025