Bug#445735: image creation fails with a non-modular kernel
On Mon, Oct 08, 2007 at 08:35:14PM -0400, Brad Jorsch wrote: On Mon, Oct 08, 2007 at 09:00:09AM +0200, maximilian attems wrote: boring and yes modular kernel are recommended! Other people recommend a non-modular kernel, especially if no modules are needed. There is no reason not to support this configuration. I second fixing this issue. I just came across this while upgrading 2.4 to 2.6. Non-modular kernels which require initrd are not that unusual, IMHO. Especially not for servers where you need to run lvm (like the submitter), md (like me) or where you need to load firmwares early. best regards thanks for your work Mario -- But after a while I learned the trick of speaking fast. You don't have to think any faster; just use twice as many words to say everything. -- Paul Graham signature.asc Description: Digital signature
Bug#445735: image creation fails with a non-modular kernel
On Sun, Oct 07, 2007 at 11:17:32PM -0400, Brad Jorsch wrote: I compiled a kernel using kernel-package, with CONFIG_MODULES not set since this machine is not going to need to load any modules. When trying to install the generated .deb, I get the following error: Executing update-initramfs with the -v option gives more information: # update-initramfs -c -v -k linux-image-2.6.22.9 update-initramfs: Generating /boot/initrd.img-linux-image-2.6.22.9 Cannot find /lib/modules/linux-image-2.6.22.9 update-initramfs: failed for /boot/initrd.img-linux-image-2.6.22.9 Unless I'm mistaken, an initramfs is still required if / is on an LVM2 logical volume. bah this is a duplicate bug report. boring and yes modular kernel are recommended! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445735: image creation fails with a non-modular kernel
Processing commands for [EMAIL PROTECTED]:
merge 445735 433708
Bug#433708: initramfs-tools: Wants to have /lib/modules/${version}/ present
when creating initramfs even under kernel without modules support
Bug#445735: image creation fails with a non-modular kernel
Merged 433708 445735.
tags 445735 patch
Bug#445735: image creation fails with a non-modular kernel
There were no tags set.
Bug#433708: initramfs-tools: Wants to have /lib/modules/${version}/ present
when creating initramfs even under kernel without modules support
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445735: image creation fails with a non-modular kernel
merge 445735 433708
tags 445735 patch
thanks
On Mon, Oct 08, 2007 at 09:00:09AM +0200, maximilian attems wrote:
bah this is a duplicate bug report.
boring and yes modular kernel are recommended!
bah, that was a useless reply.
Other people recommend a non-modular kernel, especially if no modules
are needed. There is no reason not to support this configuration.
Here's another patch, a little less quick and dirty than the one in
433708. Works for me, but I can't promise it doesn't break someone's
hook script somewhere.
--- /usr/sbin/mkinitramfs 2007-10-09 00:21:04.0 +
+++ /usr/sbin/mkinitramfs 2007-10-09 00:21:12.0 +
@@ -155,7 +155,11 @@
if [ ! -e ${MODULESDIR} ]; then
echo Cannot find ${MODULESDIR}
- exit 1
+# exit 1
+else
+ if [ ! -e ${MODULESDIR}/modules.dep ]; then
+ depmod ${version}
+ fi
fi
DESTDIR=$(mktemp -t -d mkinitramfs_XX) || exit 1
Bug#445735: image creation fails with a non-modular kernel
Package: initramfs-tools Version: 0.91b I compiled a kernel using kernel-package, with CONFIG_MODULES not set since this machine is not going to need to load any modules. When trying to install the generated .deb, I get the following error: Setting up linux-image-2.6.22.9 (3:2.6.22.9.anomie1) ... Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. mkinitramfs-kpkg failed to create initrd image. Failed to create initrd image. Executing update-initramfs with the -v option gives more information: # update-initramfs -c -v -k linux-image-2.6.22.9 update-initramfs: Generating /boot/initrd.img-linux-image-2.6.22.9 Cannot find /lib/modules/linux-image-2.6.22.9 update-initramfs: failed for /boot/initrd.img-linux-image-2.6.22.9 Unless I'm mistaken, an initramfs is still required if / is on an LVM2 logical volume. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
