Bug#579336: update-initramfs: recognize (and ignore?) moduleless/ramdiskless kernels.
On Tue, Apr 27, 2010 at 02:47:38PM +1000, Trent W. Buck wrote:
> Package: initramfs-tools
> Version: 0.94.4
> Severity: wishlist
>
> Following the kernel handbook, I built a mainline kernel using "make
> deb-pkg".
ok, fine so far.
>This kernel is configured without modules or initrd support.
pretty sure that this is not a recommended way by referenced book.
with a gun one can also shoot oneself into onselves foot..
> On installing it with dpkg -i, I got this:
>
> $ sudo dpkg -i ../linux-image-2.6.34-rc5_twb1_amd64.deb
> Preparing to replace linux-image-2.6.34-rc5 twb1 (using .../linux-image-2.6.34-rc5_twb1_amd64.deb) ...
> Unpacking replacement linux-image-2.6.34-rc5 ...
> Setting up linux-image-2.6.34-rc5 (twb1) ...
> update-initramfs: Generating /boot/initrd.img-2.6.34-rc5
> WARNING: missing /lib/modules/2.6.34-rc5
> Device driver support needs thus be built-in linux image!
> WARNING: Couldn't open directory /lib/modules/2.6.34-rc5: No such file or directory
> FATAL: Could not open /lib/modules/2.6.34-rc5/modules.dep.temp for writing: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
> FATAL: Could not load /lib/modules/2.6.34-rc5/modules.dep: No such file or directory
>
> It would be better if initramfs-tools 1) wasn't run in the first
> place; or
people explicitly asked for it to be run as nowadays people
expect to initramfs just to be generated.
> 2) gave a clearer error message, such as:
>
> update-initramfs: Generating /boot/initrd.img-2.6.34-rc5
> WARNING: CONFIG_MODULES=n in 2.6.34-rc5, a ramdisk is likely useless.
> FATAL: CONFIG_BLK_DEV_INITRD=n in 2.6.34-rc5, a ramdisk is useless.
>
> In particular, this current warning is unintelligible:
>
> Device driver support needs thus be built-in linux image!
lol indeed this was a funny minute when I put that in.
the meaning is that you'd better really have everything built in.
for eventual MODULES config settings we have now way to know.
> If the problem is in the kernel -- if "make deb-pkg" always invokes
> update-initramfs, but shouldn't -- let me know and I'll take this
> issue upstream.
if your box does not need initramfs-tools why would it be there.
once you remove it, it can't be run.
good luck in going down that road without UUID support, nor
md support.
Reply to: