Re: Kernel compile and install does not create initrd
On Sat, Jan 16, 2010 at 2:44 PM, Hugo Vanwoerkom <hvw59601@care2.com> wrote:
> Patrick Wiseman wrote:
>>
>> I have compiled a custom kernel, using 'make-kpkg clean && make-kpkg
>> --initrd --revision=sage.1.0 kernel-image', 'sage' being the name of
>> my machine. I then installed it, using 'dpkg -i
>> linux-image-2.6.30_sage.1.0_amd64.deb'. I had thought that would be
>> enough to create the initrd necessary to boot, but there is no
>> initrd-image in /boot corresponding to the kernel, and (of course)
>> none listed in /boot/grub/menu.lst for this kernel's entry. So (again
>> of course) there's a kernel panic when I attempt to boot using this
>> kernel. I tried dpkg-reconfigure on the kernel, but no joy.
>> initramfs and initrd support are enabled in my kernel config. So can
>> anyone tell me what I'm doing wrong? (I'm sure it's obvious, but I'm
>> not seeing it, and I've read the relevant sections of the Debian Linux
>> Kernel Handbook.)
>>
>
> If this is the latest version of make-kpkg, did you
> cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs
> /etc/kernel/postinst.d/
> cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs
> /etc/kernel/postrm.d/
> ?
Uh, no, I didn't. I have now. And dkpg-reconfigure has now created
the initrd image, and grub has found it. Thanks! (I appreciate the
help, but where should I have looked? My googling did not turn up
that solution! And neither did 'man make-kpkg', although I see now
there's some obtuse language in there which is perhaps meant to convey
the same information.)
Patrick
Reply to: