[SOLVED] update installed oem and oracle kernels, both are on top and wont start

[Fred-VIE]

The kernels are

5.17.0-1020.OEM.
Error: DEV LVOP0: unable to read RDB Block 8
DEV LVOP11: same as above

5.15.0-1021-ORACLE - didnt even try to start this cuz why Oracle anyways?

Edt.: what it actually did was install the "linux-signatures-nvidia-5.17.5.17.0-1020.21+1 package and the linux-image-5.17.0-1020-oen package with objects and modules using the same number.

How can I get rid of those so that the system will start normally again?
Can I just use Synaptic and the option "mark for complete removal" without anyhting bad happening?

[Snowhog]

Do so when you are booted into any prior installed kernel, one that actually boots.

[Fred-VIE]

Why do not working Kernels get into the update anyways?

Just tried the Oracle one. It didnt load either, no surprise though.

Ye removing them via Synaptic luckily worked without causing problems.

Hope they wont be in the update again

[claydoh]

It might help to post in the correct topic for the version of Kubuntu you are using?
No idea how an OEM or an Oracle specific kernel is even installed on a normal Kubuntu install to begin with, so knowing the correct release without having to ask the OP might help a little as a starting point for investigating

Assuming Nvidia GPU, this just throws extra wrenches into the mix, as I am sure these kernels might involve extra steps to (re)build the Nvidia shims that connect the closed-sourced drivers to the kernels -- if they even can with the specific versions.

[ShadYoung]

I saw that this morning and decided to wait as "Oracle" is not what I run. Sure enough the update disappeared during the day and was replaced with an update to GCC and Firmware. The reason I hesitated this morning and decided to wait a day is this is not the first time it has happened recently. The same thing happened a week or so ago and it was only because I decided to reboot before updating that I discovered it was not right. I mentioned this in the Kubuntu Facebook group as well, but in there I thought an "architecture" check would be done and actually prevent the wrong kernel being installed. Seems I was wrong about that, and that is very concerning.

As it stands, I am being very careful with every update. I do not trust it. The updater has been buggy since 22.04 came out. I suggest it is worth filing a bug report.

[Fred-VIE]

The reason I installed them was, that they did not look like new kernels but rather like some driver addition.
The OEM version was not suspicious but the Oracle one I found odd but thought it might be some compatibility thing.

I'm using Kub 22.04.