From mboxrd@z Thu Jan  1 00:00:00 1970
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Message-ID: <Pine.LNX.4.44.0311032210060.28164-100000@maxroach.lanl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [9fans] factotum.hack -> factotum and ... no more CMOS as nvram
Date: Mon,  3 Nov 2003 22:17:16 -0700
Topicbox-Message-UUID: 7ed2ac78-eacc-11e9-9e20-41e7f4b1d025


OK, on the older kernel I built for the geodes, I got it to the point that
I could use #r/nvram (i.e. CMOS) as the nvram for the key. On the newer
kernels, I can't get this to work. I've checked the data in CMOS (a.k.a.
nvram) and it is correct - - checksum is right, data is right, etc.

But I keep getting this 'bad authentication id' message. It's as though
the factotum is not looking the desired nvram, or not reading it
correctly. I have hardwired these variables in the kernel:

nvram is #r/nvram
nvroff is 0
nvrlen is 112

One thing that has changed is that the line:
factotum.hack factotum
in my old pccpu has changed to:
/386/bin/auth/factotum factotum
in the new pccpu. Could this have any bearing on my problem? What was
factotum.hack?

Is there some other nvram or other variable I should set? Will factotum
pick up these environment variables and "do the right thing", or is
something else needed?

thanks

ron