Superseding 5.11.16-1.1.ge06d321 kernel - Can Now Use - 5.13.6-1.1.21.11 kernel
Hello, I have an older Compaq nc6400 notebook (Centrino Duo). I was able to get up and running under openSUSE TDE KDE with your much appreciated help a few months ago 😁. The old thread is located here -> https://lists.opensuse.org/archives/list/users@lists.opensuse.org/thread/YVX... Some history on the 5.12.0-1-pae kernel (bootabillity issue I experienced) can be located on bugzilla here: -> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542 I have locked the 5.11.16-1.ge06d321-default kernel (after installing the https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar... repository). I have been keeping the notebook updated with the "zypper dup" command. uname -a Linux pj-Compaq-nc6400 5.11.16-1.ge06d321-default #1 SMP Thu Apr 22 10:30:16 UTC 2021 (e06d321) i686 i686 i386 GNU/Linux pj@pj-Compaq-nc6400:~> sudo zypper dup [sudo] password for root: Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 6 items are locked and will not be changed by any action: Available: kernel-default-base kernel-default-base-rebuild kernel-default-devel Installed: kernel-default kernel-devel kernel-source Nothing to do. 1. I noticed this evening that I was able to select the 5.13.6-1-pae kernel from the boot menu and not only a 5.12.xx series kernel anymore. So I selected the 5.13.6-1-pae kernel and proceeded to boot without failure to the splash screen. I entered my password when prompted at the splash screen and KDE loaded without incident to the welcome screen (This lookout character is excellent 😁). 2. I opened a konsole instance and then entered "uname -a" then "zypper dup". pj@pj-Compaq-nc6400:~> uname -a Linux pj-Compaq-nc6400 5.13.6-1-pae #1 SMP Thu Jul 29 04:18:38 UTC 2021 (2d7b44d) i686 i686 i386 GNU/Linux pj@pj-Compaq-nc6400:~> sudo zypper dup [sudo] password for root: Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 6 items are locked and will not be changed by any action: Available: kernel-default-base kernel-default-base-rebuild kernel-default-devel Installed: kernel-default kernel-devel kernel-source Nothing to do. pj@pj-Compaq-nc6400:~> 3. The 6 items that I previously locked (I used YaST to do this) may no longer need to be locked. If I decide to operate the machine under the 5.13.6-1-pae kernel. The machine seems to be operating fine with no known issues. I opened YaST and searched pattern "kernel" and there are 3 immediate packages relating to the 5.13.6-1-pae kernel listed as follows: 1a. kernel-default-base - The Standard Kernel - base modules (5.13.6-1.1.21.11) 1b. kernel-default-base-rebuild - Empty package to ensure rebuilding kernel-default-base in OBS (5.13.6-1.121.11) 1c. kernel-default-devel - Development files necessary for rebuilding kernel modules I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended. I do not see any kernel-source package listed in YaST for 5.13.6-1-pae kernel. Only kernel-source for the 5.11.16-1.1.ge06d321 (installed) and kernel-source-vanilla (uninstalled) are shown under a "kernel sources" search pattern in YaST. 4. Going forward in order to lock the 5.13.6-1-pae kernel I will use YaST. I will need kernel-sources for documentation at some point. Where can this be located and what other kernel related packages can be installed for a more robust experience if necessary? 5. I believe I do not need to uninstall the 5.11.16-1.1.ge06d321 kernel just unlock all 6 of the currently locked packages: -> 1.the kernel-default-base 2.kernel-default-base-rebuild 3.kernel-default-devel 4.kernel-default 5.kernel-devel 6.kernel-source Well, should I just remove everything 5.11.xx related while operating under 5.13.6-1-pae....install and lock kernel-default-base 5.13.6-1.21.11.....*although*....where are it's kernel-sources? Perhaps I should not uninstall or remove the 5.11.xx repository nor packages just unlock the currently locked packages and lock 5.13.6-1.21.11 Perhaps I should leave the 5.11.xx locked as is. I can also lock the 5.13.6-1.21.11 right? zypp.conf is default right now (So It's only holding 3 kernels as per default settings. 6. I hope this is a fairly well written and understandable thread. I wish to get your advice on this situation please. -Best Regards
-pj composed on 2021-08-07 00:46 (UTC-0500):
I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended.
sudo zypper al kernel-pae* will keep 5.13.6 from being removed, and prevent zypper and yast from attempting to install any other kernel-pae version.
5. I believe I do not need to uninstall the 5.11.16-1.1.ge06d321 kernel just unlock all 6 of the currently locked packages: ->
1.the kernel-default-base 2.kernel-default-base-rebuild 3.kernel-default-devel 4.kernel-default 5.kernel-devel 6.kernel-source Good plan. At some point you'll decide to remove the lock and upgrade kernel again. Once that's done, subject to any policy alteration to multiversion.kernels= in in /etc/zypp/zypp.conf, purge-kernels service will remove 5.11.16. -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 8/7/21 1:25 AM, Felix Miata wrote:
-pj composed on 2021-08-07 00:46 (UTC-0500):
I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended.
sudo zypper al kernel-pae*
will keep 5.13.6 from being removed, and prevent zypper and yast from attempting to install any other kernel-pae version.
The faulty (for this machine) 5.12.13-1-pae kernel is currently listed as an option in the bootmenu though. Using the above suggested command "sudo zypper al kernel-pae*" seems like it might lock 5.12.13-1-pae also? If the machine is currently booted/operating under the 5.13.6-1-pae then does "zypper al kernel-pae*" only lock that specific operating kernel instance (this may be what you are pointing out). How can I find the exact specific package name for the 5.13.6-1-pae kernel ?
5. I believe I do not need to uninstall the 5.11.16-1.1.ge06d321 kernel just unlock all 6 of the currently locked packages: -> 1.the kernel-default-base 2.kernel-default-base-rebuild 3.kernel-default-devel 4.kernel-default 5.kernel-devel 6.kernel-source Good plan. At some point you'll decide to remove the lock and upgrade kernel again. Once that's done, subject to any policy alteration to multiversion.kernels= in in /etc/zypp/zypp.conf, purge-kernels service will remove 5.11.16.
I believe the purge-kernels service is active by default right? Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3? Thanks for your prompt and decisive response to this situation. :]
On 07/08/2021 07.46, -pj wrote:
Perhaps I should not uninstall or remove the 5.11.xx repository nor packages just unlock the currently locked packages and lock 5.13.6-1.21.11
Perhaps I should leave the 5.11.xx locked as is. I can also lock the 5.13.6-1.21.11 right? zypp.conf is default right now (So It's only holding 3 kernels as per default settings.
6. I hope this is a fairly well written and understandable thread. I wish to get your advice on this situation please.
Maybe you can use the multiversion feature to say that the kernel version that was locked you do not want to be removed. List that specific kernel. etc/zypp/zypp.conf: ## Comma separated list of kernel packages to keep installed in parallel, if the ## above multiversion variable is set. Packages can be specified as ## 2.6.32.12-0.7 - Exact version to keep ## latest - Keep kernel with the highest version number ## latest-N - Keep kernel with the Nth highest version number ## running - Keep the running kernel ## oldest - Keep kernel with the lowest version number (the GA kernel) ## oldest+N - Keep kernel with the Nth lowest version number ## ## Note: This entry is not evaluated by libzypp, but by the ## purge-kernels service (via /sbin/purge-kernels). ## ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set multiversion.kernels = latest,latest-1,running -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
-pj composed on 2021-08-07 02:37 (UTC-0500):
Felix Miata wrote:
-pj composed on 2021-08-07 00:46 (UTC-0500):
I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended.
sudo zypper al kernel-pae*
will keep 5.13.6 from being removed, and prevent zypper and yast from attempting to install any other kernel-pae version.
The faulty (for this machine) 5.12.13-1-pae kernel is currently listed as an option in the bootmenu though. Using the above suggested command "sudo zypper al kernel-pae*" seems like it might lock 5.12.13-1-pae also?
Exactly.
If the machine is currently booted/operating under the 5.13.6-1-pae then does "zypper al kernel-pae*" only lock that specific operating kernel instance (this may be what you are pointing out).
If you want to lock only a specific kernel, the version string must be part of the lock string name. e.g. zypper al kernel-pae-5.13.6* If you want to lock all kernels of a specific version, then: zypper al kernel*5.13.6*
How can I find the exact specific package name for the 5.13.6-1-pae kernel ?
If it's an installed kernel: rpm -qa | grep nel-pae e.g. # rpm -qa | egrep 'nel-pae|nel-def' kernel-default-5.7.11-1.2.i586 kernel-default-5.8.15-1.2.i586 kernel-default-5.9.14-1.2.i586 kernel-default-5.10.16-1.3.i586 kernel-default-5.11.16-1.1.i586 kernel-default-5.12.13-1.1.i586
I believe the purge-kernels service is active by default right?
Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3?
If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure. Something else to consider if your PC seems sensitive to kernel changes is locking all kernels, then only installing a new one when you're so inclined. Locks with wildcards are never deleted by zypper, even though it claims to do so when removal is an option presented in response to an attempt to install (or remove) any version the lock would apply to. What actually happens in such attempts is zypper ignores the lock for that one specific transaction. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500):
Felix Miata wrote:
-pj composed on 2021-08-07 00:46 (UTC-0500):
I want to install and lock every possible kernel package relating to 5.13.6-1-pae that can be recommended. sudo zypper al kernel-pae* will keep 5.13.6 from being removed, and prevent zypper and yast from attempting to install any other kernel-pae version. The faulty (for this machine) 5.12.13-1-pae kernel is currently listed as an option in the bootmenu though. Using the above suggested command "sudo zypper al kernel-pae*" seems like it might lock 5.12.13-1-pae also?
Exactly.
If the machine is currently booted/operating under the 5.13.6-1-pae then does "zypper al kernel-pae*" only lock that specific operating kernel instance (this may be what you are pointing out).
If you want to lock only a specific kernel, the version string must be part of the lock string name. e.g.
zypper al kernel-pae-5.13.6*
If you want to lock all kernels of a specific version, then:
zypper al kernel*5.13.6*
If I issue the following command: zypper al kernel-pae-5.13.6-1-pae it is correct and not zypper al kernel-pae-5.13.6-1.2.i686 correct? How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST. Is there a konsole command to list all locked packages on the machine?
How can I find the exact specific package name for the 5.13.6-1-pae kernel ?
If it's an installed kernel:
rpm -qa | grep nel-pae
e.g. # rpm -qa | egrep 'nel-pae|nel-def' kernel-default-5.7.11-1.2.i586 kernel-default-5.8.15-1.2.i586 kernel-default-5.9.14-1.2.i586 kernel-default-5.10.16-1.3.i586 kernel-default-5.11.16-1.1.i586 kernel-default-5.12.13-1.1.i586
Passing command "rpm -qa | egrep 'nel-pae|nel-def' in the notebook's konsole results as follows: pj@pj-Compaq-nc6400:/> rpm -qa | egrep 'nel-pae|nel-def' kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686 pj@pj-Compaq-nc6400:/> I notice that today there was a kernel update to....kernel-pae-5.13.6-1.2.i686 (machine stable :|) Can I safely remove kernel-pae-5.12.13-1.1.i686? How can I remove this kernel and all remnants of it with zypper? YaST is not displaying the 5.12.xx kernel or any packages relating to it's series when "kernel" search pattern is used. Then the bootmenu will show the 5.11.xx and 5.13.xx kernels correct? I see how command "rpm -qa | egrep 'nel-pae|nel-def' shows the above 3 instances listed and not the below instances. This use of grep and egrep is another topic I know. 1.the kernel-default-base 2.kernel-default-base-rebuild 3.kernel-default-devel 5.kernel-devel 6.kernel-source
I believe the purge-kernels service is active by default right?
Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running
I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321 I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3?
If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure.
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation: -----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it: /usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R. I know more now in your response within the above paragraph, what you are conveying. What about CVS security patches and such for the latest kernel versions?
Something else to consider if your PC seems sensitive to kernel changes is locking all kernels, then only installing a new one when you're so inclined. Locks with wildcards are never deleted by zypper, even though it claims to do so when removal is an option presented in response to an attempt to install (or remove) any version the lock would apply to. What actually happens in such attempts is zypper ignores the lock for that one specific transaction.
I have reread this above paragraph so it's more sense. Of course I will have to file this for reference. -Best Wishes
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500):
How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine?
Of course: "zypper ll". Not the only one: cat /etc/zypp/locks
I believe the purge-kernels service is active by default right?
Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running
I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running
AFAIK that change does nothing to the menu, it only affects "purge-kernels".
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3?
If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure.
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:
-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:
/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R.
:-) I seem to recall an rpm named something like kernel-docs :-? [...] Yes! It still exists, I just looked. And an html version. But I have no idea what it contains exactly. Maybe that directory, or that directory processed and copied somewhere else. ... -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500):
How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll".
Not the only one:
cat /etc/zypp/locks
I believe the purge-kernels service is active by default right? Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running AFAIK that change does nothing to the menu, it only affects "purge-kernels".
I Thank you alot for your clarification above, now multiversion.kernels adjustments make more sense to me. I in my shallow mind was somehow thinking that the multiversion.kernels entry affected the appearance of kernels on the boot menu as well. :| Does the following entry: multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321 Does this look correct to you? What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"? Passing command "rpm -qa | egrep 'nel-pae|nel-def' in konsole currently returns 3 kernels: kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686 I would imagine that adding the correct 5.11.xx kernel label to multiversion.kernels that the boot menu would then have 4 various kernel's eventually displayed is this correct?
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3? If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure.
If I were to disable the "purge-kernels.service" do each of the eventually/additionally installed kernels appear on the machines bootmenu? How many kernels can Tumbleweed successfully have installed?
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:
-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:
/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R. :-)
I seem to recall an rpm named something like kernel-docs :-?
[...]
Yes! It still exists, I just looked. And an html version. But I have no idea what it contains exactly. Maybe that directory, or that directory processed and copied somewhere else.
...
Now this "kernel-docs" rpm is basically the same as kernel-sources is for the 5.11.xx ? YaST does not appear to show a kernel-sources package for the 5.13.xx kernel. What you are trying to convey is reading through "kernel-docs" package would be my starting point for any additional packages in relation to the 5.13.xx kernel? What I am trying to ask, is, can you suggest when the machine is running under the 5.13.xx kernel what would be the first document to review as far as major-minor in /dev..... I have certainly noted as Felix Miata stated previously, and I quote: "If you have any kernel that works, that one is all you need for normal use". I thank you for your help with this and before. I am extremely happy with the laptop right now. I have a desktop with TDE KDE installed and it's wonderful and robust also. -Regards Y (^,^) | ( : ) x ( : )
On 09/08/2021 09.09, -pj wrote:
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500):
How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll".
Not the only one:
cat /etc/zypp/locks
I believe the purge-kernels service is active by default right? Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running AFAIK that change does nothing to the menu, it only affects "purge-kernels".
I Thank you alot for your clarification above, now multiversion.kernels adjustments make more sense to me. I in my shallow mind was somehow thinking that the multiversion.kernels entry affected the appearance of kernels on the boot menu as well. :|
Does the following entry:
multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
Does this look correct to you?
It does, but that I know of the existence of this setting doesn't mean I'm an expert on it :-D The procedure would be to write an entry then try if it works. Now, how exactly to "try" without destroying the target is the problem.
What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"?
No, the "label" comes from the rpm name. You can see the service that does it: minas-tirith:~ # systemctl cat purge-kernels.service # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/ [Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels [Install] WantedBy=multi-user.target minas-tirith:~ # Ok, it runs once soon after boot if file "/boot/do_purge_kernels" exists, root is writeable, then fires "/usr/bin/zypper -n purge-kernels", and finally deletes "/boot/do_purge_kernels". Thus, you can manually run "/usr/bin/zypper -n purge-kernels". But perhaps reading the manual we can find if there is a way to run it without actually /running/ it. Mmm... I don't see what '-n' does. You could try "--dry-run" minas-tirith:~ # zypper --dry-run -n purge-kernels The flag --dry-run is not known. minas-tirith:~ # minas-tirith:~ # zypper -n purge-kernels --dry-run Reading installed packages... Preparing to purge obsolete kernels... Configuration: latest,latest-1,running Running kernel release: 5.3.18-lp152.84-default Running kernel arch: x86_64 Resolving package dependencies... Nothing to do. minas-tirith:~ # Ok, there you have a test method :-)
Passing command "rpm -qa | egrep 'nel-pae|nel-def' in konsole currently returns 3 kernels:
kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686
I would imagine that adding the correct 5.11.xx kernel label to multiversion.kernels that the boot menu would then have 4 various kernel's eventually displayed is this correct?
How to display the kernels in boot is decided, I don't know how it is decided. I suppose that at some point zypper sees what is installed and writes the menu.
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3? If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure. If I were to disable the "purge-kernels.service" do each of the eventually/additionally installed kernels appear on the machines bootmenu? How many kernels can Tumbleweed successfully have installed?
I have no idea of the limit. Disabling purge-kernels would not have effect on the menu. Something (zypper?) would see the installed kernels and write the appropriate menu. AFAIK, there is something you can run yourself and write the boot menu solely, but this instant I'm unsure. Could be: grub2-mkconfig -o /boot/grub2/grub.cfg
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:
-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:
/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R. :-)
I seem to recall an rpm named something like kernel-docs :-?
[...]
Yes! It still exists, I just looked. And an html version. But I have no idea what it contains exactly. Maybe that directory, or that directory processed and copied somewhere else.
...
Now this "kernel-docs" rpm is basically the same as kernel-sources is for the 5.11.xx ? YaST does not appear to show a kernel-sources package for the 5.13.xx kernel.
I'm not sure what it contains. I assume it contains the same as the documentation in the source tree, without having to install the huge source package, but I don't know.
What you are trying to convey is reading through "kernel-docs" package would be my starting point for any additional packages in relation to the 5.13.xx kernel?
Huh, no.
What I am trying to ask, is, can you suggest when the machine is running under the 5.13.xx kernel what would be the first document to review as far as major-minor in /dev.....
It is possible that the kernel-doc package contains that file(s) too. I think so, but I don't know.
I have certainly noted as Felix Miata stated previously, and I quote: "If you have any kernel that works, that one is all you need for normal use".
I thank you for your help with this and before. I am extremely happy with the laptop right now. I have a desktop with TDE KDE installed and it's wonderful and robust also.
:-) -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 8/9/21 5:16 AM, Carlos E. R. wrote:
On 09/08/2021 09.09, -pj wrote:
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500): How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll". Compaq-nc6400:/etc/zypp> zypper ll
# | Name | Type | Repository | Comment --+-----------------------------+---------+------------+-------- 1 | kernel-default | package | (any) | 2 | kernel-default-base | package | (any) | 3 | kernel-default-base-rebuild | package | (any) | 4 | kernel-default-devel | package | (any) | 5 | kernel-devel | package | (any) | 6 | kernel-source | package | (any) | Compaq-nc6400:/etc/zypp> Do you know why the following repository is: -> https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar... Not listed in the repository field above? Yes, I can see this repository is installed with: System -> Yast -> Software -> Software Repositories -> tiwai_kernel_5.11 (I still have the above 6 listed packages locked obviously).
Not the only one:
cat /etc/zypp/locks Noted thanks.
I believe the purge-kernels service is active by default right? Yes.
Currently here multiversion.kernels line 554: 1 multiversion.kernels = latest,latest-1,running I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running AFAIK that change does nothing to the menu, it only affects "purge-kernels". I Thank you alot for your clarification above, now multiversion.kernels adjustments make more sense to me. I in my shallow mind was somehow thinking that the multiversion.kernels entry affected the appearance of kernels on the boot menu as well. :|
Does the following entry:
multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
Does this look correct to you? It does, but that I know of the existence of this setting doesn't mean I'm an expert on it :-D
You may be giving yourself less credit than deserved. Upon a few powercycles and /etc/zypp/zypp.conf line 554 modifications I have determined the following. The kernel should be added with nothing more than it's numerical syntax: e. g. 5.13.8-1.1 no syntax of .586 nor prefix of kernel-default. . Current "zypper dup" preformed then powercycled. I have edited /etc/zypp/zypp.conf here to the following, saved file then powercycled the machine: -> multiversion.kernels = latest,latest-1,running,5.13.8-1.1 If I edit /etc/zypp/zypp.conf to the following, save file and powercycle: -> multiversion.kernels = 5.13.8-1.1 Command "zypper -n purge-kernels --dry-run" outputs: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2 Command "rpm -qa | egrep 'nel-pae|nel-def'" outputs: -> kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.13.8-1.1.i686 kernel-pae-5.13.6-1.2.i686 Compaq-nc6400:/etc/zypp>
The procedure would be to write an entry then try if it works. Now, how exactly to "try" without destroying the target is the problem.
What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"? No, the "label" comes from the rpm name.
You mean by executing command (or something of this nature?): > "rpm -qa | egrep 'nel-pae|nel-def'" Is there a command to list all the installed packages (and their states) similar to "dpkg-l | less" for use with openSUSE that you are aware of?
You can see the service that does it: minas-tirith:~ # systemctl cat purge-kernels.service # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/
[Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels
[Install] WantedBy=multi-user.target minas-tirith:~ #
Ok, it runs once soon after boot if file "/boot/do_purge_kernels" exists,
I do not think that purge.kernels-service runs after each boot. Why I am saying this is when I edited /etc/zypp/zypp.conf line 554 to the following: -> multiversion.kernels = 5.13.8-1.1 <- : . Powercycled then in konsole passed the following command as root: -> "zypper -n purge-kernels --dry-run" , I was asked the following: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2 with 5.11.xx being locked nothing in reference to 5.11.xx appeared.
root is writeable, then fires "/usr/bin/zypper -n purge-kernels", and finally deletes "/boot/do_purge_kernels".
Thus, you can manually run "/usr/bin/zypper -n purge-kernels". But perhaps reading the manual we can find if there is a way to run it without actually /running/ it.
Mmm... I don't see what '-n' does.
You could try "--dry-run"
minas-tirith:~ # zypper --dry-run -n purge-kernels The flag --dry-run is not known. minas-tirith:~ # minas-tirith:~ # zypper -n purge-kernels --dry-run Reading installed packages...
Preparing to purge obsolete kernels... Configuration: latest,latest-1,running Running kernel release: 5.3.18-lp152.84-default Running kernel arch: x86_64
Resolving package dependencies... Nothing to do. minas-tirith:~ #
Ok, there you have a test method :-) Excellent work, noted. 😁
Passing command "rpm -qa | egrep 'nel-pae|nel-def' in konsole currently returns 3 kernels:
kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686
I would imagine that adding the correct 5.11.xx kernel label to multiversion.kernels that the boot menu would then have 4 various kernel's eventually displayed is this correct? How to display the kernels in boot is decided, I don't know how it is decided. I suppose that at some point zypper sees what is installed and writes the menu.
Would you have any further suggestions or even a potential to keep 4 of the past kernels instead of only 3? If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure. If I were to disable the "purge-kernels.service" do each of the eventually/additionally installed kernels appear on the machines bootmenu? How many kernels can Tumbleweed successfully have installed? I have no idea of the limit.
Disabling purge-kernels would not have effect on the menu. Something (zypper?) would see the installed kernels and write the appropriate menu. AFAIK, there is something you can run yourself and write the boot menu solely, but this instant I'm unsure. Could be:
grub2-mkconfig -o /boot/grub2/grub.cfg Now the above command you describe is updating grub, grub2 perhaps? On
There is no "/boot/do_purge_kernels" file living here currently. There is a boot.readme file in /boot though. Could this be triggered by zypper perhaps? Perhaps I am incorrect completely. :| the laptop here I am using Grub2 with Trusted Boot Support currently.
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:
-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:
/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R. :-)
I seem to recall an rpm named something like kernel-docs :-?
[...]
Yes! It still exists, I just looked. And an html version. But I have no idea what it contains exactly. Maybe that directory, or that directory processed and copied somewhere else.
... Now this "kernel-docs" rpm is basically the same as kernel-sources is for the 5.11.xx ? YaST does not appear to show a kernel-sources package for the 5.13.xx kernel.
I'm not sure what it contains.
I assume it contains the same as the documentation in the source tree, without having to install the huge source package, but I don't know.
What you are trying to convey is reading through "kernel-docs" package would be my starting point for any additional packages in relation to the 5.13.xx kernel? Huh, no.
What I am trying to ask, is, can you suggest when the machine is running under the 5.13.xx kernel what would be the first document to review as far as major-minor in /dev..... It is possible that the kernel-doc package contains that file(s) too. I think so, but I don't know.
It's noted.
I have certainly noted as Felix Miata stated previously, and I quote: "If you have any kernel that works, that one is all you need for normal use".
I thank you for your help with this and before. I am extremely happy with the laptop right now. I have a desktop with TDE KDE installed and it's wonderful and robust also. :-)
-Wishes
* -pj
On 8/9/21 5:16 AM, Carlos E. R. wrote:
On 09/08/2021 09.09, -pj wrote:
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500): How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll". Compaq-nc6400:/etc/zypp> zypper ll
# | Name | Type | Repository | Comment --+-----------------------------+---------+------------+-------- 1 | kernel-default | package | (any) | 2 | kernel-default-base | package | (any) | 3 | kernel-default-base-rebuild | package | (any) | 4 | kernel-default-devel | package | (any) | 5 | kernel-devel | package | (any) | 6 | kernel-source | package | (any) |
Compaq-nc6400:/etc/zypp>
Do you know why the following repository is: -> https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar...
Not listed in the repository field above?
Yes, I can see this repository is installed with: System -> Yast -> Software -> Software Repositories -> tiwai_kernel_5.11 (I still have the above 6 listed packages locked obviously).
Not the only one:
cat /etc/zypp/locks Noted thanks.
> I believe the purge-kernels service is active by default right? Yes.
> Currently here multiversion.kernels line 554: 1 multiversion.kernels = > latest,latest-1,running I edited line 554 of /etc/zypp/zypp.conf to the following: > multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
I powercycled (noted no change in boot menu entries) then reverted to default: > multiversion.kernels = latest,latest-1,running AFAIK that change does nothing to the menu, it only affects "purge-kernels". I Thank you alot for your clarification above, now multiversion.kernels adjustments make more sense to me. I in my shallow mind was somehow thinking that the multiversion.kernels entry affected the appearance of kernels on the boot menu as well. :|
Does the following entry:
multiversion.kernels = latest,latest-1,running,5.11.16-1.ge06d321
Does this look correct to you? It does, but that I know of the existence of this setting doesn't mean I'm an expert on it :-D
You may be giving yourself less credit than deserved. Upon a few powercycles and /etc/zypp/zypp.conf line 554 modifications I have determined the following. The kernel should be added with nothing more than it's numerical syntax: e. g. 5.13.8-1.1 no syntax of .586 nor prefix of kernel-default. .
Current "zypper dup" preformed then powercycled.
I have edited /etc/zypp/zypp.conf here to the following, saved file then powercycled the machine: -> multiversion.kernels = latest,latest-1,running,5.13.8-1.1
If I edit /etc/zypp/zypp.conf to the following, save file and powercycle: -> multiversion.kernels = 5.13.8-1.1
Command "zypper -n purge-kernels --dry-run" outputs: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2
Command "rpm -qa | egrep 'nel-pae|nel-def'" outputs: -> kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.13.8-1.1.i686 kernel-pae-5.13.6-1.2.i686 Compaq-nc6400:/etc/zypp>
The procedure would be to write an entry then try if it works. Now, how exactly to "try" without destroying the target is the problem.
What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"? No, the "label" comes from the rpm name.
You mean by executing command (or something of this nature?): > "rpm -qa | egrep 'nel-pae|nel-def'"
Is there a command to list all the installed packages (and their states) similar to "dpkg-l | less" for use with openSUSE that you are aware of?
You can see the service that does it: minas-tirith:~ # systemctl cat purge-kernels.service # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/
[Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels
[Install] WantedBy=multi-user.target minas-tirith:~ #
Ok, it runs once soon after boot if file "/boot/do_purge_kernels" exists,
I do not think that purge.kernels-service runs after each boot. Why I am saying this is when I edited /etc/zypp/zypp.conf line 554 to the following: -> multiversion.kernels = 5.13.8-1.1 <- : . Powercycled then in konsole passed the following command as root: -> "zypper -n purge-kernels --dry-run" , I was asked the following: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2 with 5.11.xx being locked nothing in reference to 5.11.xx appeared.
There is no "/boot/do_purge_kernels" file living here currently. There is a boot.readme file in /boot though.
Could this be triggered by zypper perhaps? Perhaps I am incorrect completely. :|
root is writeable, then fires "/usr/bin/zypper -n purge-kernels", and finally deletes "/boot/do_purge_kernels".
Thus, you can manually run "/usr/bin/zypper -n purge-kernels". But perhaps reading the manual we can find if there is a way to run it without actually /running/ it.
Mmm... I don't see what '-n' does.
You could try "--dry-run"
minas-tirith:~ # zypper --dry-run -n purge-kernels The flag --dry-run is not known. minas-tirith:~ # minas-tirith:~ # zypper -n purge-kernels --dry-run Reading installed packages...
Preparing to purge obsolete kernels... Configuration: latest,latest-1,running Running kernel release: 5.3.18-lp152.84-default Running kernel arch: x86_64
Resolving package dependencies... Nothing to do. minas-tirith:~ #
Ok, there you have a test method :-) Excellent work, noted. 😁
Passing command "rpm -qa | egrep 'nel-pae|nel-def' in konsole currently returns 3 kernels:
kernel-default-5.11.16-1.1.ge06d321.i586 kernel-pae-5.12.13-1.1.i686 kernel-pae-5.13.6-1.2.i686
I would imagine that adding the correct 5.11.xx kernel label to multiversion.kernels that the boot menu would then have 4 various kernel's eventually displayed is this correct? How to display the kernels in boot is decided, I don't know how it is decided. I suppose that at some point zypper sees what is installed and writes the menu.
> Would you have any further suggestions or even a potential to > keep 4 of the past kernels instead of only 3? If you have any kernel that works, that one is all you need for normal use. If you expect to ever do any kernel bisection looking for when a bug first appeared, it's convenient not to have deleted older kernels. For most people, there's no point in changing multiversion.kernels. If you're more comfortable keeping more, go ahead and keep more. Another option is to disable purge-kernels.service and delete kernels manually at your pleasure. If I were to disable the "purge-kernels.service" do each of the eventually/additionally installed kernels appear on the machines bootmenu? How many kernels can Tumbleweed successfully have installed? I have no idea of the limit.
Disabling purge-kernels would not have effect on the menu. Something (zypper?) would see the installed kernels and write the appropriate menu. AFAIK, there is something you can run yourself and write the boot menu solely, but this instant I'm unsure. Could be:
grub2-mkconfig -o /boot/grub2/grub.cfg Now the above command you describe is updating grub, grub2 perhaps? On the laptop here I am using Grub2 with Trusted Boot Support currently.
I am interested in kernel-sources for 5.13.xx series due to the following, well basically additional documentation:
-----> There was a text file in "/usr/src/linux/Documentation" (if the kernel sources are installed) that described every possible device file in /dev. I can not find it now. Ah! Found it:
/usr/src/linux/Documentation/admin-guide/devices.txt The other important data in /dev is the Major-Minor numbers. <----- Compliments to Carlos E.R. :-)
I seem to recall an rpm named something like kernel-docs :-?
[...]
Yes! It still exists, I just looked. And an html version. But I have no idea what it contains exactly. Maybe that directory, or that directory processed and copied somewhere else.
... Now this "kernel-docs" rpm is basically the same as kernel-sources is for the 5.11.xx ? YaST does not appear to show a kernel-sources package for the 5.13.xx kernel.
I'm not sure what it contains.
I assume it contains the same as the documentation in the source tree, without having to install the huge source package, but I don't know.
What you are trying to convey is reading through "kernel-docs" package would be my starting point for any additional packages in relation to the 5.13.xx kernel? Huh, no.
What I am trying to ask, is, can you suggest when the machine is running under the 5.13.xx kernel what would be the first document to review as far as major-minor in /dev..... It is possible that the kernel-doc package contains that file(s) too. I think so, but I don't know. It's noted.
I have certainly noted as Felix Miata stated previously, and I quote: "If you have any kernel that works, that one is all you need for normal use".
I thank you for your help with this and before. I am extremely happy with the laptop right now. I have a desktop with TDE KDE installed and it's wonderful and robust also. :-) -Wishes
you need to *specify* a particular repo if that is what you desire. and some trimming might be appropriate. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
-pj composed on 2021-08-17 16:17 (UTC-0500):
Is there a command to list all the installed packages (and their states) similar to "dpkg-l | less" for use with openSUSE that you are aware of? My installations have scripts I use for zypper routines: # l /usr/local/bin/zyp* -rwxr-xr-x 1 root root 109 Mar 1 2017 /usr/local/bin/zypse* -rwxr-xr-x 1 root root 112 Mar 6 2017 /usr/local/bin/zypsei* -rwxr-xr-x 1 root root 115 Aug 7 01:35 /usr/local/bin/zypseinvk* -rwxr-xr-x 1 root root 279 Aug 7 01:35 /usr/local/bin/zypsek* -rwxr-xr-x 1 root root 74 Oct 4 2017 /usr/local/bin/zypseo* -rwxr--r-- 1 root root 263 Jun 6 01:35 /usr/local/bin/zypstart* # cat /usr/local/bin/zypsei #!/bin/sh zypper --no-refresh se -s -i $* | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort
The two new ones are a result of the new repos and additional kernels for 15.3: # cat /usr/local/bin/zypseinvk #!/bin/sh echo "zypper -v in kernel-default kernel-default-extra" zypper -v in kernel-default kernel-default-extra # cat /usr/local/bin/zypsek #!/bin/sh echo "zypper --no-refresh se -s kernel-default | egrep -v 'extra|opt|base|live|debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort" zypper --no-refresh se -s kernel-default | egrep -v 'extra|opt|base|live|debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2021-08-17 at 16:17 -0500, -pj wrote: El 2021-08-17 a las 16:17 -0500, -pj escribió:
On 8/9/21 5:16 AM, Carlos E. R. wrote:
On 09/08/2021 09.09, -pj wrote:
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500): How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll". Compaq-nc6400:/etc/zypp> zypper ll
# | Name | Type | Repository | Comment --+-----------------------------+---------+------------+-------- 1 | kernel-default | package | (any) | 2 | kernel-default-base | package | (any) | 3 | kernel-default-base-rebuild | package | (any) | 4 | kernel-default-devel | package | (any) | 5 | kernel-devel | package | (any) | 6 | kernel-source | package | (any) |
Compaq-nc6400:/etc/zypp>
Do you know why the following repository is: -> https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar...
Not listed in the repository field above?
Maybe nothing is locked from there :-? Dunno.
Yes, I can see this repository is installed with: System -> Yast -> Software -> Software Repositories -> tiwai_kernel_5.11 (I still have the above 6 listed packages locked obviously).
...
The procedure would be to write an entry then try if it works. Now, how exactly to "try" without destroying the target is the problem.
What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"? No, the "label" comes from the rpm name.
You mean by executing command (or something of this nature?): > "rpm -qa | egrep 'nel-pae|nel-def'"
cer@Telcontar:~> rpm -qa | grep kernel-def kernel-default-5.3.18-lp152.78.1.x86_64 <==== kernel-default-devel-5.3.18-lp152.75.1.x86_64 kernel-default-5.3.18-lp152.87.1.x86_64 <==== kernel-default-devel-5.3.18-lp152.78.1.x86_64 kernel-default-devel-5.3.18-lp152.87.1.x86_64 cer@Telcontar:~> uname -a Linux Telcontar 5.3.18-lp152.87-default #1 SMP Sun Aug 8 21:53:57 UTC 2021 (44d702a) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> The arrow indicates the rpm names that I mean. It matches the uname, but it is not the same thing.
Is there a command to list all the installed packages (and their states) similar to "dpkg-l | less" for use with openSUSE that you are aware of?
I don't know what "dpkg-l | less" does...
You can see the service that does it: minas-tirith:~ # systemctl cat purge-kernels.service # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/
[Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels
[Install] WantedBy=multi-user.target minas-tirith:~ #
Ok, it runs once soon after boot if file "/boot/do_purge_kernels" exists,
I do not think that purge.kernels-service runs after each boot.
The service file evaluates on every boot, and if the file "/boot/do_purge_kernels" exists then it starts the program. If it does not exist, then the command does not run.
Why I am saying this is when I edited /etc/zypp/zypp.conf line 554 to the following: -> multiversion.kernels = 5.13.8-1.1 <- : . Powercycled then in konsole passed the following command as root: -> "zypper -n purge-kernels --dry-run" , I was asked the following: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2 with 5.11.xx being locked nothing in reference to 5.11.xx appeared.
There is no "/boot/do_purge_kernels" file living here currently. There is a boot.readme file in /boot though.
Could this be triggered by zypper perhaps? Perhaps I am incorrect completely. :|
zypper creates the flag file "/boot/do_purge_kernels". ...
I have no idea of the limit.
Disabling purge-kernels would not have effect on the menu. Something (zypper?) would see the installed kernels and write the appropriate menu. AFAIK, there is something you can run yourself and write the boot menu solely, but this instant I'm unsure. Could be:
grub2-mkconfig -o /boot/grub2/grub.cfg Now the above command you describe is updating grub, grub2 perhaps? On the laptop here I am using Grub2 with Trusted Boot Support currently.
grub2, of course. Grub1 we can consider that doesn't exist for practical purposes, so when people say "grub" they actually mean version 2. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYSYRSRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVvrsAoIcvVg3Vf1s/1Zkb3LRB h5WxmWP/AJ9UrHueqoFG1Nee2b5HBOWtyeOOzA== =QDU6 -----END PGP SIGNATURE-----
participants (4)
-
-pj -
Carlos E. R. -
Felix Miata -
Patrick Shanahan