At 3:05 PM -0800 3/11/03, Jesse Peterson wrote:
>Finding information on the web shows me the OF node /chosen, in 
>which "bootpath" is a property.  It had a bunch of hex values in it, 
>so i cleared it and then tried to boot after a cold boot.  Now I 
>just get a DEFAULT CATCH:
>
>0 > dev /chosen 0 encode-int " bootpath" property boot DEFAULT 
>CATCH!, code=FFF00300 at   %SRR0: FF80AC9C   %SRR1: 0000B070
>
>Any clues?
>
>Jesse Peterson wrote:
>>Interesting thoughts, if turn it on, immediatedly go to OF and wait 
>>a bit for the spin up (slow disk) and type 'boot', I get:
>>
>>0 > boot
>>OF_open bootpath=wos{s0
>>read stage 2 blocks: 01234567. done!
>>starting stage 2...
>>DEFAULT CATCH!, code=FFF00700 at   %SRR0: 00600000   %SRR1: 00083070
>>  ok
>>0 >
>>
>>Heh, bootpath=wos{s0 ??
>>Any ideas on this?

Hmmm.  Back to basics.  This is OF 1, right?  There are bugs in some 
of the boot variable code which our ofwboot detects and works around. 
Bootpath sounds related.

Make sure that you have boot-file, and boot-device environment 
variables are set to something rational, or else make sure the 
boot-command is set to something which includes a boot path on the 
boot command line.

My best guess.

>>Henry B. Hotz wrote:
>>
>>>At 7:17 PM -0800 3/10/03, Jesse Peterson wrote:
>>>
>>>>I can only assume that netbsd doesn't support automatically 
>>>>booting from this machine.  Is this true?  Somebody point me to 
>>>>the light!
>>>
>>>
>>>
>>>Sounds like it has nothing to do with the disk spinup.  You need 
>>>to find out what the "soft reset" does and duplicate it.  I 
>>>wouldn't have a clue myself.

-- 
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu