Denis Laxalde wrote:
> Ok. So this test fails and according to the documentation the culprit
> should be a statically compiled driver. I guess I could then try to
> rebuild the kernel with more drivers as modules, but where to start?
Thanks! In modern times, initramfs-tools lets udev load some modules,
such as the disk and network driver, before calling init. So
disabling the tpm module entirely to rule out that cause could be a
comfort. "make localmodconfig" is supposed to create a configuration
with just the currently loaded modules enabled, which could be useful
for coming up with a good starting point.
Another thing to try would be booting into an even more minimal
configuration, without loading any modules or mounting the root
filesystem, by passing the parameter "break=top" on the kernel command
line[1]. It would presumably be necessary to load the appropriate
disk driver ("modprobe ahci") and enable swap ("swapon /dev/sda5") to
get useful results.
[1] see initramfs-tools(8), http://wiki.debian.org/InitramfsDebug
[2]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110825214005.ga18...@elie.gateway.2wire.net
