From owner-freebsd-ppc@FreeBSD.ORG Sun Feb 1 01:49:10 2004 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A317916A4CE for ; Sun, 1 Feb 2004 01:49:10 -0800 (PST) Received: from liberty.onthenet.com.au (liberty.OntheNet.com.au [203.22.124.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31DFF43D1F for ; Sun, 1 Feb 2004 01:49:09 -0800 (PST) (envelope-from grehan@freebsd.org) Received: from freebsd.org (CPE-30-4.dsl.onthenet.net [203.144.30.4]) i119n5ZG052823; Sun, 1 Feb 2004 19:49:07 +1000 (EST) (envelope-from grehan@freebsd.org) Message-ID: <401CCC07.4080803@freebsd.org> Date: Sun, 01 Feb 2004 19:51:03 +1000 From: Peter Grehan User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: peter@larkowski.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-ppc@freebsd.org Subject: Re: Booting a 2nd rev 12" powerbook (1Ghz) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 09:49:10 -0000 Hi Peter, > pci1: at device 18.0 (no driver attached) This is the first problem: the GEM driver needs to be updated with new PCI IDs. That's an easy fix, and I'll get that done pronto. > panic: nexus_alloc_resource: no pic attached This has also been seen on the 17" P'Book. The algorithm used to locate the interrupt controller in the OpenFirmware device tree isn't working on these models. At the OpenFirmware prompt, would you be able to do 0 > dev /chosen 0 > .properties (don't forget the '.' !) ... and there should be a node called "interrupt-controller". If not, the probe won't work, and that's where the panic is coming from. > At this point, if I am in syscons, I have no keyboard any longer, so I > hold the power button and return to OSX, but if I disable syscons, I can > poke around in the debugger on either keyboard (usb or builtin) Any > thoughts? That's because USB hasn't been probed yet so the syscons/USB kbd won't work. With syscons disabled, the console is the polled-mode OpenFirmware console, so both the USB and internal kbd's will work. later, Peter.