From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] supported ipaq's?
Date: Tue, 25 Jun 2002 10:26:27 +0200 [thread overview]
Message-ID: <52e48b688f49ed8ed3c34b0a60217c7e@plan9.bell-labs.com> (raw)
> i've been trying to get plan9 working on an ipaq (well i spent
> some of last night doing it). i had some successes and some
> failures.
>
> i can't get the latest bootldr to boot 9 from flash. it looks
> to me like the boot formats must have changed. i can boot a
> kernel from ram (using "load ram", "call 0xc....") and it runs
> but the kernel is in an unrecognised format if it tries to
> boot automatically.
One change I discovered is that the Linux boot loader for the bitsy
now recognizes more than one boot format. If you create the
partitions and load a kernel and paqdisk, you should give the
command `boot flash' to boot Plan 9.
You can set the boot parameter to `flash'
set boottype flash
if memory serves me (maybe it's boot_type) and
save params
to make that permanent.
> it looks like the paqdisk that i've generated is broken. the
> ipaq tries to boot off it but can't find /bin/rc. if i
> mount the paqdisk locally (paqfs paqdisk) i get a broken
> process whenever i try to access anything other than the
> root directory).
When the kernel starts up, the first thing it should print is a
fingerprint of the paqdisk. If that succeeds, the paqdisk format
is correct. If /bin/rc still can't be found, check that you've installed
arm binaries before making a paqdisk. `mk paqdisk' will take many files
from /arm but will not install them there if they don't exist.
However, mkfs will complain about missing files.
Let me know how you fare.
Sape
next reply other threads:[~2002-06-25 8:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 8:26 Sape Mullender [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 9:09 Stephen Parker
2002-06-26 9:08 Sape Mullender
2002-06-26 9:03 Sape Mullender
2002-06-26 9:03 Sape Mullender
2002-06-26 7:35 Stephen Parker
2002-06-26 7:29 Fco.J.Ballesteros
2002-06-26 7:28 Stephen Parker
2002-06-25 16:46 Fco.J.Ballesteros
2002-06-25 16:39 Fco.J.Ballesteros
2002-06-25 15:56 rob pike, esq.
2002-06-25 15:56 Stephen Parker
2002-06-25 15:54 Sape Mullender
2002-06-25 15:53 Fco.J.Ballesteros
2002-06-25 16:10 ` Axel Belinfante
2002-06-25 15:51 Stephen Parker
2002-06-25 15:44 Stephen Parker
2002-06-25 8:03 Fco.J.Ballesteros
2002-06-25 7:59 Stephen Parker
2002-06-25 7:45 Fco.J.Ballesteros
2002-06-24 19:00 Sape Mullender
2002-06-24 16:42 presotto
2002-06-24 16:38 Axel Belinfante
2002-06-27 22:55 ` Latchesar Ionkov
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=52e48b688f49ed8ed3c34b0a60217c7e@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).