From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Date: Mon, 8 Mar 2004 13:18:27 +0100 [thread overview]
Message-ID: <912f0084d774ee243eb0f9fd2c8858f5@plan9.escet.urjc.es> (raw)
In-Reply-To: <20040308120540.GB2405@shire>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
Use our 9pcdisk.gz, it's up to date and works.
Also, zero out your nvram block (if any). It seems that you
have one and it seems to have a bad password (although AFAIK,
a 9pcdisk would not check that).
[-- Attachment #2: Type: message/rfc822, Size: 2883 bytes --]
From: "Alberto Cortés" <alcortes@coitt.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Date: Mon, 8 Mar 2004 13:05:40 +0100
Message-ID: <20040308120540.GB2405@shire>
Some time ago, David said:
> You're booting a cpu kernel that doesn't expect a user to be around
> and does expect to find its key (and other stuff) either in nvram
> or in a disk paritition called nvram.
>
> Boot a terminal kernel (like 9pcdisk or 9pcf).
I have tried with /386/9pcdisk and /386/9pcf but both kernels give me
the same results:
> 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?
--
url: http://163.117.15.158/~acortes/index.html
prev parent reply other threads:[~2004-03-08 12:18 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
2004-03-08 15:18 ` [9fans] boot.c -> bad nvram key -> solved! (workaround, not fixed) Alberto Cortés
2004-03-08 12:18 ` Fco.J.Ballesteros [this message]
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=912f0084d774ee243eb0f9fd2c8858f5@plan9.escet.urjc.es \
--to=nemo@lsub.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).