On Wednesday 11 April 2007 10:54, Javier Gracia Castro 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
You probably built busybox with wrong CPU instruction set. It's like trying to run i686 binaries on Pentium Classic. -- vda _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
