> > 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.
>
> Loadable module support. If I exclude it then
> mkinitr
> 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
mkinitramfs-kpkg succeeds. This is
> > 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
CONFIG_INITRAMFS_SOURCE=""
CONFIG_
On Thu, Jan 04, 2007 at 07:35:02PM +0100, Matt Miller wrote:
> Under etch I'm trying to use "dpkg -i" to install a .deb I built using
> make-kpkg. I'm passing "--initrd" to make-kpkg, since I'm booting
> off a software RAID device. I've done this before on this same
> machine without a problem, b
5 matches
Mail list logo