(CCing debian-boot and quoting full message as that is the proper list for this subject) On Friday 25 February 2005 18:28, Dennis Wicks wrote: > When installing a kernel that uses an initrd the install process > abends because the default in /etc/kernel-img.conf is wrong and > when the installer responds with, I preseme, a CR then dpkg is > aborted. As far as I have been able to determine there is > now way to continue from this point. All options result in the > /etc/kernel-img.conf file being replaced with the one containing the > do_initrd = No option that causes the problem. Following is the > contents of /var/log/messages leading up to the abort. The prompt and > response is flagged with >>>>> > > Selecting previously deselected package kernel-image-2.6.8-2-s390. > Unpacking kernel-image-2.6.8-2-s390 (from > .../kernel-image-2.6.8-2-s390_2.6.8-5_s390.deb) ... > > You are attempting to install an initrd kernel image (version > 2.6.8-2-s390) This will not work unless you have configured your boot > loader to use initrd. (An initrd image is a kernel image that expects > to use an INITial Ram Disk to mount a minimal root file system into RAM > and use that for booting). > > I repeat, You need to configure your boot loader -- please read your > bootloader documentation for details on how to add initrd images. > > If you have already done so, and you wish to get rid of this message, > please put > "do_initrd = Yes" > in /etc/kernel-img.conf. Note that this is optional, but if you do not, > you will continue to see this message whenever you install a kernel > image using initrd. > > >>>>> Do you want to stop now? [Y/n]Ok, Aborting > > dpkg: error processing > /var/cache/apt/archives/kernel-image-2.6.8-2-s390_2.6.8-5_s390.deb > (--unpack) > > subprocess pre-installation script returned error exit status 1 > Errors were encountered while processing: > /var/cache/apt/archives/kernel-image-2.6.8-2-s390_2.6.8-5_s390.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Did you boot the installer with the 2.4.27 kernel? If so, you were possibly bitten by a bug that was identified (for powerpc) and solved. The bug was that the decision whether or not an initrd is needed was made on the version of the kernel the installer was booted with, rather than the kernel the user has chosen for the new system. Could you please file an installation report [1] for this issue with details of you installation so we can check if its been resolved? [1] http://www.debian.org/devel/debian-installer/report-template Cheers, FJP
Attachment:
pgpOrEmhTgUNx.pgp
Description: PGP signature