headers
Donald T Hayford | 6 Dec 2008 15:44

[Fwd: Problem with Install Kernel for Kurobox Pro]

I originally sent this to port-arm, but thought this might be a better 
location.  I've built the install kernel for the KUROBOX_PRO (which is 
currently not supported, but is being worked on by several of the 
port-arm folk) using the same steps on a Linux box and it boots without 
a problem.  Unfortunately, I need to use Cygwin in general.  I tried 
several different sets of Mr Kiyohara's diff and tar files for the 
KUROBOX_PRO with the same results.  With Cygwin, the normal kernel boots 
and runs ok.  The installation kernels all fail as below.  Using Linux, 
both kernels boot and run correctly.  I use the same steps to build for 
both Cygwin and Linux.

Is there maybe some environment variable I should be setting?  Nothing 
popped out at me.

Any help is greatly appreciated.

Don Hayford

-------- Original Message --------
Subject: 	Problem with Install Kernel for Kurobox Pro
Date: 	Sun, 30 Nov 2008 09:05:55 -0500
From: 	Donald T Hayford <don <at> donhayford.com>
To: 	port-arm <at> netbsd.org

I'm trying to build an installation version of the Kurobox Pro kernel 
and I'm getting a kernel panic when it boots up with a message about a 
bad directory entry. 

First bad, reclen=0x10, DIRSIZ=16, namlen=4, flags=0x5001, 
entryoffsetinblock=50
(Continue reading)

Permalink | Reply | 5 comments |
headers
Ken Hornstein | 7 Dec 2008 03:55
X-Face
Picon
Picon
Favicon

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

>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
(Continue reading)

Permalink | Reply | 4 comments |
headers
Donald T Hayford | 7 Dec 2008 14:39

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

Ken Hornstein wrote:
> 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
>   
Thanks for the reply.  Your suggestions are good ones and I'll give them 
a shot.  I guess I get to learn a lot more about building NetBSD than I 
originally anticipated. :-)

The fact that there is a problem like this surprises me a little, since 
Cygwin has been around a long time and is relatively mature.  Of course,
(Continue reading)

Permalink | Reply | 0 comments |

Gmane