On Thu, 30 Jan 2025, Peter Boy Uni via arm wrote:
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
Go to /boot/loader/entries and compare the entries for the 6.12 and 6.8
kernels. I ran into this too, where until you update the right configs,
dracut still uses old LVM names, UUIDs, etc.
As an interim measure, (after booting with the old kernel) compare the
loader entries and update the new kernel entry to be like the working
entry. Grep through /etc/default and other places looking for what the
new (old/broken) kernel had. After next kernel upgrade, compare the
loader entries in /boot before actually rebooting. Manually edit so
boot works, and then make another search for where dracut is getting the
old config.
--
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
