> So you should really put device-mapper into the boot runlevel. And btw, why > do > compile things as modules which you need in any case? Doesn't make sense to > me. >
I put device-mapper into the boot runlevel. I re-compiled the kernel with dm-mod=<*>, dm_crypt=<*>, mmc_block=<*> and rebooted. No change. Near the start of boot messages this appears: *Setting up the Logical Volume Manager Locking type 1 initilisation failed. There follows a couple of screenfuls of self-abuse then *ERROR: lvm failed to start. Followed by fsck.ext2 complaining it can't read the volumes, naturally, since they're are'nt mounted. a screenful or two of this then * Some local filesystems failed to mount La di da Then *Configuring kernel parameters... Finally the volumes are found and mounted and the login appears. All seems normal except that under /etc/init.d depscan.sh and runscript.sh are flashing white on red indicating that they now point to nothing. And whatever else I haven't spotted yet. mw
