[9fans] bitsy boot problems

[9fans] bitsy boot problems

[john]

I just found two bitsies yesterday, a 3630 and a 3670. I thought I'd try installing on the 3670 because the other one has a useful Linux install on it already. Anyway, both had Linux bootloaders installed already, so I built a kernel and paqdisk, uploaded them, and tried booting. Here's what I get; can anyone help figure out what's wrong here?


206 MHZ ARM, ver 1/part b11/step 8
64M memory: 27M kernel data, 37M user, 226M swap
root is from (paq)[paq]:
paq...paqfs: sysfatal reading block: /dev/flash/ramdisk:
version...panic: boot process died: sys: write on closed pipe pc=0x00006c74
panic: boktrace /kernel/path c0010d6c c011714c c01171a9
ot procc01170f8=c0010d68 ess diec01170fc=c0071110 d: sys:c0117104=c003afdc  write c0117128=c003b03c on clos
ed pipe c0117140=c003b2a0 pc=0x00c0117144=c0010d68 006c74c0117148=c003b2a4
c0117150=c006ddcc
c01171b0=c008d9d4 c01171b4=c008d780 c01171bc=c008f5c4 c01171c8=c00795a4
c01171d4=c008d510 c01171d8=c008e740 c01171dc=c008d8d4 c01171e0=c008d510
c01171e8=c008d7bc c01171f4=c008d780 c01171fc=c008f5c4 c0117208=c00795a4
c011721c=c008fa84 c011723c=c00601f8 c0117248=c006b3e0 c0117250=c006b3e8
c011725c=c006dd8c c0117274=c001093c c0117280=c00796c8 c0117284=c0079ba4
c01172ac=c00715e4 c01172b4=c0010920 c01172c8=c001045c c01172e8=c0008248
c01172f0=c0079ba4
it's a wonderful day to die

Re: [9fans] bitsy boot problems

[ron minnich]

So FWIW I just told john two things (we work in the unix room here at
sandia labs ... we even have a pjw poster). I just get in later
because he is the industrious intern and I am the grizzled old guy.

First: the boot process is dying. One easy thing to do is set up so
that when you boot it drops you into an rc running out of ramdisk, and
just poke around, see if you can do things to the disk, run paqfs (can
even do it under acid, probably) and so on. You can learn a lot.

Second, the usual, debug prints in paqfs ...

ron

Re: [9fans] bitsy boot problems

[john]

> For some reason, after recompiling stuff (some things hadn't compiled
> properly at first) and rebuilding the paqdisk (it's now about 6.5MB),
> when I do "load ramdisk" xms completes but the ramdisk never gets
> written to the flash.  This is all I see:
> xms: 6628492 bytes transmitted
> !
>
> It looks like the ramdisk partition's size is only 0x600000, whatever
> unit that is.  If that's in bytes, the newly created paqdisk is too
> large which could explain the problem.
>
> John

Forgot that the partition sizes are used by the kernel; I dropped acme,
ssh, and winwatch to get the paqdisk under the ramdisk partition
size. Now I get as far as root is from: [paq]:  paqfs...
then sit there forever. Are there any bitsy users out there who have
recently recompiled and reinstalled their bitsy stuff? Anybody got
a kernel & paqdisk that is known to work?


John