Booting a 2nd rev 12" powerbook (1Ghz)

[peter at larkowski.net]

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 at freebsd.org>
> To: peter at larkowski.net
> Cc: freebsd-ppc at 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.
>