From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Mon Aug 10 14:20:00 EDT 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id c30ab891 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Mon, 10 Aug 2020 11:19:46 -0700 (PDT)
Message-ID: <4DA0B50AE9EEE940378CE51744CE2AD7@eigenstate.org>
To: 9front@9front.org
Subject: Re: [9front] NVRAM access on Raspi
Date: Mon, 10 Aug 2020 11:19:45 -0700
From: ori@eigenstate.org
In-Reply-To: <20200810201412.3bcc6b9d@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: just-in-time-scale HTTP interface lifecycle-based locator 

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