From: "Alberto Cortés" <alcortes@coitt.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key -> solved! (workaround, not fixed)
Date: Mon, 8 Mar 2004 16:18:12 +0100 [thread overview]
Message-ID: <20040308151812.GB2988@shire> (raw)
In-Reply-To: <d9bb927d083025142cd90279eca5fd7d@proxima.alt.za>
Some time ago, lucio said:
> > I have tried with /386/9pcdisk and /386/9pcf but both kernels give me
> > the same results:
> >
> Don't worry about it, it is harmless. You may even want to get rid of
> the warning by executing auth/wrkey once the terminal is running. I
> suspect something has crept into the startup that always checks for
> NVRAM and the installation seems always to create an NVRAM partition.
> But, as I mentioned, it does no harm whatsoever.
Thats right!, the last ISO i downloaded from Plan9 web site creates a
small (1 sector, 512 B) partition for nvram. Also, the boot(8) process
for terminals check keys in it.
Maybe something crept in boot(8) on the last versions, because in a
previous version of plan9 i didn't see that behaviour (maybe some code
from cpu kernel leaked in???).
Anyway, i have get rid of the warnings by deleting/renaming the nvram partition
with disk/prep /dev/sdC0/9fat as Presotto & Nemo suggested.
It can also be solved with the auth/wrkey trick that Lucio and
Zhen Lin mentioned (not sure, i didn't try it).
As Lucio said, the warnings were quite harmless as the systems boot
normally, but i were a little worried (newbie thoughts).
Thanks you all for your help.
--
url: http://163.117.15.158/~acortes/index.html
next prev parent reply other threads:[~2004-03-08 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:12 [9fans] boot.c -> bad nvram key Alberto Cortés
2004-03-07 15:50 ` David Presotto
2004-03-07 17:07 ` Alberto Cortés
2004-03-08 14:16 ` Zhen Lin
2004-03-08 12:05 ` Alberto Cortés
2004-03-08 12:17 ` lucio
2004-03-08 14:06 ` David Presotto
2004-03-08 15:18 ` Alberto Cortés [this message]
2004-03-08 12:18 ` Fco.J.Ballesteros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040308151812.GB2988@shire \
--to=alcortes@coitt.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).