From owner-freebsd-questions@FreeBSD.ORG Thu Dec 1 14:20:34 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF93516A420 for ; Thu, 1 Dec 2005 14:20:34 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id E605043D7F for ; Thu, 1 Dec 2005 14:20:24 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 28711 invoked from network); 2 Dec 2005 01:20:23 +1100 Received: from 203-214-159-121.perm.iinet.net.au (HELO ?192.168.13.3?) (203.214.159.121) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Dec 2005 01:20:23 +1100 Message-ID: <438F069E.1030105@meijome.net> Date: Fri, 02 Dec 2005 01:20:14 +1100 From: Norberto Meijome User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Gestur A. Grjetarsson" References: <636A75F5E9CA8741A3136582949F95876E925E@postur.ecweb.local> In-Reply-To: <636A75F5E9CA8741A3136582949F95876E925E@postur.ecweb.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: problem booting FreeBSD 6.0 on IBM Blade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 14:20:34 -0000 Gestur A. Grjetarsson wrote: > Hi > > I'm having a problem installing freebsd on an ibm blade > the problem I face is that during boot, it always stops in OK prompt with the message "can't load 'kernel'" [...] > > can anyone point me out... it seems that when I try type in > load /boot/kernel/kernel > > I get ? instead of / > Hi there - I don't think I know the answer , but I've managed to figure things out in the past by issuing 'lsdev' (no quotes) from that point and see what it says/ what devices it can see. Then you can usually change where it tries to find the kernel (passing the right path from the hardware/BIOs point of view). (and again, maybe not ;) ) hope it helps. Beto