> > If I exclude [loadable module support] then mkinitramfs-kpkg fails,
> > and if I include it then mkinitramfs-kpkg succeeds.
>
> If you don't need loadable modules, then ... you don't need an init*
> because all the stuff you need is already in the kernel.
That does seem to make sense. Howeve
On Thu, Jan 04, 2007 at 10:33:20PM +0100, Matt Miller wrote:
> > Using mkinitramfs-kpkg to build the ramdisk.
> > mkinitramfs-kpkg failed to create initrd image.
> > ...
> > I'm guessing that I'm missing something else in
> > menuconfig.
>
>
> Using mkinitramfs-kpkg to build the ramdisk.
> mkinitramfs-kpkg failed to create initrd image.
> ...
> I'm guessing that I'm missing something else in
> menuconfig.
Loadable module support. If I exclude it then
mkinitramfs-kpkg fails, and if I include it then
mkinitr
> > Using mkinitramfs-kpkg to build the ramdisk.
> > mkinitramfs-kpkg failed to create initrd image.
>
> there is an initrd support option in menuconfig
I think I selected the necessary options:
[EMAIL PROTECTED]:/usr/src/linux-source-2.6.18$ grep -i ram .config
CONFI
s before on this same
> machine without a problem, but this one is giving me:
>
> ...
> Using mkinitramfs-kpkg to build the ramdisk.
> mkinitramfs-kpkg failed to create initrd image.
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.18-xpc2-4-jan-2007 (
...
Using mkinitramfs-kpkg to build the ramdisk.
mkinitramfs-kpkg failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.18-xpc2-4-jan-2007 (--install):
subprocess post-installation script returned error exit status 9
I'm trying to build a stripped
6 matches
Mail list logo