So I updated tumbleweed and now my bluetooth doesn't work. After some investigation, I plan to file a bug report. It seems the firmware worked with kernel 5.14, but now it doesn't work with 5.15. But for now, as long as I boot into the old kernel, I still can use my bluetooth headphones, and this is important for multiple applications. The kernel I want to use is the 2nd kernel in the list, which is 5.14. I want to preserve this kernel so that on future updates, if they have not solved the bug, the 15.4 kernel will be preserved, but the default kernel, which is 5.15, will be replaced by the next kernel update. Is there a way to do this? At one time in the past I expanded the number of kernels that were in the list of available kernels so that I kept like 6 kernels. I don't remember why I did that, and I don't need that many in any case. However, I don't know how to preserve just one kernel, so that that particular kernel won't be erased, but that updates for other kernels will still load and I will be able to try them. Any ideas? -- George Box: 15.2 | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.2 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: TW | Plasma 5 | Core i7 | 64 | 16GB
George from the tribe composed on 2021-11-26 19:37 (UTC-0600):
I don't know how to preserve just one kernel, so that that particular kernel won't be erased, but that updates for other kernels will still load and I will be able to try them.
Read man zypper, section locks. e.g. sudo zypper al kernel-default-5.14.14* -- 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 Saturday 27 November 2021, Felix Miata wrote:
George from the tribe composed on 2021-11-26 19:37 (UTC-0600):
I don't know how to preserve just one kernel, so that that particular kernel won't be erased, but that updates for other kernels will still load and I will be able to try them.
Read man zypper, section locks.
e.g.
sudo zypper al kernel-default-5.14.14*
There is also multiversion.kernels in /etc/zypp/zypp.conf e.g. ## Comma separated list of kernel packages to keep installed in parallel, if the ## above multiversion variable is set... multiversion.kernels = 5.12.12,latest,latest-1,running I'm not well enough informed to say which approach should be preferred. Cheers, Michael
On 11/26/21 20:31, Michael Hamilton wrote:
On Saturday 27 November 2021, Felix Miata wrote:
George from the tribe composed on 2021-11-26 19:37 (UTC-0600):
I don't know how to preserve just one kernel, so that that particular kernel won't be erased, but that updates for other kernels will still load and I will be able to try them.
Read man zypper, section locks.
e.g.
sudo zypper al kernel-default-5.14.14*
There is also multiversion.kernels in /etc/zypp/zypp.conf
e.g.
## Comma separated list of kernel packages to keep installed in parallel, if the ## above multiversion variable is set...
multiversion.kernels = 5.12.12,latest,latest-1,running
I'm not well enough informed to say which approach should be preferred.
Cheers, Michael
Thanks - I did both. I put a lock using zypper al kernel-default-5.14.14 I also modified this line in the /etc/zypp/zypp.conf: multiversion.kernels = 5.14.14-2.1,latest,latest-1,running I hope those will not cause some kind of redundancy conflict. -- George Box: 15.2 | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.2 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: TW | Plasma 5 | Core i7 | 64 | 16GB
participants (3)
-
Felix Miata -
George from the tribe -
Michael Hamilton