Just a wild guess: has it anything to do with an initrd option? This is the system I mostly use: add the new busybox as something like busybox.new and test the applets you added with the old system. If everything seems to work, rename busybox to busybox.old and rename busybox.new to busybox. Most of all, I prefer to do the tests on an NFS mounted system since it's much easier to replace a part.
kind regards, wim vinckier. On 4/11/07, Javier Gracia Castro <[EMAIL PROTECTED]> wrote: > Hello again, > > My situation is: I want to add a wireless USB device (based on zd1211) > to my board AT91RM9200-EK with a 2.6.20 Linux kernel. I downloaded a > file system image with uClibc and busybox. I compiled the driver of > this device as modules of the kernel and I dowloaded them to the > board. When I try to load this driver module (.ko file) with the > modprobe command it tries to search for a .o file. I read comments > about this problem from posts of this mail list. This problem is > because of in configuration file of busybox, > CONFIG_FEATURE_2_4_MODULES should be disabled. > > Then, I download a newer version of Busybox 1.4.2 and disabled this > option after make menuconfig. I compiled it with a uClibc toolchain > and I updated my file system. > > When I try to boot the file system with init=/sbin/init I only obtain: > > RAMDISK: Compressed image found at block 0 > VFS: Mounted root (ext2 filesystem). > Freeing init memory: 100K > > and nothing else (no kernel panic) > > If I set init=/sbin/sh or /sbin/bash (sh and bash are from the > original file system, they don't belong to buxybox), I obtain a prompt > but with execution of most busybox commands I obtain: > > Illegal instruction > > The privileges of my busybox executable are: > > -rwsr-xr-x 1 root root 725088 2007-04-11 10:52 busybox > > I don't know what to do, because I wanted to solve a problem and now I > have another bigger problem. > > Thanks in advance, > > Javier > > > Quoting Larry Brigman <[EMAIL PROTECTED]>: > > > On 4/10/07, Javier Gracia Castro <[EMAIL PROTECTED]> wrote: > >> 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 > >> > > > > Suggestions: > > use init=/bin/sh because if init dies you get a kernel panic. > > Use buildroot. > > > > One place of reference (not just busybox but embedded development in > > general) > > http://lldn.timesys.com/webinars > > I don't use their products but I have use there articles and webinars > > as practical resources. > > > > _______________________________________________ > busybox mailing list > [email protected] > http://busybox.net/cgi-bin/mailman/listinfo/busybox > -- You have been on the computer to long when you start tilting your head sideways to smile :-) _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
