I have upgraded from freshly installed 2025-06-26 image to most recent 2025-09-09 image and when booting the new image a kernel panic happened
#[TEMPORARY SOLUTION] Kernel panic when upgrading to newer image
sterile sonnet
regal jay
which image, and on what hardware?
junior garnet
and did you run any post-install steps
sterile sonnet
No
sterile sonnet
and did you run any post-install steps
No post install steps
sterile sonnet
which image, and on what hardware?
Kinoite-nvidia-open-hardened
junior garnet
which image, and on what hardware?
@sterile sonnet
sterile sonnet
A second
CPU: 13th Gen Intel(R) Core(TM) i7-1355U (12) @ 5.oo GHz
GPU 1: Nvidia GeForce RTX 3050 4GB Laptop GPU [Discrete]
GPU 2: Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
junior garnet
interesting
thanks
unfortunately this doesn't give me any clear ideas
assuming zero changes were made aside from updating
that makes me inclined towards nvidia shipping a bug
sterile sonnet
I can send the error message from before kernel panic
junior garnet
you could try binary searching the date tags
which look like :20250810
instead of :latest
sterile sonnet
you could try binary searching the date tags
Excuse me, but how do I do that?
junior garnet
Excuse me, but how do I do that?
rpm-ostree rebase to your current change but change the tags like above
from latest to a date
junior garnet
which look like `:20250810`
like this
sterile sonnet
I can send the error message from before kernel panic
error: ../../grub-core/kern/mm.c:552:out of memory
Then it says to press any key to continue
Kernel panic error is: VFS: Unable to mount root fs on unknown block(0,0)
regal jay
that makes me inclined towards nvidia shipping a bug
moment 
junior garnet
looks like this issue https://github.com/ublue-os/bazzite/issues/3147
@sterile sonnet do you have secure boot enabled
sterile sonnet
No
junior garnet
and our key enrolled
junior garnet
No
oh
well that will prevent nvidia drivers from loading
although it shouldn't cause the error in question
sterile sonnet
you could try binary searching the date tags
Ah understood
error: while pulling 20250810: Remote "kinoite-nvidia-open-hardened" not found
junior garnet
error: while pulling 20250810: Remote "kinoite-nvidia-open-hardened" not found
?
what command did you run
the rebase target should match the string in rpm-ostree status exactly aside from the tag
if you omit any part of it, it will break
sterile sonnet
Got it
Pulling currently
20250810 is okay
Testing 20250825
20250825 is okay
Testing 20250903
20250903 is not okay
Testing 20250829
20250829 is not okay
Testing 20250827
20250827 is okay
Testing 20250828
20250828 is okay
@junior garnet @regal jay the problem is between 20250828 and 20250829
regal jay
seems like it must be an upstream issue then, there weren't any secureblue commits on August 28-29 that could cause anything like this
sterile sonnet
Excuse me, how would one track down the issue causing it and how would one sent the report to upstream?
junior garnet
Excuse me, how would one track down the issue causing it and how would one sent ...
run rpm-ostree db diff while having those two date tags in staged/current deployments
it will tell you which packages changed
sterile sonnet
I have found the temporary solution in the provided issue: disable the TPM chip in BIOS settings
I also checked the changed packages between 20250828 and 20250829, it was a kernel update
sterile sonnet
looks like this issue https://github.com/ublue-os/bazzite/issues/3147
This issue
[TEMPORARY SOLUTION] Kernel panic when upgrading to newer image
sterile sonnet
Update: I have found the upstream issue on this problem, https://bugzilla.redhat.com/show_bug.cgi?id=2263643
The root of the error has been found and the patch has been submitted last month, and is planned to be shipped in fedora 44
Which expected to release 2026-04-14
The specific patch is https://src.fedoraproject.org/rpms/grub2/pull-request/198