On Sat, Aug 17, 2019 at 11:01 AM zb4ng <zb4ng@arcor.de> wrote:
On my desktop, there are two LEAP systems, 15.0 and 15.1. grub is managed by the older version 15.0.
Show grub.cfg from 15.0 and 15.1. Actually providing result of bootinfoscript (https://raw.githubusercontent.com/arvidjaar/bootinfoscript/master/bootinfosc...) would be the best to avoid lengthy (and usually misleading) descriptions.
Now, i found that on 15.1, an old version of the kernel is used rather than the latest patch:
This is most likely incorrect. I expect grub.cfg on 15.1 to default to latest version (unless you set defaults explicitly) but grub.cfg from 15.1 is not used by bootloader of 15.0. ...
I figured, I should let grub refresh its boot entries, so I started the boot configuration in Yast on 15.0, but had no success with it.
It is not clear what you did and what "no success" means (did it fail? If yes, what was the error message?), but unless you have changed something in bootloader configuration simply entering and quitting YaST botloader module won't do anything. Try "update-bootloader --refresh" in 15.0.
Maybe, i could simply delete the old kernels manually? But how can i avoid this from happening every time a new patch is released?
Assuming you have default configuration that is using os-prober to incorporate bootloader entries from one Linux instance into bootloader configuration of another Linux instance - this is one time static process. If Linux A is managing bootloader, it scans grub.cfg of Linux B once - and is not aware of any changes in Linux B after that. You will need to refresh bootloader in Linux A (using e.g. command shown above) every time something in Linux B changes. Not that refresh happens implicitly when something changes in Linux A as well (e.g. new kernel installed). Alternative is to not use os-prober, but manually configure bootloader in Linux A to call bootloader of Linux B directly. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org