From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] pccpu kernel: how to get #S/sdC0/nvram recognized?
Date: Tue, 4 Nov 2003 21:33:47 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0311042120520.4387-100000@maxroach.lanl.gov> (raw)
I have a pccpu kernel. I have got a #S compiled in and working. I can do
things to a compact flash if it is plugged in. Compact flash I/O works
fine.
Now I'm finding I'm not sure how the bit of magic happens that gets things
set up so that factotum can find #S/sdC0/nvram. The system comes up and
sdC0 is there all right, I can 'fdisk -p /dev/sdC0/data > /dev/sdC0/ctl'
dance and the 'prep -p blah blah' dance and make the nvram partition
visible -- after it has booted. But while it is booting, factotum has no
luck in getting to that partition.
On boot, I get the "can't read nvram: #S/sdC0/nvram' does not exist"
error from factotum. What particular thing makes it so that factotum can
find that #S/sdC0/nvram? What do I in the pccpu config file to make this
magic happen? I have not tried this approach before so I am fairly lost,
as you can see.
This is really weird, by the way. I've verified that the contents of CMOS
are good, and that factotum is reading and writing them. But on reboot,
factotum still is unhappy with the authid, after successfully reading the
two items that come before it. I'm not sure what's going on here.
So, I am trying #S/sdC0/nvram, but am hitting this other roadblock.
thanks
ron
next reply other threads:[~2003-11-05 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 4:33 ron minnich [this message]
2003-11-04 23:24 ` Russ Cox
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=Pine.LNX.4.44.0311042120520.4387-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).