From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] bitsy anyone?
Date: Tue, 21 Oct 2008 14:10:25 -0700 [thread overview]
Message-ID: <621112A569DAE948AD25CCDCF1C075331AB3B1@dolly.ntdom.cupdx> (raw)
In-Reply-To: <a2d238df0810211409ndd63610w6959894f2786e20@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
>"add ramdisk 0x0200000 0x0800000",
I believe the command in question is:
partition define ramdisk 0x200000 0x600000 0
I had changed it to 0x800000 too, but still got the kernel panic...
I'll take a look in paq.c and see if I can fix the hard-coded sizes.
Thanks!!
-Ben
-----Original Message-----
From: 9fans-bounces@9fans.net on behalf of Eoghan Sherry
Sent: Tue 10/21/2008 2:09 PM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] bitsy anyone?
> However, I had some problems when uploading the paqdisk
> on the iPaq when the image file is larger than 4 MB. The image
> seems to be corrupted during the upload on the iPaq and Plan 9
> crash during boot. This problem does not appear with a smaller paqdisk.
I don't have a Plan 9 system or a bitsy at hand but I remember
running into this. The hard coded partition definition is fparts in
/sys/src/9/boot/paq.c. The ramdisk partition is defined to be 4 MB although the
various documents imply it should be 6 MB.
I recall simply changing the ramdisk entry to,
"add ramdisk 0x0200000 0x0800000",
allowed me to use larger images.
Hope this helps,
eoghan
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3250 bytes --]
next prev parent reply other threads:[~2008-10-21 21:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 9:27 [9fans] Are there any blind users of Plan 9? Chris Brannon
2008-10-20 9:55 ` Rudolf Sykora
2008-10-20 9:56 ` Gorka Guardiola
2008-10-20 10:15 ` Jeff R. Allen
2008-10-20 10:29 ` Rudolf Sykora
2008-10-20 10:34 ` Pietro Gagliardi
2008-10-20 14:12 ` john
2008-10-20 21:00 ` Federico G. Benavento
2008-10-20 21:15 ` Pietro Gagliardi
2008-10-21 5:00 ` Lyndon Nerenberg
2008-10-21 5:20 ` Uriel
2008-10-21 10:37 ` [9fans] How to go about doing screen reading Pietro Gagliardi
2008-10-21 15:52 ` Chris Brannon
2008-10-21 17:21 ` [9fans] bitsy anyone? Benjamin Huntsman
2008-10-21 17:29 ` Francisco J Ballesteros
2008-10-21 18:17 ` David du Colombier
2008-10-21 21:09 ` Eoghan Sherry
2008-10-21 21:10 ` Benjamin Huntsman [this message]
2008-10-21 21:49 ` Eoghan Sherry
2008-10-23 9:29 ` [9fans] Are there any blind users of Plan 9? matt
2008-10-20 15:10 ` Dave Eckhardt
2008-10-20 16:06 ` Chris Brannon
2008-10-20 19:15 ` Noah Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=621112A569DAE948AD25CCDCF1C075331AB3B1@dolly.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).