Re: [Fwd: Problem with Install Kernel for Kurobox Pro]

[Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost>]

>The normal kernel seems to work fine (but it doesn't use a memory 
>disk).  Incidentally, I'm building on a windows XP machine using 
>Cygwin.  The build commands are:
>$ ./build.sh -O ../obj -T ../tools -m evbarm-el tools
>$ ./build.sh -O ../obj -T ../tools -U -u -m evbarm-el distribution
>$ ./build.sh -O ../obj -T ../tools -U -u -m evbarm-el -V 
>KERNEL_SETS=KUROBOX_PRO release

So at a first glance I would say that the problem is with the process that
builds the ramdisk image, since from the errors you post it looks like
you have a corrupted ramdisk image.

It might be useful to go to src/distrib/evbarm/instkernel and run
nbmake-evbarm (from tools/bin) and watch very carefully the process
where the ramdisk is created; the key tool is makefs (nbmakefs in
tools/bin).  I would guess that there is a problem with this tool under
Cygwin.  You could set some bits in the debug mask and run it by hand
to perhaps glean some insight.  At the very worst, you might have to
hunker down with the makefs sources and figure out what's wrong, if
you really want to solve it.

You could always take the ramdisk.fs image from the Linux system
and use it on the Cygwin system; the only problem is that from what
I see the ramdisk filesystem is always rebuilt by default.  It looks
like there is some logic in the Makefile to prevent that, but I'm
not sure if it's disabled or simply not working; you might have to
do some hacking around to get it to always use your prebuilt ramdisk
image.

--Ken