Prev: 2.6.14-2-386, missing thermal.ko and initrd
Next: Dicota PC-Link Z14438Z
From: Matt Miller on 5 Jan 2007 12:20
> > 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. However, when I try to boot from my module-
free kernel I get what looks like the same kernel panic I get when I try
to boot a module-enabled kernel without loading an initrd. So, I
thought I needed an initrd in all cases.

I managed to fake out mkintramfs-kpkg by creating an empty
/lib/modules/<version> directory. That allowed the kernel to install,
but on boot I get a message like "module RAID1 not found" (remember I'm
booting off an md RAID1 device). I verified that I'm statically
compiling in this support, but something is still broken somewhere.

I'll keep trying stuff, and hopefully post back a clean solution.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
First  |  Prev  | 
Pages: 1 2
Prev: 2.6.14-2-386, missing thermal.ko and initrd
Next: Dicota PC-Link Z14438Z