Retaining previous kernel boot option?

Thanks
Please report your findings

OK. I installed the previous kernel on the test machine and it booted it. fine. It did change the boot order in GRUB so the newer kernel is not the default. I think I can change GRUB from YAST to reorder it though. It’s a test box and boots Mandriva 2007 normally to play NWN and a old version of Urban Terror so no big deal I have to select the OS I am booting anyway.

edit
GRUB Boot order changed and it’s working just fine

This is what I found:

http://dl.dropbox.com/u/10573557/SUSE%20Misc/multi-v%20hash%20removed.png

http://dl.dropbox.com/u/10573557/SUSE%20Misc/multi-v%20allchecked.png

This is very interesting.

When I did my experiment I searched kernel-desktop and only saw the desktop default kernels.
So I wouldn’t have noticed the difference you spotted.
I obviously want the result of “multiversion = provides:kernel-desktop”

I’ll test it on my test box as well right now. (saving up to build a more current system for testing)

It seems that the default installed kernel isn’t a desktop kernel on that machine rather it’s a “default” kernel. When I installed the desktop kernel I did not get a WM when I tried to boot it. Booting to the installed “default kernel” gives me a WM. I’ll have to poke around a bit and see what I can make happen. This old machine is not such a great machine.

“provides:kernel-desktop” does only allow the kernel-desktop to be selected as only the radio buttons were displayed under the default kernels and the desktop kernels have tick boxes and were selectable.

Posting from my test box with linux-c6ju 2.6.34.7-0.3-desktop #1 SMP PREEMPT 2010-09-20 15:27:38 +0200 i686 athlon i386 GNU/Linux.

I figure in about five more weeks I might have the money to build a modern four core desktop testing machine around a Phenom II 955 and a Gigabyte motherboard of some type.

To say the least I am rather confused by your posts just above, considering the image you have in post #9
And that your sig quotes: Linux 2.6.34.7-0.3-desktop

You understand that default, desktop and pae are kernel flavours.
That is: kernel-default (is the openSUSE default kernel)
kernel-desktop (is the kernel enhanced for desktop users/machines) (also does pae)
kernel-pae (addresses >3GB RAM in a 32 environment)

I have two totally different machines in play here. One I can test stuff on without too much fear of breaking things and starting over completely and one which I absolutely don’t want to have to reinstall the OS on if humanly possible.

The old machine had a “default kernel” installed not a desktop kernel. I guess this was by default. This machine has a enhanced desktop kernel installed. I guess by default since I made no conscious choice to install it. They are both running 11.3 KDE 4.4 with the enhanced desktop kernel now.

My zypp.conf file is set for multiversion = provides:kernel-desktop on both of them now.

On 2010-09-29 07:30, malcolmlewis wrote:

> [/QUOTE]
> Hi
> AFAIK, it should be;
>


> multiversion = provides:multiversion(kernel)
> 

Yes, you should then get a ‘checkbox’ under the versions tab as opposed
to a ‘radio’ button.

Curiously, I don’t (11.2 with one kernel update pending).

If I put the line:


multiversion = kernel-desktop

then only the “kernel-desktop” gets the checkbox, not the rest of the kernel rpms. So I have to use:


] multiversion =
kernel-desktop,kernel-debug-devel,kernel-default-devel,kernel-desktop-devel,kernel-source,kernel-syms,kernel-xen,devel,preload-kmp-desktop

which works.

The documentation says:


] ##
] ## 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.
] ##
] ## Example:
] ##      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:
] ##      empty
] ##

They key word is probably the “should” in “(kenel and kmp packages should do this)”. Apparently,
they don’t.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)