What I've been typing is
nvalias bsd /pci@f2000000/mac-io@17/ata-4@1f000/@0:9,ofwboot.xcf
(I had quite a lot of trouble originally working out what the boot 
command should be. I eventually copied the ofwboot.xcf file to my Mac 
OS partition manually; the installer hadn't done it for me. I put it at 
the root level of my Mac partition, but it may be in the wrong place -- 
I don't know how I would have got it there if I hadn't had OS 9 
installed, as that partition isn't recognised by BSD -- is there a way 
to do this, and did I put it i the right place?)

nvramrc type gives me
okalias bsd /pci@f2000000/mac-io@17/ata-4@1f000/@0:9,ofwboot.xcf
BUT when I try
boot bsd
the computer boots into OS 9 with extra blue text on the screen -- the 
text disappears too quickly to read it all, but it says it's booting 
/pci@f2000000/mac-io@17/ata-4@1f000/@0:10,\\:tbxi, then 'loading ELF.'

nvramrc dump gives me to the side of the hex output
devalias bsd /pci@f2000000/mac-io@17/ata-4@1f000/@0:9,ofwboot.xcf 
.devalias bsd /pci@f2000000/mac-io@17/ata-4@1f000/@0:9,ofwboot.xcf
What's the .devalias bit for?

If I use devalias can I alias more than the device? For example, I can 
already boot with
boot hd:9,ofwboot.xcf
I wanted to make this shorter.

After clearing with setenv nvramrc, I still get 'NVRAMRC not valid' on 
trying nvstore.


On 17 Apr 2005, at 09:07, Dan LaBell wrote:

>
> On Apr 15, 2005, at 5:52 AM, zeta.orionis wrote:
>
>> Open Firmware 3; I have 2 OSs (OS 9 and NetBSD 2.0) on this computer.
>>
>> In OF, nvalias [alias] [boot device] works as far as I can make out.
> exact input might help, but see below first
>
>> nvstore produces, without exception, 'NVRAMRC not valid.'
>>
> Do you need nvstore? From my notes on OF I have nvstore associated with
> nvedit, and nvrun...  Yes,  from Apple Open Firmware Read me:  Goes 
> nvedit which edits a temp buffer, then either nvrun to run forth code 
> from tempbuffer, or nvstore to actually
> move script into nvram, or nvquit to discard temp buffer.   nvalias 
> says it stores
> the command devalias <alias> <device-pathname> in nvramrc, I think, 
> maybe nvstore
> is not necessary, than devalias is more direct, and actually its the 
> temp buffer that is of nvedit/nvstore invalid because it hasn't been 
> initialized... No nvedit call, there may be a checksum involved or 
> similar-- I actually haven't used nvedit on the mac more than entering 
> it and then ^c to quit it, I should probably learn it.
>
>> I've reset PRAM and tried reset-nvram in OF; neither have helped.
>> Is resetting PRAM the same as resetting NVRAM, or are they two 
>> different things? Ought my next step be downloading the 90MB Mac OS 
>> 9.1 update so I can run t
>> he firmware updater? -- just tell me whether it would help, so I 
>> don't spend two days downloading for nothing. As far as I can see 
>> it's not NVRAM that's the problem; it's the NVRAMRC file. I don't 
>> know how to alter this
> Its listed in printenv
> Also
> nvramrc type
> will print it.
> cr ascii # emit nvramrc type ascii # emit cr
> should do
> #<contents of string>#
> all on 1 line, might help find any garbage in it.   I don't have any 
> nvaliases,
> I think I'll set one, and try it out.  That last line is untested I 
> actually just
> did cr nvramrc type cr, and then nvramrc  and verified 0 len string 
> via .s to look at stack.  -- should work though basically just a 
> putc...
>
>