Bug 152118

Created attachment 69216 [details]
All YaST2 Logs and HWinfo

"Non-OSS" selection triggered this

The activation is done by bootloader.

Since kernels are installable in parallel now, it does not seem to be a packager bug to me.

If "Non-OSS" selection should add all kernels is questionable though.

OTOH, users can select whatever kernel they decide. Question, how can bootloader know which is the right one ?

Günther, you write that kernel-smp was activated. Did the system boot ?

Yes, the system is starting wih kernel-smp, afterward I change it to default.

This is the first time i have three kernels ;).

Is this a problem from the boot Parameter "lapic" ?? Without, the installation stops in Yast2, after the license screen.

Additional Info:

On a real smp system (no HT), i have the *-default Kernel from the three Kernels

You should have a boot entry for each of the installed kernels.

No, i have only one and at the end, i mean, a confuse previos Kernel entry.

You should have these sections, using grub and depending on the language:

title SUSE LINUX 10.0.42
kernel /boot/vmlinuz
[...]

title Diskette                          (not sure about this one)
chainloader [...]

title Failsafe -- SUSE LINUX 10.0.42
kernel /boot/vmlinuz
[...]

title Vorheriger Kernel -- SUSE LINUX 10.0.42
kernel /boot/vmlinuz.previous

with /boot/vmlinuz being a link to the last installed kernel,
and /boot/vmlinuz.prevoius being a link to the kernel that was installed next to last.

This would be the expected behaviour

*** Bug 153341 has been marked as a duplicate of this bug. ***

*** Bug 153341 has been marked as a duplicate of this bug. ***

Taking agruen into Cc.

What I can see from the comments is:

  - yast2-packager can now install several kernels in parallel
  - the "Non-OSS" selection includes all kernels

The logs from mkinitrd tell me that indeed three kernels exist: default, smp
and bigsmp.

yast2-bootloader only creates one section. It uses the kernel binary that is
selected by Kernel::ProbeKernel(), which is "vmlinuz" for i386.

So an installation with multiple kernels will only create a section for
"/boot/vmlinuz", which is the link created by the last installed kernel
package.

There is no feature request to change this.

(Also, there is no support in Kernel.ycp for that.)

If we want to change this, we may as well create sections and everything else
from the post-install scripts of the kernel packages. This is what is done on
"rpm -i". Again, there is no feature request for this.

In any case, this is not a simple change, it requires some re-design and
re-coding of yast2-bootloader and perl-Bootloader (to handle multiple
sections).

Open a feature request for this please.

Comment #8: we don't support bootloader entries for each installed kernel; we only create entries for the current and previous kernel. Maybe we can fix this after SLES10 GA.

The selection should not include all three kernels: the last kernel that is installed would get booted, which is usually wrong. AFAIK yast selects an appropriate kernel automatically.

Stefan, can you fix this?

> - the "Non-OSS" selection includes all kernels
No.

The only kernel which is in any selection is kernel-xen (Xen selection). All other kernels are installed by YaST2. Reassigning.

Fixed already, this is a known bug.

I would guess it's bug 156513 then, indeed.