From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by ewsd; Sat Aug 15 11:48:27 EDT 2020 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 3CE6F90A for <9front@9front.org>; Sat, 15 Aug 2020 11:48:21 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Sat, 15 Aug 2020 11:48:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=uPLZDx QVwaLxNL+JNktRC0I98y3IfrMoGCKxFNRY4M0=; b=pkmYiCzpFe3VhIlvYDCTuu OaXttdhTJWnTwTDG6Jr53arSJtH4nGdholLq1I9vRE5H/k2ichsK6KiDVDqRw+ye YYdngeENQkQGPNBPK48CmNT2A50euYv9+0a4dD4SaEcDt55d9lJ0DAa/awOOQhFN bIsc2twUHYhjwpUTNmQrcB762EcXo+qCKeAAGrhcxaF0BgTRTEdmGPNtVkURmlX9 kyDsNs+1XoL15IIhBHLX1SZFDcmSAhqji07k2K4lSzfFGwnsKONFyCT4EAe0WByx 9zFTuGs1V8ZjBe4toztH1lNUV19o+fC/r8Ektg8Au+17TTaO4hWJ3ZM34nVeyHlw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrleelgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdftrghmrghkrhhishhhnhgrnhcuofhuthhhuhhkrhhishhh nhgrnhdfuceorhgrmhesrhhkrhhishhhnhgrnhdrohhrgheqnecuggftrfgrthhtvghrnh epjeduiedukedtudekgeekkedufeeklefgheehieegleffffekhfehgfeugeetieeknecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprhgrmhesrh hkrhhishhhnhgrnhdrohhrgh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2BD70660069; Sat, 15 Aug 2020 11:48:18 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-185-g038a4a3-fm-20200813.001-g038a4a3b Mime-Version: 1.0 Message-Id: <440bd4b2-77b0-4177-94de-f1febd7136eb@www.fastmail.com> In-Reply-To: References: <20200810201412.3bcc6b9d@gmx.de> <4DA0B50AE9EEE940378CE51744CE2AD7@eigenstate.org> <20200810212116.3da09595@gmx.de> Date: Sat, 15 Aug 2020 21:17:59 +0530 From: "Ramakrishnan Muthukrishnan" To: 9front@9front.org Subject: Pi 4 CPU server problems (Was Re: [9front] NVRAM access on Raspi) Content-Type: text/plain List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: structured markup package manager 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 -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