![](https://seccdn.libravatar.org/avatar/b150acea6b2203078d2a9d30bedeee91.jpg?s=120&d=mm&r=g)
On 19/07/17 21:39, Carlos E. R. wrote:
On 2017-07-19 08:38, Basil Chupin wrote:
On 18/07/17 20:59, Carlos E. R. wrote:
On 2017-07-18 05:26, Basil Chupin wrote:
Hi John,
I'll add a bit more to what I stated above re doing something so as not to clobber the 4.11 or 4.12 kernel from /repo/Kernel:/stable....
If you are using zypper to update your oS or even use Yast itself, both or either will try and re-install the original installed kernel ie, 4.4.x because in all probability it is marked as being installed in Yast's Version information. You will see what I mean if you:
* start Yast * search for 'kernel' and you will see a number of entries with 'kernel' in them * highlight each one (by clicking on each one) and then select VERSION * you may see that kernel 4.4.x is still ticked as being installed even though 4.11/4.12 is also shown as installed
and this last item is what will make zypper or Yast try an re-install 4.4.x kernel. Nevertheless, grub will boot the most recent kernel by default, no matter if the original is still installed. Umm, not necessarily... But you may absolutely correct in what you say. Let me explain...
I experienced just the opposite to what you wrote above only yesterday (and before I wrote the above 'addendum to the addendum'). Perhaps something did not happen which I expected and therefore what happened did happen :-).
After installing the new 4.12.x kernel, I looked in /boot and found that the '@vmlinuz' and @initrd' both pointed to the old (4.4.x) kernel. Now this may have resulted from some part of the kernel family of files not being installed during the many attempts I had to go thru while trying to stop Yast from re-installing 4.4.x :-). I do not know what maintains those links, and what criteria. Specially when you install an extra kernel.
I guess the point here is to check in /boot as to which kernel is actually configured for use at boot time before hitting the 'reboot' "button" :-). Grub 2 uses the kernel with the bigger number. Currently openSUSE grub2's doesn't use those symlinks, I believe.
You can go "read" /boot/grub2/grub.cfg. Search for "### BEGIN /etc/grub.d/10_linux ###", and the next entry is the main one.
OK, let's make something clear at this point in time. My comment about the kernel goes back some 12 days ago and by now I suspect that most, if not all, people have forgotten what I said which was that//I have Leap 42.3 BETA installed (but it is due for official release next Tuesday OZ time/day) and that I also installed the latest kernel 4.12.x from the .../stable/standard/ repo and am, therefore, not using the normal kernel which comes with Leap 42.3. Well, my comments relate _only_ to this combo: Leap 42.3 and kernel 4.12.x. Let's carry on.... Earlier today I booted into Leap 42.3 and then did the "zypper three-step dance" routine -- the very first thing I do when I first switch on the computer. To my surprise 'zypper patch' came up with wanting to install kernel 4.4.76 when the damn thing is not showing in Yast as I had labouriously deleted the damn thing! I also looked in /boot and found that both '@initrd' and '@vmlinuz' were _still_ symlinked to kernel 4.4.76 -- but grub.cfg showed that initrd had kernel 4.12.2 to use. To cut a long story short: the person-in-the-woodpile was a file which appeared in Leap 42.3 (but is not in Leap 42.2) and is the cause of this hassle of zypper/Yast wanting to re-install kernel 4.4.76. The file is drm-kmp-default. When you try and install kernel 4.12.x using Yast and deleting kernel 4.4.x, you will get a dependency error(s) and one of them will contain a reference to drm-kmp-default. Select to DELETE this file and this will stop 4.4.x from being re-installed. As I said, this applies only Leap 42.3 and does NOT apply to Leap 42.2. BC -- You are NOT entitled to your opinion. You are entitled to your INFORMED opinion. Nobody is entitled to be ignorant. Harlan Ellison -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org