From owner-freebsd-sparc64@FreeBSD.ORG Sun May 15 17:33:14 2005 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 EC0FC16A4CE for ; Sun, 15 May 2005 17:33:14 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27F5443D7E for ; Sun, 15 May 2005 17:33:14 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) j4FHXBQ8015991; Sun, 15 May 2005 19:33:12 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id j4FHX61A015990; Sun, 15 May 2005 19:33:06 +0200 (CEST) (envelope-from marius) Date: Sun, 15 May 2005 19:33:06 +0200 From: Marius Strobl To: Sean Hafeez Message-ID: <20050515193306.B15193@newtrinity.zeist.de> References: <69889da30505141501c9edc55@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <69889da30505141501c9edc55@mail.gmail.com>; from sah.list@gmail.com on Sat, May 14, 2005 at 03:01:02PM -0700 X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-4; AVE: 6.30.0.12; VDF: 6.30.0.177; host: newtrinity.zeist.de) cc: freebsd-sparc64@freebsd.org Subject: Re: jumping to kernel entry - 5.4 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: Sun, 15 May 2005 17:33:15 -0000 On Sat, May 14, 2005 at 03:01:02PM -0700, Sean Hafeez wrote: > Thought I would try 5.4 on my Ultra60 with 2x350Mhz CPUs. Booting from > the CD I get to.. > > jumping to kernel entry at 0xc0040000 > > and the system hangs there. Did a seach and the only thing I could > find was some other people asking about it at: > > http://lists.freebsd.org/pipermail/freebsd-sparc64/2005-April/003028.html > > So anyone got a fix? Anything info I need to post? > You're most likely not using a serial console. FreeBSD/sparc64 up to including 5.4 only really supports serial consoles. Prior to 5.4 however the FreeBSD/sparc64 GENERIC kernels came with ofw_console(4) enabled which happens to work with graphical consoles to a certain extent. In the FreeBSD/sparc64 5.4 GENERIC kernel that bit of support for graphical consoles was traded for proper serial console support (which also just sucked when driven by ofw_console(4) on a machine that uses a chip not supported by sab(4) or zs(4)) by switching from the ofw_console(4)/sab(4)/zs(4) combination to uart(4). If you want to use FreeBSD/sparc64 5.4 with a graphical console anyway you have to compile a custom kernel. On a machine with a Creator, Creator3D or Elite3D card and a RS232 keyboard you should use the creator(4)/syscons(4)/uart(4). Otherwise your only choice is to revert to ofw_console(4). Note that uart(4) can't be used together with ofw_console(4) in the same kernel as ofw_console(4) isn't a proper driver causing both to conflict at several levels. There's no simple "fix" to this other than to complete the native support for graphical consoles in FreeBSD/sparc64. As it currently stands FreeBSD 6.0 and 5.5 most likely will support graphical consoles on most of the sparc64 machines FreeBSD currently runs on in the GENERIC kernel (read: expect SBus- based and non-Mach64 PCI graphics cards and PS/2 keyboards). Marius