From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bootalphapc
Date: Tue, 6 Jul 2004 13:54:21 -0600 [thread overview]
Message-ID: <46dc3dd0e49ca017454e8cddb6385471@plan9.ucalgary.ca> (raw)
In-Reply-To: <20040706T093258Z_FFB700000000@mail2.cu-portland.edu>
> Did you use the out-of-the-box bootalphapc, or some other method to
> get it going? Also, is your filesystem running locally on the PWS, or
> from another machine via network? How much trouble was all this?
>
i boot using bootalphapc from a Plan 9 cpu server on which i've
started ip/tftpd and ip/dhcpd. the ndb configuration for the alpha
(i.e. what the dhcp server will look at) is:
sys=alpha
ether=0000f875fafa
ip=192.168.1.5
bootf=bootalphapc
proto=tcp
fs=136.159.220.110
auth=136.159.220.110
authdom=plan9.ucalgary.ca
ipgw=192.168.1.1
dns=136.159.5.14
dns=136.159.5.15
not all of this is required (it should be in the ipnet= configuration).
bootalphapc looks for a configuration
file describing the machine in /alpha/conf/AA.BB.CC.DD (the ip address
of the machine booting). there's an example there (10.0.0.2), and here's
what i have:
plan9% cd /alpha/conf
plan9% ls
10.0.0.2
192.168.1.5
plan9% cat 192.168.1.5
bootfile=/alpha/9apccpu
bootargs=tcp
ether0=type=2114x
fs=136.159.220.110
auth=136.159.220.110
plan9%
bootalphapc downloads the kernel via tftp and jumps to it.
as for hard -- it wasn't hard at all. the kernel booted to 'root is
from:' immediately, the only thing i needed to do is fix interrupts
(the PCI interrupts seem to be offset by 8). there's still something
wrong with the clock interrupts, of which there are about 500 extra
ones generated every second.
the combined time wasn't more than 4-5 days, of which most was spent
trying different permutations of the IRQ settings and waiting for
others who know to reply to my silly questions.
andrey
ps: http://pages.cpsc.ucalgary.ca/~mirtchov/screenshots/alpha.png
next prev parent reply other threads:[~2004-07-06 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 16:32 Ben Huntsman
2004-07-06 19:54 ` andrey mirtchovski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 5:19 Ben Huntsman
2004-07-02 14:59 ` andrey mirtchovski
2004-07-02 4:57 Ben Huntsman
2004-07-02 5:08 ` andrey mirtchovski
2004-07-02 15:40 ` jmk
2004-07-06 16:13 ` andrey mirtchovski
2004-07-02 4:15 Ben Huntsman
2004-07-02 4:29 ` Geoff Collyer
2004-07-02 4:36 ` George Michaelson
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=46dc3dd0e49ca017454e8cddb6385471@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).