So, I installed the kernel-desktop-3.16.7-24 as an update but didn’t work on my system. So I fellback to the version before that one and I’m planning on uninstalling the newest. But the problem (?) here is that whenever I do a zypper rm kernel-desktop-3.16.7-24 or an uninstall from YaST, the package kernel-desktop-base-3.16.7-24 gets installed and viceversa. Also, even though I remove either of them, the bootloader still has 3.16.7-24 as default and must select the 3.16.7-21 manually. Is this normal behavior? Or am I removing the kernel package the wrong way?
But the problem (?) here is that whenever I do a zypper rm kernel-desktop-3.16.7-24 or an uninstall from YaST, the package kernel-desktop-base-3.16.7-24 gets installed and viceversa.
Something else you have installed seems to require kernel-desktop-3.16.7-24 (some kmp package maybe). You have to remove that as well.
Taboo kernel-desktop-base (it is just a stripped down version of kernel-desktop with most kernel modules missing and won’t really work on standard PC systems), and you will see what that is when trying to remove kernel-desktop.
Also, even though I remove either of them, the bootloader still has 3.16.7-24 as default and must select the 3.16.7-21 manually. Is this normal behavior?
When you remove both kernel-desktop and kernel-desktop-base, there should not be an entry for it in the boot loader any more.
If one of them is installed, an entry is there of course.
You can select the default boot entry in YaST->Boot Loader though.
My system’s bootloader turned into a loop. Once it gets past the countdown and starts booting the system, the PC reboots again.
Something else you have installed seems to require kernel-desktop-3.16.7-24 (some kmp package maybe). You have to remove that as well.
Taboo kernel-desktop-base (it is just a stripped down version of kernel-desktop with most kernel modules missing and won’t really work on standard PC systems), and you will see what that is when trying to remove kernel-desktop.
Found said package. It was crash-kmp-desktop. But again, even though I try to remove both packages, both zypper and YaST seem to try to install an alternative. Either kernel-xen, kernel-vanilla, kernel-debug, kernel-ec2 or kernel-default each with its respective crash-kmp package.
You can select the default boot entry in YaST->Boot Loader though.
You must have a kernel. that is normally kernel-desktop unless you have a very good reason not to use desktop.
You may have 2 kernels installed at the same time to allow boot to the older if there is a problem with a newer
If you have a driver, say NVIDIA, that you installed for another then the normal kernel flavour then that package would be dependent and may force the reinstall of some odd flavour of the kernel.
You do not need or want kernel-base or any other flavour of any package you only want desktop flavours for any kernel dependent package. having any other flavour package for any dependent program code will force the reinstall of that flavour kernel and ll it’s trimmings.
Hm, any error message? Does it actually load the kernel and initrd? (there should be messages about this)
Have you tried recovery mode (2nd entry in “Advanced Options”)?
Found said package. It was crash-kmp-desktop. But again, even though I try to remove both packages, both zypper and YaST seem to try to install an alternative. Either kernel-xen, kernel-vanilla, kernel-debug, kernel-ec2 or kernel-default each with its respective crash-kmp package.
As gogalthorpe mentioned, you need to have a kernel, so YaST wants to install another flavour if you remove the only one(s) installed.
If you mark “kernel-desktop” for deinstallation, all versions will be removed, also the older ones.
Use the “Versions” tab below the package list to uninstall one particular version.
Yes, it does exactly the same looping thing. Both the normal kernel option and the recovery mode show the message of loading the kernel and the init ramdisk, then the reboot. No error message whatsoever. Maybe I’ll check the logs later.
As gogalthorpe mentioned, you need to have a kernel, so YaST wants to install another flavour if you remove the only one(s) installed.
If you mark “kernel-desktop” for deinstallation, all versions will be removed, also the older ones.
Use the “Versions” tab below the package list to uninstall one particular version.
If I try to uninstall from the versions tab, it keeps trying to install kernel-desktop-base. I have tried to reinstall such latest kernel version three times so far with no success. Guess I’ll have to use the fallback version until there’s a better update.
You have to be really aggressive in the software manager to force what you want when trying to do what you describe.
Some care will be needed too if you are not that familiar with what you are doing
There are no logs at this point, if I understand you correctly.
It seems to reboot just after the initrd is loaded, before the Linux boot even starts.
One thing you could try is to disable the loading of the CPU microcode update. This has caused problems for certain CPUs in the recent past, although normally it manifests as hanging at “Loading initial ramdisk…”, not a reboot.
To do that, just add “dis_ucode_ldr” to the boot options (e.g. press ‘e’ in the boot menu and append it to the line starting with “linux”/“linuxefi”).
If I try to uninstall from the versions tab, it keeps trying to install kernel-desktop-base.
Lock kernel-desktop-base to prevent it from being installed before you try to remove kernel-desktop-3.16.7-24.
I.e. right-click on it and select “Taboo - Never Install”.
IT WORKED! Thank you very much. I probably should have stated what my real problem was from the very beginning, and maybe this thread should be renamed. Anyhow, I just added the line to the bootloader kernel parameters so it loads by default. No need of removing the kernel whatsoever.