From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <912f0084d774ee243eb0f9fd2c8858f5@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] boot.c -> bad nvram key From: Fco.J.Ballesteros In-Reply-To: <20040308120540.GB2405@shire> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-btablgfltroujxtzyrwacxxedd" Date: Mon, 8 Mar 2004 13:18:27 +0100 Topicbox-Message-UUID: 23476bd6-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-btablgfltroujxtzyrwacxxedd Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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). --upas-btablgfltroujxtzyrwacxxedd Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Mon Mar 8 13:07:04 MET 2004 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 6467A19A07; Mon, 8 Mar 2004 07:06:38 -0500 (EST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 265CA19A08; Mon, 8 Mar 2004 07:06:33 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 6D98719CFC; Mon, 8 Mar 2004 07:05:45 -0500 (EST) Received: from tnetsmtp1.mail.isp (smtp.telefonica.net [213.4.129.135]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id BE5BB19CC4 for <9fans@cse.psu.edu>; Mon, 8 Mar 2004 07:05:43 -0500 (EST) Received: from 80-26-72-139.uc.nombres.ttd.es ([80.26.72.139]) by tnetsmtp1.mail.isp (terra.es) with ESMTP id HU9AXI00.0N8 for <9fans@cse.psu.edu>; Mon, 8 Mar 2004 13:05:42 +0100 Received: from alcortes by 80-26-72-139.uc.nombres.ttd.es with local (Exim 3.35 #1 (Debian)) id 1B0JVs-0000fs-00 for <9fans@cse.psu.edu>; Mon, 08 Mar 2004 13:05:40 +0100 From: Alberto =?iso-8859-1?Q?Cort=E9s?= To: 9fans@cse.psu.edu Subject: Re: [9fans] boot.c -> bad nvram key Message-ID: <20040308120540.GB2405@shire> References: <20040307141250.GC879@shire> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-Operating-System: Linux 2.4.18 i686 X-Editor: GNU Emacs 21.2.1 Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: Alberto =?iso-8859-1?Q?Cort=E9s?= List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 8 Mar 2004 13:05:40 +0100 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu X-Spam-Status: No, hits=0.2 required=5.0 tests=NORMAL_HTTP_TO_IP autolearn=no version=2.63 X-Spam-Level: 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 --upas-btablgfltroujxtzyrwacxxedd--