Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
20 years ago

busybox version 5.1 won't run

I built the busybox in the Nios II Version 5.1 for Windows distribution, as described in the Nios II Linux Reference Guide document. I add it to the filesystem I load into the FLASH as new-busybox, so that I could run it from the command line. When I run it, I get this printout. I have tried configuring the General Configuration - Buffer Allocation policy all three ways, as that looked like the most likely problem I could control. But I get the same messages from the kernel every time.

Any ideas or suggestions?

# new-busybox

Allocation of length 1250046 from process 34 failed

DMA per-cpu:

cpu 0 hot: low 2, high 6, batch 1

cpu 0 cold: low 0, high 2, batch 1

Normal per-cpu: empty

HighMem per-cpu: empty

Free pages: 10504kB (0kB HighMem)

Active:314 inactive:145 dirty:0 writeback:0 unstable:0 free:2626 slab:584 mappe0

DMA free:10504kB min:512kB low:640kB high:768kB active:1256kB inactive:580kB pro

lowmem_reserve[]: 0 0 0

Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pao

lowmem_reserve[]: 0 0 0

HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB presento

lowmem_reserve[]: 0 0 0

DMA: 0*4kB 1*8kB 0*16kB 0*32kB 2*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 1*2048kBB

Normal: empty

HighMem: empty

Unable to allocate RAM for process text/data, errno 12

new-busybox: memory exhausted#

1 Reply

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    20 years ago

    Well, I have made some progress. I downloaded the source code for version 1.01 from busybox.net and after massaging the Makefile and Rules.mak to correclty find the include and library files, I got it to build. I put it into my romfs and it basically runs. It does not run when linked as init at boot time, but I can run it as the target of the links for many apps. I am still running the distributed busybox version:

    init started: BusyBox v1.00-pre8 (2005.06.20-12:07+0000) multi-call binary

    at init time, as init.exe gives a init: exec failed message after loading the ram filesystems. At least I can control the applications I support now.

    Any ideas why the version 1.01 will not run as init?