Jivko Sabev wrote:
> Having
>
> CONFIG_CRAMFS=y
>
> does not change anything. Exactly the same problem as before. Namely boot
> process hangs after finding the compressed ram image. There are no errors
> reported.
The reason why loop-AES README says CONFIG_CRAMFS=n is because long time ago
someone had problems with it when cramfs tried to "probe" if root file
system type was cramfs. While doing that, cramfs also damaged the initrd
data sufficiently badly that minix file system could not mount it any more.
The workaround was to disable cramfs, or to specify rootfstype=minix kernel
parameter. That rootfstype=minix kernel parameter disables attempts to mount
using all built-in file systems, so cramfs no longer got a chance to
probe/damage the initrd data.
You provided some data about your setup, but something is still missing.
Your bootloader configuration, and specifically what parameters get passed
to kernel when it boots is important. Please provide that info.
Can you also modify your build-initrd.sh config so that
TOOLSPROMPT=1
is set there? Then build new initrd. It doesn't do much other than ask you
to press ENTER key when initrd code begins to run. At least you get to know
if it got that far.
Also, can you verify that dietlibc is working ok? Like this:
$ printf '#include <unistd.h>\nint main(){write(1,"hello\\n",6);}\n' >xxx.c
$ diet gcc -O2 -s xxx.c
$ ./a.out
hello
$
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
