tags 655437 + confirmed
thanks
I have to confirm this. This (the problem reported by Martin) is
particularly confusing when several flavours are possible. On a x86-64
system, I get this:
Mar 29 15:53:14 base-installer: info: kernel linux-image-686-pae
usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel linux-image-486 usable on
686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel
linux-image-3.2.0-2-686-pae usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel linux-image-3.2.0-2-486
usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: Found kernels
'linux-image-3.2.0-2-486,linux-image-3.2.0-2-686-pae,linux-image-486,linux-image-686-pae'
Mar 29 15:53:14 base-installer: info: arch_kernel candidates:
linux-image-3.2-686-pae linux-image-3.2-686-bigmem
linux-image-3.2-amd64 linux-image-3.2-686 linux-image-3.2-486
Mar 29 15:53:14 base-installer: info: arch_kernel:
linux-image-3.2-686-pae (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel:
linux-image-3.2-686-bigmem (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel:
linux-image-3.2-amd64 (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: linux-image-3.2-686
(absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: linux-image-3.2-486
(absent)
This needs to be fixed for wheezy. However, since the choices presented
to the user are sorted alphabetically, the current situation must cause
a greater usage of the 486 image on i386, which works around #650819. It
may be wise to wait for #650819 to be fixed before uploading a fix for
this one.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f77899d.2040...@gmail.com