From: cblack1@uiuc.edu
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Alpha bootloader "kernel stack not valid"
Date: Thu, 23 Feb 2006 03:19:33 -0600 [thread overview]
Message-ID: <20060223091933.GA429@slash.bytex64.net> (raw)
In-Reply-To: <c57a535f07a00357bfb41770d50cba1b@collyer.net>
On Thu, Feb 23, 2006 at 12:15:50AM -0800, geoff@collyer.net wrote:
> I'd start by replacing the 82559 with a 2114x. Mine is a DE-500 but
> you might be able to find Netgear FA310s (not 311s), which should work
> too.
Alright, I'll see if I can scrounge one of those.
> What's in your /alpha/conf file?
bootfile=/alpha/9apc
bootargs=tcp
ether0=type=8255x
fs=10.0.0.12
> What's your /lib/ndb entry for the alpha?
There are actually two machines doing this, neither of them plan9 (the
"other computer" that compiled the binaries was actually running in
qemu). My router serves the bootp request, and another linux machine
does tftp. I've looked at packet dumps of the bootp/tftp traffic, and
I'm pretty sure it's all working as it should.
> It might be revealing to install and boot a BSD or Linux and see if it
> runs correctly.
Well, I can boot the debian install image just fine, including bringing
up the network interface and pulling down things via HTTP. I am getting
a bunch of machine checks for ECC errors that I hadn't noticed before.
I'll put in a hard drive and see if I can get a working system out of
it.
next prev parent reply other threads:[~2006-02-23 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 4:55 cblack1
2006-02-23 6:57 ` geoff
2006-02-23 7:30 ` cblack1
2006-02-23 8:15 ` geoff
2006-02-23 9:19 ` cblack1 [this message]
2006-02-23 9:40 ` geoff
2006-02-23 9:48 ` cblack1
2006-02-23 16:25 ` LiteStar numnums
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=20060223091933.GA429@slash.bytex64.net \
--to=cblack1@uiuc.edu \
--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).