Subject: RE: Installing NetBSD onto a Motorola PowerStack Series E
To: 'Jochen Kunz' <>
From: Chesterton Andrew-BLUW13 <>
List: port-prep
Date: 07/30/2003 14:30:32
Hi Jochen,
	Thanks for all your help.
I am quite prepared to loan my machine to somebody to help in getting =
it running, if that is what is needed.=20
I am based in Leicestershire in the UK.

Hopefully somebody out there has "The Clue" that is needed to help.

Thanks Again,

-----Original Message-----
From: Jochen Kunz []=20
Sent: 29 July 2003 19:00
To: Chesterton Andrew-BLUW13
Subject: Re: Installing NetBSD onto a Motorola PowerStack Series E

On 2003.07.29 18:36 Chesterton Andrew-BLUW13 wrote:

> I have created the Com port boot disk and this is the captured output =

> when the system boots:
[...]  =20
> cpu0 at mainbus0: 604 (Revision 3.3), ID 0 (primary)                  =

[...]                     =20
> pchb0: vendor 0x1057 product 0x0001 (rev. 0x24)
product MOT MPC105      0x0001  MPC105 \"Eagle\" Host Bridge

> pcib0: vendor 0x8086 product 0x0484 (rev. 0x43)
product INTEL SIO               0x0484  82378ZB System I/O (SIO)

There is already support for the CPU, host- and ISA-bridge in port =
prep. All we need is some glue code to make this machine knowen to =

> siop0 at pci0 dev 12 function 0: Symbios Logic 53c825 (fast wide =
> pci_intr_map: no mapping for pin A
> siop0: couldn't map interrupt
OK. Interrupt routing trouble. Depending on the hardware there may be a =
chance to get this solved quite quick.=20

I have done some work in that area of port-prep / port-ofppc, so I know =
a bit what is going on. But I am no kernel hacking expert, I am still a =
novice. (I still need to understand that interrupt handling stuff.) If =
someone with "The Clue" can get access to this machine in an =
developement environement it would be a matter of a few houres to get =
NetBSD running. At the moment I can't help you further. Sorry. Maybe a =
NetBSD kernel hacking guru is willing to volunteer and you can setup =
some remote console access for him?=20

> root on md0a dumps on md0b
> trap: kernel ISI by 0xbf8002e0 (SRR1 0x40009032)
> panic: trap
Hmm. Don't know how to trace this.=20