From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Date: Mon, 8 Mar 2004 09:06:17 -0500 [thread overview]
Message-ID: <e35699b2ff8f880998eab2b6ce6656d5@plan9.bell-labs.com> (raw)
In-Reply-To: <d9bb927d083025142cd90279eca5fd7d@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
My mistake, I missed the
kfs...
and thought it was the kenrel complaining. I'm an
idiot, sorry for causing someone to go off and check
what kernel they where running.
Rename the nvram partition to something else and
the messages should go away. Man 8 prep.
[-- Attachment #2: Type: message/rfc822, Size: 2779 bytes --]
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Date: Mon, 8 Mar 2004 14:17:24 +0200
Message-ID: <d9bb927d083025142cd90279eca5fd7d@proxima.alt.za>
> 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.
>> root is from (il, tcp, local)[local!#S/sdC0/fs]:
>> user[none]: glenda
>> kfs...bad nvram key
>> bad authentication id
>> bad authentication domain
>> version...time...
>
> Any advice?
>
Of course, somebody may want to get to the bottom of this, but I'm not
sure it's worth the effort.
++L
next prev parent reply other threads:[~2004-03-08 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:12 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 [this message]
2004-03-08 15:18 ` [9fans] boot.c -> bad nvram key -> solved! (workaround, not fixed) Alberto Cortés
2004-03-08 12:18 ` [9fans] boot.c -> bad nvram key 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=e35699b2ff8f880998eab2b6ce6656d5@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).