In message <E18A6ug-0007h0-00@chiark.greenend.org.uk>
          Ben Harris <bjh21@netbsd.org> wrote:

> In article <5b1df1914b.peter@riscpc01.reading.fourcom.com> you write:
> >In message <a166ed914b.peter@riscpc01.reading.fourcom.com>
> >          Peter Bell <peter@bellfamily.org.uk> wrote:
> >
> >> Yes, the bootloader will load a kernel from the ARCIN interface via
> >> UNIXFS, but it then panics in exactly the same way as it did with the
> >> Conner drive attached - waiting for irq.
> >> 
> >> However, if the same kernel is loaded from an ADFS device, it runs
> >> fine and the IBM drive attached to the ARCIN can be accessed perfectly
> >> well - even via PCNFS.
> >
> >Nope, it's not to do with where the kernel loads from, it happens when
> >the root partition and/or other options are given to the BtNetBSD
> >command.  IOW, if I let the system prompt for the root device, then it
> >comes up and runs perfectly happily.
> 
> Hmm.  And you're specifying the same root device in both cases, yes?

Yep, it's wd1a in all cases - whether specified in the fastboot, or
entered manually at the end of the boot.

> >> Have you managed to boot the kernel off an ARCIN-connected drive and,
> >> if so, are any of the changes you've made in current likely to
> >> be related to this?
> >
> >I think that question is still relevant - perhaps a delay is needed
> >after the card is detected?
> 
> My ARCIN only has a CD-RW drive on it, so I haven't experienced this
> problem.  I'll try shuffling things around this weekend and see what I can
> come up with.

Thanks very much - I do appreciate all your assistance.  In the
meantime I'll try to get my ARCIN back into a working state (see my
last post!).

-- 
Peter Bell - peter@bellfamily.org.uk