Re: Issues with NetBSD 8.1 macppc

Joerg Sonnenberger <[email protected]>
Newsgroups gmane.os.netbsd.ports.macppc
Message-ID <[email protected]>
On Wed, Oct 30, 2019 at 05:40:52PM +0000, Mark Cave-Ayland wrote:
> On 30/10/2019 14:07, Joerg Sonnenberger wrote:
> 
> > On Tue, Oct 08, 2019 at 05:03:30AM +0100, Mark Cave-Ayland wrote:
> >> 2) Can you see any error messages booting with -nographic (this redirects the screen
> >> device to a serial TTY which is output to the console)?
> > 
> > Hello Mark,
> > I run into the same issues while trying to get the automated testing with
> > Anita to work. After some suggestions from Michael, I tracked it down to 
> >   https://anonhg.netbsd.org/src/file/ccc87740ba45/sys/arch/powerpc/oea/ofw_autoconf.c#l140
> > 
> > Commenting out that OF_finddevice call fixes the boot. While booting
> > from CD-ROM, it tries to lookup:
> >   /pci@f2000000/mac-io@c/ata-3@21000/cdrom@0:0/netbsd
> > in qemu 4.1.0. Any further ideas on how to trace this down?
> 
> Hi Joerg,
> 
> So just to confirm that this is cause of the XXXX error message that you see? If I
> load qemu-system-ppc and try and list the contents of the various partitions on the
> NetBSD 8.1 CDROM then I see this:

0 > dir /pci@f2000000/mac-io@c/ata-3@21000/cdrom@0:0,\ mac-parts mac-parts: Unable to determine filesystem
 ok
0 > dir /pci@f2000000/mac-io@c/ata-3@21000/cdrom@0:1,\ mac-parts: Unable to determine filesystem
 ok
0 > dir /pci@f2000000/mac-io@c/ata-3@21000/cdrom@0:2,\ 
     16384 2019-10-30 11:49:38 Desktop DB
         0 2019-10-30 11:49:38 Desktop DF
    131072 2019-10-30 11:49:38 macppc\
   5477006 2019-10-30 11:49:01 netbsd
     81486 2019-10-30 11:49:01 ofwboot.xcf
 ok

and after "boot cd:,ofwboot.xcf:

...
[   1.0000000] bootpath: /pci@f2000000/mac-io@c/ata-3@21000/cdrom@0:0/netbsd

with a kernel that has the block in line 140 above commented out.

The ISO has been created with:
  mkisofs -r -o boot.iso -hfs -part -l -J -N -m netbsd ofwboot.xcf netbsd

Joerg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.