From owner-freebsd-bugs@FreeBSD.ORG Thu Oct 21 20:21:34 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB98716A4CE; Thu, 21 Oct 2004 20:21:34 +0000 (GMT) Received: from virtualhost.dk (ns.virtualhost.dk [195.184.98.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1617A43D46; Thu, 21 Oct 2004 20:21:34 +0000 (GMT) (envelope-from axboe@zx2000.home.kernel.dk) Received: from [62.242.22.158] (helo=zx2000.home.kernel.dk) by virtualhost.dk with esmtp (Exim 3.36 #1) id 1CKjRI-0004oC-00; Thu, 21 Oct 2004 22:21:36 +0200 Received: by zx2000.home.kernel.dk (Postfix, from userid 1000) id 50AC22BB2E; Thu, 21 Oct 2004 22:21:06 +0200 (CEST) Date: Thu, 21 Oct 2004 22:21:06 +0200 From: Jens Axboe To: Arun Sharma Message-ID: <20041021202105.GI32465@suse.de> References: <200410080602.i9862nYp081905@freefall.freebsd.org> <41670570.2080109@intel.com> <41673488.6000209@intel.com> <20041009180225.GE13195@suse.de> <20041018113430.GK2349@suse.de> <41741B58.6080104@intel.com> <20041020082952.GA10531@suse.de> <417803D4.4010601@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417803D4.4010601@intel.com> cc: freebsd-bugs@freebsd.org cc: freebsd-gnats-submit@freebsd.org cc: Mark Linimon Subject: Re: ia64/72128: 5.3-beta6 doesn't boot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 20:21:34 -0000 On Thu, Oct 21 2004, Arun Sharma wrote: > Jens Axboe wrote: > >Hi, > > > >Here's the memmap on my box: > > > >Shell> memmap > > Looks pretty similar to my 4GB box. It looks like your serial console is > working fine for EFI. Could you please check the settings for the kernel > in the boot loader ? > > I use something like: > > hw.uart.console="io:0x2f8,br:57600" > > Your baud rate might be different. But you certainly need to change the > io to 0x2f8 (COM2) from the default of 0x3f8 (COM1) on the Tiger. That might just be it, I actually suspected this earlier today. But I thought the serial port on the tiger _was_ on 0x3f8. I'll give it a shot tomorrow, thanks. -- Jens Axboe