9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] NVRAM access on Raspi
Date: Mon, 10 Aug 2020 11:19:45 -0700	[thread overview]
Message-ID: <4DA0B50AE9EEE940378CE51744CE2AD7@eigenstate.org> (raw)
In-Reply-To: <20200810201412.3bcc6b9d@gmx.de>

> Hello,
> 
> after I finally managed to get a Raspberry running some more than the
> original install image, a few more problems arise.
> 
> When trying to auth/wrkey I only get an error that accessing the nvram
> is to an unknown device. src auth/nvram shows me that only readnvram()
> is called there, but the man page doesn't even mention arm systems, and
> what's stated there seems to indicate that the correct location,
> /dev/sdM0/nvram isn't even tried.
> 
> So is there a trick to work around that? Could I simply dd to the
> device, if I knew the correct format (I still don't) or bind /dev/sdM0
> to /dev/sdC0 or the like?
> 
> Another point: as I have an SD card larger than the decompressed SD
> image, how is it possible to expand the HJFS (or at least be able to
> use the rest as file system space)?
> 
> Thanks in advance && best regards
> Eckard

nvram=#S/sdM0/nvram in plan9.ini (or whatever the acutal
device is. You also need to do this with nvme.)



  reply	other threads:[~2020-08-10 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 18:14 Eckard Brauer
2020-08-10 18:19 ` ori [this message]
2020-08-10 18:55   ` [9front] " Eckard Brauer
2020-08-10 19:21   ` Eckard Brauer
2020-08-15 15:08     ` Ramakrishnan Muthukrishnan
2020-08-15 15:47       ` Pi 4 CPU server problems (Was Re: [9front] NVRAM access on Raspi) Ramakrishnan Muthukrishnan
2020-08-15 19:18         ` Eckard Brauer
2020-08-15 16:45       ` [9front] NVRAM access on Raspi ori
2020-08-10 19:08 Romano

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=4DA0B50AE9EEE940378CE51744CE2AD7@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    /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).