Deare NetBSD:

This is about a problem I encountered when trying to install
NetBSD-1.4.1/macppc onto a Macintosh G4 400MHz machine.  I didn't succeed
so I couldn't use send-pr from the machine itself.  I've copied this layout
from an Alpha which is running NetBSD/1.4.1.

I realise that this a very new machine so perhaps it isn't correct to class
this as a bug, but it will need to be fixed sometime.

By the way I have been able to net-boot this G4 Macintosh from an Alpha
running NetBSD 1.4.1 (using the 1.4.1 distribution) so quite a lot of the
system works properly.

SEND-PR: -*- send-pr -*-
>Submitter-Id:  net
>Originator:    Ray Phillips
>Organization:  JKMRC
>Confidential:  no
>Synopsis:      sysinst hangs up
>Severity:      critical
>Priority:      medium
>Category:      install
>Class:         sw-bug
>Release:       NetBSD/macppc 1.4.1
>Environment:   Macintosh G4 with an IDE disk, NetBSD/macppc 1.4.1 using
>the netbsd-GENERIC_MD kernel

>Description:

I installed MacOS onto the internal hard disk and put the file
netbsd-GENERIC_MD from the 1.4.1 distribution into its root directory.
Then I rebooted the machine, dropped into the Open Firmware interface and
typed

boot hd:5,netbsd-GENERIC_MD

It booted into NetBSD all right and I chose the install option.

When I said I wanted to install a new system onto a hard disk and chose
'yes' to say that I wanted to create the partitions this message appeared
perhaps half a dozen times

pciide 0:0:0: lost interrupt
type: ata
c_bcount: 512
c_skip:0

followed by

pciide 0:0:0: Bus Master DMA error: missing interrupt, status=0x20
wd0c: DMA error reading fsbn 0 (wd0 bn0; cn 0 tn 0 sn 0), retrying

then more of the first group.

Eventually it dropped back into the normal sysinst interface until I told
it to go ahead and make the partitions with the sizes it suggested.  When I
did that the first message was printed repeatedly with the exception that
512 was changed to 8192, ie.

pciide 0:0:0: lost interrupt
type: ata
c_bcount: 8192
c_skip:0

I also tried just configuring the network from within sysinst but that
wouldn't work either.  Sometimes it said there was no route to host (I
presume that's my local nameserver) and sometimes it froze during the test
phase, just after I'd entered the details.