Kernal Panic Clarification

[Malmoth]

"uname -v" please. We've already had one user using "opnsense-update -fk" wondering why they land on a 24.7.8 kernel which is entirely correct when you are not on 24.7.10 yet in which case the kernel hotfix procedure doesn't matter anyway. :)

Apologies if I haven't been clear. By the exact same issue, I did mean the exact same issue. I did receive the original update, and than 24.7.10_2. And I currently am stuck at stable/24.7-n267979-0d692990122.

See this link
https://forum.opnsense.org/index.php?topic=44413.msg221775#msg221775

But these are already the steps outlined in the release notes themselves. These are the steps that I've tried, just like nivek1612, but despite the fact that I'm on the default mirror, it just doesn't update the kernel.
I misunderstood what passeri was talking about when they mentioned "the terminal procedures." I thought they were using "terminal" in reference to "last" or "final," as in they were referring to some sort of last ditch option that wasn't referenced earlier. That was just me being silly.

Maybe I was doing something wrong with the GUI option. I basically used the "Reinstall" button for the "opnsense" package. I assume that's what the "reinstall from the GUI" meant in the release notes. Am I right?

Regardless though, "opnsense-update -fk" should work, but it doesn't.

[franco]

Did you reboot to boot into the updated kernel? The Cloudflare mirror could be playing tricks again if you have that one set.


Cheers,
Franco

[Malmoth]

Of course. That was part of the manual update instructions.
Didn't realize the default mirror relies on Cloudflare. I guess I'll just have to wait until Cloudflare invalidates caches on their backend.

[franco]

I can assure you the default mirror is fine. It only has one kernel file and it's the right one.


Cheers,
Franco