9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Date: Sun,  7 Mar 2004 10:50:15 -0500	[thread overview]
Message-ID: <bbd628f9745c1bcad07b614adc59b62c@plan9.bell-labs.com> (raw)
In-Reply-To: <20040307141250.GC879@shire>

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

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).

[-- Attachment #2: Type: message/rfc822, Size: 3619 bytes --]

From: "Alberto Cortés" <alcortes@coitt.es>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] boot.c -> bad nvram key
Date: Sun, 7 Mar 2004 15:12:50 +0100
Message-ID: <20040307141250.GC879@shire>

I have make a new installation of a plan 9 terminal in a clean disk
(actually, it is a vmware "machine").

After loading the kernel, boot(8) prints these lines:

> 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...

And then init(8) is executed and everything seems to work ok. I do
not know what those "bad foo bar" lines mean. Does it have something
to do with boot(8) trying authenticate with the local root server?

I have been looking at /sys/src/9/boot/boot.c and
/sys/src/9/boot/bootauth.c but i can not identify the problem, i think
it is somewhere between these lines (from boot.c):

> /*
> * pick a method and initialize it
> */
> mp = rootserver(argc ? *argv : 0);
> (*mp->config)(mp);
> islocal = strcmp(mp->name, "local") == 0;
> ishybrid = strcmp(mp->name, "hybrid") == 0;
> 
> /*
> * authentication agent
> */
> authentication(cpuflag);
>
> /*
> * connect to the root file system
> */
> fd = (*mp->connect)();
> if(fd < 0)
>       fatal("can't connect)();
> if(getenv("srvold9p"))
>       fd = old9p(fd);
> if(!islocal && !ishybrid){
>        if(cfs)
>              fd = (*cfs)(fd);
> }

I am not skilled enough for solving this, any pointers, explanations
or recommendations?

-- 
url: http://163.117.15.158/~acortes/index.html

  reply	other threads:[~2004-03-07 15:50 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 [this message]
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     ` [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=bbd628f9745c1bcad07b614adc59b62c@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).