From owner-freebsd-sparc64@FreeBSD.ORG Thu Sep 16 13:59:41 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 462B816A4CE for ; Thu, 16 Sep 2004 13:59:41 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E263643D1D for ; Thu, 16 Sep 2004 13:59:40 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i8GDxdTH019776; Thu, 16 Sep 2004 09:59:39 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i8GDxcAS019775; Thu, 16 Sep 2004 09:59:38 -0400 (EDT) Date: Thu, 16 Sep 2004 09:59:38 -0400 From: Ken Smith To: kinux Message-ID: <20040916135938.GG17484@electra.cse.Buffalo.EDU> References: <00ce01c49bc4$ab07b1c0$4c22fea9@winxp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ce01c49bc4$ab07b1c0$4c22fea9@winxp> User-Agent: Mutt/1.4.1i cc: freebsd-sparc64@freebsd.org Subject: Re: Fail to install 5.3 on Netra t1 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 13:59:41 -0000 On Thu, Sep 16, 2004 at 04:10:45PM +0800, kinux wrote: > Executing last command: boot cdrom > Boot device: /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f File and args: > kernel/unix > > >> FreeBSD/sparc64 boot block > Boot path: /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2,0:f > Boot loader: kernel/unix > File kernel/unix not found > Program terminated > ok BTW, it is most likely the "File and args: kernel/unix" thing that is causing your specific problem and that's probably a setting in your EEPROM. If you have the same problem booting miniinst as you had booting the bootonly CD then try: boot cdrom /boot/kernel/kernel to see if that helps. If it does you should probably change your EEPROM settings. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |