Thursday, January 30, 2025

[fedora-arm] Update to kernel 6.12.10 left my Rock Pi 4 not bootable

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@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


--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

No comments:

Post a Comment