Hi,
On Mon, 30 Apr 2007 13:21:33 +0200, Paul Menzel <[EMAIL PROTECTED]>
said:
> Am Sonntag, den 29.04.2007, 19:25 -0500 schrieb Manoj Srivastava:
>> Probably not, but there is not enough information in this report to
>> determine where the problem does indeed lie. If you could provide a
>> transcript of the installation, it might be easier to see which
>> initrd generation tool was invoked, and why it failed, and if it
>> issued any diagnostics.
> Ok, that's right. Unfortunately I did not find any log files. So I
> redid the whole process and redirected the output into files. See
> attached.
> I removed the kernel-image with dpkg -r, which took also care of the
> initrd file. Afterwards I installed the newly build kernel with dpkg
> -i and no initrd file was there. So it is reproducible for me.
The problem, from what I can tell, is that the kernel package
does not think it was created with --initrd. This is a non-initrd
image, for instance:
__> head -n 50 /var/lib/dpkg/info/linux-image-2.6.21.1-skas3-v8.2.postinst\
| grep initrd
my $initrd = ""; # initrd kernel
my $mkimage = ""; # command to generate the initrd image
my $do_initrd = ''; # Normally we do not
my $warn_initrd = 'YES'; # Normally we do
This is one that is an initrd image:
__> head -n 50 /var/lib/dpkg/info/linux-image-2.6.21.1.postinst | grep initrd
my $initrd = "YES"; # initrd kernel
my $mkimage = ""; # command to generate the initrd image
my $do_initrd = ''; # Normally we do not
my $warn_initrd = 'YES'; # Normally we do
Try yourself with:
head -n 50 /var/lib/dpkg/info/linux-image-2.6.21.1_pm.1.postinst | grep initrd
And see if it was indeed compiled without initrd support.
manoj
--
s = (char*)(long)retval; /* ouch */ --Larry Wall in doio.c from the perl
source code
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
