From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <46f50d92a1d9d7418edd618fe91c560f@csplan9.rit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bitsy boot problems
Date: Fri,  7 Mar 2008 18:31:11 -0500
From: john@csplan9.rit.edu
In-Reply-To: <7fdd354d85c5e3ab085996cf0471cba9@csplan9.rit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 72d233b0-ead3-11e9-9d60-3106f5b1d025

> 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