Bug#253197: Fix for the problem

[Frans Pop <aragorn@tiscali.nl>]

On Monday 02 May 2005 04:53, Chad Martin wrote:
> Just setting the version to 2.4 or 2.6 does not match the available
> kernel-image names.  Those names look like 2.6.8-2-686 or
> 2.6.8-10-em64t. The "." in the "cut" command needs to be a "-".

No, what we want to install is one of the following packages. These 
packages help kernel upgrades: the actual kernel-images are pulled in by 
dependencies from these.
Automatic selection of the em64t kernels are currently not supported by 
the installation system.

kernel-image-2.4
kernel-image-2.4-386
kernel-image-2.4-586tsc
kernel-image-2.4-686
kernel-image-2.4-686-smp
kernel-image-2.4-k6
kernel-image-2.4-k7
kernel-image-2.4-k7-smp

kernel-image-2.6
kernel-image-2.6-386
kernel-image-2.6-686
kernel-image-2.6-686-smp
kernel-image-2.6-k7
kernel-image-2.6-k7-smp

I would expect the kernel-image-2.[46]-686-smp images to be the correct 
ones for dual Xeon.
If you want to be able to select a different kernel-image, you should 
install at medium or low (expert) priority.

We really need the output of 'cat /proc/cpuinfo' from the original 
submitter of the report (or someone having the same setup) to check if 
our kernel selecting rules need changing.

Cheers,
FJP