[BusyBox] boot problem
Magnus Damm
damm at opensource.se
Thu Dec 5 10:44:02 UTC 2002
Hi again,
I don't know much about the arm toolchain, sorry.
Just make sure that you always use the correct cross-tools,
ie use arm-linux-objdump or whatever you prefix is...
And then you have cpu-flags and stuff like that.
I would get a precompiled static "known good" binary and
see if that works.
/ magnus
Igor Trevisan wrote:
>
> Sorry for the details missing but...
> I will remedy!
> First: busybox is compiled static.
> Then, this is file command output with busybox:
> busybox: ELF 32-bit LSB executable, no machine, version 1 (SYSV),
> statically linked, stripped
> With objdump I find:
> busybox: file format elf32-little
> busybox
> architecture: UNKNOWN!, flags 0x00000102:
> EXEC_P, D_PAGED
> start address 0x00008090
>
> Program Header:
> LOAD off 0x00000000 vaddr 0x00008000 paddr 0x00008000 align
> 2**0
> filesz 0x00056ab6 memsz 0x00056ab6 flags r-x
> LOAD off 0x00056ab6 vaddr 0x00066ab8 paddr 0x00066ab8 align
> 2**0
> filesz 0x00000f88 memsz 0x00008aec flags rw-
>
> Sections:
> Idx Name Size VMA LMA File off Algn
> 0 .init 00000010 00008074 00008074 00000074 2**2
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 1 .text 0004e16c 00008090 00008090 00000090 2**4
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 2 .fini 0000000c 000561fc 000561fc 0004e1fc 2**2
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 3 .rodata 000088ae 00056208 00056208 0004e208 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 4 .data 00000d30 00066ab8 00066ab8 00056ab6 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 5 .eh_frame 00000004 000677e8 000677e8 000577e6 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 6 .ctors 00000008 000677ec 000677ec 000577ea 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 7 .dtors 00000008 000677f4 000677f4 000577f2 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 8 .jcr 00000004 000677fc 000677fc 000577fa 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 9 .got 00000240 00067800 00067800 000577fe 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 10 .sbss 00000000 00067a40 00067a40 00057a3e 2**0
> CONTENTS
> 11 .bss 00007b64 00067a40 00067a40 00057a3e 2**5
> ALLOC
> objdump: busybox: no symbols
>
> And finally...
> I have both /bin/sh and /sbin/init in my filesystem.
>
> I hope this can help you to help me!
> Could it be the "no machine" and "architecture: UNKNOWN!"
> the reasons for the boot error?
> Something wrong in building busybox?
> And if it's so...
> How to remedy?
> Thanks again in advance...
> Igor.
>
> On 5 Dec 2002 at 18:16, Magnus Damm wrote:
>
> >
> > Do you have the required libraries on the target filesystem?
> > Or is busybox compiled static?
> >
> > Use "file" to see if a binary is linked static or not..
> > And use objdump -x | grep NEEDED to look for required libraries.
> >
> > Do you have /sbin/init or /bin/sh on your target filesystem?
> >
> > Good luck!
> >
> > / magnus
> >
> > >I am trying to boot Linux 2.4.19-rmk4 with busybox-0.60.5 complied
> > >against uClibc (last stable version at today) on a ccdb89712 Cirrus
> > >Logic arm machine.
> > >
> > >This is what I get:
> > >
> > >VFS: Mounted root (nfs filesystem).
> > >
> > >Freeing init memory: 52k
> > >
> > >Kernel panic: No init found. Try passing init= option to kernel.
> > >
> > >Can someone tell me what's the reason for this and how can I
> > >solve it?
> > >Thanks...
> > > Igor.
> > >---------------------------------------------------------------------
> > >------ --- No electrons were killed to produce this document! ---
> > >---------------------------------------------------------------------
> > >------ _______________________________________________ busybox
> > >mailing list busybox at busybox.net
> > >http://busybox.net/mailman/listinfo/busybox
>
> \ | | | | | | /
> | |
> | O O |
> ________oOOOo____0____oOOOo_________________
> This mail was made with 100% recycled electrons!
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
More information about the busybox
mailing list