Problem with busybox when booting file system

[Javier Gracia Castro]

Hi everybody,

I am very new at Linux and embedded systems. I have a problem with the  
shell of busybox. I am working with the board AT91RM9200-EK and a  
2.6.20 Linux kernel.

I used a file system with Busybox 1.4.1 that I didn't build. I had  
some problems with insmod and modprobe when I tried to load the driver  
of a zd1211 device as a module. I obtained this driver after compiling  
the kernel modules (is a .ko file) and I included the folder with the  
modules in the file system. When I used the modules commands of this  
version of Busybox, there were some problems because they searched for  
.o files. Reading several posts in some forums, I discovered that  
these commands have some problems in 2.6 kernels when the option  
CONFIG_FEATURE_2_4_MODULES is enabled.

Then, I downloaded Busybox 1.4.2 and after doing make defconfig, I  
disabled this option and I compiled it with a uClibc toolchain. I  
downloaded all files generated to my file system.

when I try to boot my system after updating Busybox, it doesn't boot  
and I obtain the following message:

RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 100K

But it doesn't do any thing else.

In the arguments for the kernel I specify init=/sbin/init

I think that it is a problem with the shell. Perhaps I don't configure  
correctly shells options because I don't know which options I should  
enable.

Please, any help or suggestion is welcomed,

Javier