Pi 4 CPU server problems (Was Re: [9front] NVRAM access on Raspi)

["Ramakrishnan Muthukrishnan" <ram@rkrishnan.org>]

On Sat, Aug 15, 2020, at 8:38 PM, Ramakrishnan Muthukrishnan wrote:
>
> I am trying to do exactly this on a Pi4. This is what I did.
> 
> I created a file plan9.ini in the dos partition.
> 
> 9fs dos
> acme /n/dos/plan9.ini
> 
> and added:
> nvram=#S/sdM0/nvram
> 
> I did not understand the bit about nvme. What is the line you added for 
> that? There is no nvme in /dev/sdM0. I rebooted and auth/wrkey is still 
> complaining about nvram. There is no /env/nvram. How did you progress 
> from this? 

Answering my own query. It looks like on Pi kernels with 9front, plan9.ini does not seem to have any effect. I had to add nvram=#S/sdM0/nvram and service=cpu in the 9fat cmdline.txt file. auth/wrkey did work after that. (I could have just done nvram=/dev/sdM0/nvram as that would create the entry in /env, but took a while to sink in that environment variables are also files and I could just create one on the terminal..)

However, after a reboot, I am dropped into a shell:

cirno#

I can't seem to start rio ("rio -i riostart" says:

rio: can't open display: initdisplay: /dev/draw/new: '/dev/draw' file does not exist.

Indeed, that file does not exist. But I can drawterm into it (via drawterm compiled from 9front website): drawterm -h <ip address of pi> -u glenda

On the terminals, it shows:

aux/kbdfs: warning: can't open /dev/mousein: '/dev/mousein' './dev/mousein' file does not exist
tee: cannot open /dev/eia0: '/dev/eia0' mounted directory forbids creation

I wonder what this is saying. The mouse seem to work and I don't know what the eia device is.

Cheers
-- 
  Ramakrishnan