9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Lynema <elynema@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9front nvram setup
Date: Thu, 18 Apr 2024 08:38:59 -0400	[thread overview]
Message-ID: <CAFnNXi=iixN+K65_o0VkbNDoggvg==LmG-vUDQkGjGLA8szBUw@mail.gmail.com> (raw)
In-Reply-To: <983F291ACB9434DA026EC4C8414693EA@felloff.net>

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

It was that nvrlen setting. Apparently that needs to be something like 256
or it gets mad. It didnt like 0.

Sent from my phone. Please excuse the fact that I can't type on these
things to save my life.

On Thu, Apr 18, 2024, 4:59 AM <cinap_lenrek@felloff.net> wrote:

> > I am setting up a CPU server on 9front, and have been getting the
> following
> > errors that I just can't seem to work around.
> > can't write to nvram: i/o error
> > I have set my nvram in plan9.ini to
> > nvram=#S/sdE2/nvram
> > nvroff=0
> > nvrlen=0
> 
> You can break into rc shell at the bootargs prompt by typing !rc
> 
> then you can inspect the state of the sata drive.
> 
> cd /dev/sdE2
> ls
> cat ctl
> 
> Check if the nvram partition is here.
> 
> I'm curious as it complains only on write?
> 
> --
> cinap

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7b64800a7a98e3e1-M058812cc2e58a761c0b7cb05
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2433 bytes --]

  reply	other threads:[~2024-04-18 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 17:36 Eric Lynema
2024-04-15 18:03 ` [9fans] " elynema
2024-04-15 19:26   ` Eric Lynema
2024-04-18  8:57 ` [9fans] " cinap_lenrek
2024-04-18 12:38   ` Eric Lynema [this message]
2024-04-18 14:34     ` cinap_lenrek
2024-04-18 16:05       ` Eric Lynema

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='CAFnNXi=iixN+K65_o0VkbNDoggvg==LmG-vUDQkGjGLA8szBUw@mail.gmail.com' \
    --to=elynema@gmail.com \
    --cc=9fans@9fans.net \
    /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).