9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "Can't read from nvram: /env/nvrof file does not exist"
Date: Fri, 18 Apr 2003 08:12:29 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0304180808020.19033-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <200304180310.h3I3AX516789@augusta.math.psu.edu>

On Thu, 17 Apr 2003, Dan Cross wrote:

> Hmm, that's strange.  I doubt it's a bug in the readnvram code, but
> rather, something weird that's causing the read to fail, and when
> readnvram() prints out an error message, "%r" is being interpolated
> with the last error string (that the nvroff environment variable
> doesn't exist).  My guess is that the nvram file doesn't exist on the
> 9fat on the flash device.

well, this brings up an issue. I am having a weird IDE problem with plan9
fdisk and prep.

Here are the platforms.
vmware, virtual disk (i.e. a file) on 2nd channel master (sdD0)
vmware, virtual disk (i.e. a file) on 1st channel master (sdC0)
vmware, compact flash physical disk on 2nd channel master (sdD0)
geode (hardware), compact flash on 2nd channel master    (sdD0)

If I do this in plan 9 fdisk:
fdisk /dev/sdx0/data
p 1 0 490
w
q

once I exit, no partition is there.

If I do this:
cat > /dev/sdx0/ctl
<some partition info>

the partition is there *until reboot*, then it goes away

If I fdisk the CF in linux, the partition(s) are there.
(in this case I create FAT and Plan 9 partitions in linux fdisk)

Once I fdisk the CF in linux, and use the disk in plan 9, I can:
prep -banw /dev/sdx0/plan9
the plan9 partitions are there -- until reboot.

OK, what am I doing wrong? Seems like the fdisk/prep stuff does not
'take'. But it works fine for install. weird.

ron



  parent reply	other threads:[~2003-04-18 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 23:18 ron minnich
2003-04-17 23:24 ` Russ Cox
2003-04-18  3:10   ` Dan Cross
2003-04-18  3:13     ` Russ Cox
2003-04-18 14:12     ` ron minnich [this message]
2003-04-18 15:22       ` Russ Cox
2003-04-18  3:24   ` Russ Cox
2003-04-18  6:13     ` Dan Cross
2003-04-18 14:17       ` ron minnich
2003-04-18 18:33         ` Dan Cross
2003-04-18 18:37           ` rsc
2003-04-18 18:38             ` ron minnich
2003-04-18 18:39             ` Dan Cross
2003-04-18 19:30             ` ron minnich
2003-04-18 19:43               ` Russ Cox
2003-04-18 19:51                 ` ron minnich
2003-04-18 19:56                   ` rsc
2003-04-18 14:13     ` ron minnich

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=Pine.LNX.4.44.0304180808020.19033-100000@maxroach.lanl.gov \
    --to=rminnich@lanl.gov \
    --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).