From owner-freebsd-ppc@FreeBSD.ORG  Sun Feb  1 05:50:38 2004
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
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 09D6D16A4CE; Sun,  1 Feb 2004 05:50:38 -0800 (PST)
Received: from decstation.larkowski.net (d60-65-37-214.col.wideopenwest.com
	[65.60.214.37])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 87AB643D5C; Sun,  1 Feb 2004 05:50:33 -0800 (PST)
	(envelope-from peter@larkowski.net)
Received: from localhost (peter@localhost)i11Dobc04122;
	Sun, 1 Feb 2004 08:50:38 -0500 (EST)
Date: Sun, 1 Feb 2004 08:50:33 -0500 (EST)
From: peter@larkowski.net
To: Peter Grehan <grehan@freebsd.org>
In-Reply-To: <401CCC07.4080803@freebsd.org>
Message-ID: <Pine.NEB.4.44.0402010848170.4109-100000@decstation.larkowski.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2004 13:50:38 -0000

Peter:

Ok, there is not in fact a "interrupt-controller" node.  Where do we go
from here?  Is there any other useful info I can provide?  Let me know.

-p


On Sun, 1 Feb 2004, Peter Grehan wrote:

> Date: Sun, 01 Feb 2004 19:51:03 +1000
> From: Peter Grehan <grehan@freebsd.org>
> To: peter@larkowski.net
> Cc: freebsd-ppc@freebsd.org
> Subject: Re: Booting a 2nd rev 12" powerbook (1Ghz)
>
> Hi Peter,
>
> > pci1: <network> 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.
>