I currently have 2.6.31.8 installed on my netbook which causes problems, causing the netbook to freeze.
So, I downgraded to 2.6.31.5 and is working properly. Using Yast, I had marked 2.6.31.8 as do not install but after several days of use (by my kids) 2.6.31.8 mysteriously comes back and the system freeze again >:(
How can I have 2.6.31.8 and 2.6.31.5 both installed on the same system so that I can avoid the trouble to manually reinstall 2.6.31.5?
You install 2.6.31.5 in parallel with the newer one and don’t delete the newer one. You might have to do this in YaST or even the command line because the default action of the updater is to only keep the latest. FYI, from the command line, locate and download the RPM file you need, and the command will be something like:
rpm -i --force kernel-default-2.6.31.5.i586.rpm
You should end up with two sets of entries in GRUB, I think two entries for each version. You can then make the older one the default from YaST.
Thanks Ken,
now I’ve both 2.6.31.5 and 2.6.31.8 in grub and even went into yast to lock up 2.6.31.5, hope this will solve my problem 
ken yap wrote:
> You install 2.6.31.5 in parallel with the newer one and don’t delete the
> newer one. You might have to do this in YaST or even the command line
> because the default action of the updater is to only keep the latest.
> FYI, from the command line, locate and download the RPM file you need,
> and the command will be something like:
>
> rpm -i --force kernel-default-2.6.31.5.i586.rpm
In fact the canonical way is to set “multiversion” in
/etc/zypp/zypp.conf correctly, e.g.: multiversion = kernel-default
Good luck,
Andreas Stieger
Ah, learnt something new. Does this prevent updates from deleting the previous version? I’ve wanted this functionality for a long time. It’s so annoying when a kernel update breaks the computer and there’s no easy way to go back.
ken yap wrote:
> Does this prevent updates from deleting the previous version?
Yes, “zypper up” will offer to install the new version in addition to
the installed one instead of upgrading it.
With kind regards,
Andreas Stieger
Just make sure you don’t run out of space in /boot because mutiversion does not limit the number of kernels it will keep. As long as you keep an eye on it, it should be fine though. 
This is assuming that your /boot is on a small separate partition
Or / is on a small partition.
On Sat, 06 Feb 2010 00:36:01 GMT, Wilson Phillips <Wilson_Phillips@no-mx.forums.opensuse.org> wrote:
>
>microchip8;2115512 Wrote:
>> This is assuming that your /boot is on a small separate partition
>
>Or / is on a small partition.
Yes this will sometimes be to the point. Not everybody can afford hundreds of
gigabytes of disk. And some others will have to design / install to very
resource constrained targets. Others will have disk space to waste, but chose
poor partition sizes. There will be many more variations that than i havenoted.
But in essence no different a problem than proposed packages overflowing available space. And amenable to the same solutions already implemented in other distros. Firstly, if the available space is insufficient, the transaction doesn’t go through and the worst that happens is the installation remains on an older version of the package. Secondly, to be able to specify and enforce a limit on multiversions retained.
All doable and I hope will in place by 11.3. About time.
I very much agree!