You add these (do not include the quotes “”) using YaST / Software / Software Repositories then you use YaST / Software / Software Management, search on kernel, and use the versions tab to select the kernel version you want to install. I might suggest you also enable the ability to maintain more than one kernel version in zypp just in case a newer version did not work.
I suggest you open up the file zypp.conf from the folder** /etc/zypp** as root, find the code below and remove the comment # from the line that says multiversion = provides:multiversion(kernel)
## Packages which can be installed in different versions at the same time.
## Packages are selected either by name, or by provides. In the later case
## the string must start with "provides:" immediately followed by the capability.
## kernel - just packages whith name 'kernel'
## provides:multiversion(kernel) - all packages providing 'multiversion(kernel)'
## (kenel and kmp packages should do this)
## Valid values:
## Comma separated list of packages.
## Default value:
multiversion = provides:multiversion(kernel)
In KDE Do: Alt-F2: kdesu kwrite /etc/zypp/zypp.conf
In Gnome Do: Alt-F2: gnomesu gedit /etc/zypp/zypp.conf
Enter the root user password, make the suggested change as shown above and then save the file. I think when you run YaST next, the change will take place, but a restart might be good as well. Basically, you will now maintain more that one version of the linux kernel and you must explicitly uncheck any kernel version in YaST so that it will be removed.
I am now running 3.1.10-54-desktop thanks to your instructions.
Just wondered how much testing the 3.1.10-54 kernel gets?
Looking at the change log it is full of back ports from latter kernels.
I am guessing this is done so we can stay on the kernel version that 12.1 was shipped with although the more backports in there the less like 3.1.10 it becomes.
Seems like a lot of work for a repo that isnt included in the default list of repos. (not complaining because it contains exactly what I need thanks to the maintainer).
Just trying to guage who is using this repo and therefore how much testing it is getting.
So I can not exactly say how much testing goes on for the openSUSE repository. If you can imagine, anyone can report a bug with a present openSUSE version and if its bad enough, everyone gets it and if not, it goes into the latest kernel repository only. Same for general fixes for the kernel were we all get security fixes, but not all hardware fixes go into the main kernel. Right now, another thing has happened that makes this separate kernel repository more important. At The Linux Kernel Archives, the 3.1.10 kernel has been declared as being at End Of Life (EOL) and the meaning of which you can read here: End-of-life (product) - Wikipedia, the free encyclopedia. So if you get any fixes at all for 3.1, it will be in this special openSUSE repository until openSUSE 12.1 is declared at being the end of its life as well. Of course, you can use my bash script SAKC to load any released kernel version into your openSUSE version if you wish.