From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 23 Feb 2006 03:19:33 -0600 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" Message-ID: <20060223091933.GA429@slash.bytex64.net> References: <20060223073007.GA32767@slash.bytex64.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Topicbox-Message-UUID: 04d44170-ead1-11e9-9d60-3106f5b1d025 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.