9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Romano <unobe@cpan.org>
To: eckard.brauer@gmx.de
To: 9front@9front.org
Subject: Re: [9front] NVRAM access on Raspi
Date: Mon, 10 Aug 2020 12:08:49 -0700	[thread overview]
Message-ID: <FE14D1145D989FD0B090BB157F5AD66C@smtp.pobox.com> (raw)

> Am Mon, 10 Aug 2020 11:19:45 -0700 schrieb ori@eigenstate.org:
>> nvram=#S/sdM0/nvram in plan9.ini (or whatever the acutal
>> device is. You also need to do this with nvme.)
> Just tried that, seems not to work. Errors are unchanged.
> 
> Can I check it's taken from plan9.ini, as it also doesn't seem to like
> my -a tcp!*!564 and nobootprompt= lines?
> 
> lc '#S/sdM0' does show the nvram entry, but I don't trust that so far,
> as it also shows an 9fat entry, and even 9fs 9fat (taken from FQA to
> acceess plan9.ini) doesn't work. I have to do 9fs dos, maybe as only
> /dev/sdM0/fs and /dev/sdM0/dos are mentioned with a short name at boot
> (or in /dev/kmesg). But OTOH xd /dev/sdM0/nvram shows me a disk block
> of zeroed storage, so I'd expect the device entry to be correct.

For the rpi4, there's no default in /sys/src/libauthsrv/readnvram.c
for arm64.  Updating to have an arm64 default as /dev/sdM0/nvram
allows for the pi3 image downloaded from 9front to use that
autoamatically without having to set nvram=/dev/sdM0/nvram before
running auth/wrkey, or set it in cmdline.txt.

cmdline.txt is where the plan9.ini values are taken from, but it all
needs to be *on* *one* *line*:

	console=0 bootargs='/dev/sdM0/fs -A -a tcp!*!564' ...

Also, there's no default arm64 when creating a profile--there should
be.  Update /sys/lib/newuser to include that.

(I have the above in my notes and have been meaning to put out a patch to update readnvram.c and newuser, but haven't.)

Also note that if you're going to be running rio on the rpi4 as a cpu
server instead of drawterm'ing in, you might run into another problem.
 From time to time when running rio, I get this on /dev/kprint:

	rio: setname faled: unknown id for draw image'

which I tracked down to /sys/src/cmd/rio/wind.c.  But I don't know the
cause, and it makes the entire graphics messed up: a window seemingly
is maximized to take the entire screen, but it actually does not, and
the re-paint of the windows has to be done by moving the different
windows around.  I have to slay rio, and restart to get the graphics
"fixed".

I hope the above helps.  An rpi4 is my primary 9front device for now,
so that's where I'm writing this from.


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:08 Romano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-10 18:14 Eckard Brauer
2020-08-10 18:19 ` [9front] " ori
2020-08-10 18:55   ` Eckard Brauer
2020-08-10 19:21   ` Eckard Brauer
2020-08-15 15:08     ` Ramakrishnan Muthukrishnan
2020-08-15 16:45       ` ori

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=FE14D1145D989FD0B090BB157F5AD66C@smtp.pobox.com \
    --to=unobe@cpan.org \
    --cc=eckard.brauer@gmx.de \
    /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).